|
40 | 40 | </address>
|
41 | 41 | </author>
|
42 | 42 |
|
43 |
| - <date day="3" month="October" year="2024" /> |
| 43 | + <date day="15" month="October" year="2024" /> |
44 | 44 |
|
45 | 45 | <area>Security</area>
|
46 | 46 | <workgroup>OAuth Working Group</workgroup>
|
|
1180 | 1180 | Values are registered on a Specification Required <xref target="RFC8126"/>
|
1181 | 1181 | basis after a two-week review period on the [email protected]
|
1182 | 1182 | mailing list, on the advice of one or more Designated Experts.
|
1183 |
| - However, to allow for the allocation of values prior to publication, |
| 1183 | + However, to allow for the allocation of values prior to publication |
| 1184 | + of the final version of a specification, |
1184 | 1185 | the Designated Experts may approve registration once they are satisfied
|
1185 |
| - that such a specification will be published. |
| 1186 | + that the specification will be completed and published. |
| 1187 | + However, if the specification is not completed and published |
| 1188 | + in a timely manner, as determined by the Designated Experts, |
| 1189 | + the Designated Experts may request that IANA withdraw the registration. |
1186 | 1190 | </t>
|
1187 | 1191 | <t>
|
1188 | 1192 | Registration requests sent to the mailing list for review should use
|
|
1216 | 1220 | creating a conflict of interest for a particular Expert,
|
1217 | 1221 | that Expert should defer to the judgment of the other Experts.
|
1218 | 1222 | </t>
|
| 1223 | + <t> |
| 1224 | + The reason for the use of the mailing list is to enable |
| 1225 | + public review of registration requests, enabling both Designated Experts |
| 1226 | + and other interested parties to provide feedback on proposed registrations. |
| 1227 | + The reason to allow the Designated Experts to |
| 1228 | + allocate values prior to publication as a final specification is to enable |
| 1229 | + giving authors of specifications proposing registrations |
| 1230 | + the benefit of review by the Designated Experts |
| 1231 | + before the specification is completely done, |
| 1232 | + so that if problems are identified, the authors can iterate and fix them |
| 1233 | + before publication of the final specification. |
| 1234 | + </t> |
1219 | 1235 |
|
1220 | 1236 | <section title="OAuth Protected Resource Metadata Registry" anchor="PRMetadataReg">
|
1221 | 1237 | <t>
|
|
1845 | 1861 | The authors of this specification would like to thank the attendees of the IETF 115 OAuth and HTTP API Working Group meetings
|
1846 | 1862 | and the attendees of subsequent OAuth Working Group meetings for their input on this specification.
|
1847 | 1863 | We would would also like to thank
|
| 1864 | + Amanda Baber, |
1848 | 1865 | Mike Bishop,
|
1849 | 1866 | Ralph Bragg,
|
1850 | 1867 | Brian Campbell,
|
|
1875 | 1892 | <section anchor="History" title="Document History">
|
1876 | 1893 | <t>[[ to be removed by the RFC Editor before publication as an RFC ]]</t>
|
1877 | 1894 |
|
| 1895 | + <t> |
| 1896 | + -13 |
| 1897 | + <list style="symbols"> |
| 1898 | + <t> |
| 1899 | + Described motivations for the IANA registration procedure, |
| 1900 | + per additional comments by Murray Kucherawy. |
| 1901 | + </t> |
| 1902 | + </list> |
| 1903 | + </t> |
| 1904 | + |
1878 | 1905 | <t>
|
1879 | 1906 | -12
|
1880 | 1907 | <list style="symbols">
|
|
0 commit comments