| 1 |
<pre>Internet Architecture Board (IAB) D. McPherson, Ed. |
| 2 |
Request for Comments: 6220 O. Kolkman, Ed. |
| 3 |
Category: Informational J. Klensin, Ed. |
| 4 |
ISSN: 2070-1721 G. Huston, Ed. |
| 5 |
April 2011 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Defining the Role and Function of IETF Protocol</span> |
| 9 |
<span class="h1">Parameter Registry Operators</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
Many Internet Engineering Task Force (IETF) protocols make use of |
| 14 |
commonly defined values that are passed in messages or packets. To |
| 15 |
ensure consistent interpretation of these values between independent |
| 16 |
implementations, there is a need to ensure that the values and |
| 17 |
associated semantic intent are uniquely defined. The IETF uses |
| 18 |
registry functions to record assigned protocol parameter values and |
| 19 |
their associated semantic intentions. For each IETF protocol |
| 20 |
parameter, it is current practice for the IETF to delegate the role |
| 21 |
of Protocol Parameter Registry Operator to a nominated entity. This |
| 22 |
document provides a description of, and the requirements for, these |
| 23 |
delegated functions. |
| 24 |
|
| 25 |
Status of This Memo |
| 26 |
|
| 27 |
This document is not an Internet Standards Track specification; it is |
| 28 |
published for informational purposes. |
| 29 |
|
| 30 |
This document is a product of the Internet Architecture Board (IAB) |
| 31 |
and represents information that the IAB has deemed valuable to |
| 32 |
provide for permanent record. Documents approved for publication by |
| 33 |
the IAB are not a candidate for any level of Internet Standard; see |
| 34 |
<a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 35 |
|
| 36 |
Information about the current status of this document, any errata, |
| 37 |
and how to provide feedback on it may be obtained at |
| 38 |
<a href="http://www.rfc-editor.org/info/rfc6220">http://www.rfc-editor.org/info/rfc6220</a>. |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">McPherson, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. |
| 68 |
|
| 69 |
Table of Contents |
| 70 |
|
| 71 |
<a href="#section-1">1</a>. Overview ........................................................<a href="#page-2">2</a> |
| 72 |
2. Roles and Responsibilities Concerning IETF |
| 73 |
Protocol Parameter Registries ...................................<a href="#page-3">3</a> |
| 74 |
<a href="#section-2.1">2.1</a>. Protocol Parameter Registry Operator Role ..................<a href="#page-4">4</a> |
| 75 |
<a href="#section-2.2">2.2</a>. IAB Role ...................................................<a href="#page-7">7</a> |
| 76 |
<a href="#section-2.3">2.3</a>. IESG Role ..................................................<a href="#page-7">7</a> |
| 77 |
<a href="#section-2.4">2.4</a>. Role of the IETF Trust .....................................<a href="#page-8">8</a> |
| 78 |
<a href="#section-2.5">2.5</a>. Role of the IAOC ...........................................<a href="#page-8">8</a> |
| 79 |
<a href="#section-3">3</a>. Miscellaneous Considerations ....................................<a href="#page-8">8</a> |
| 80 |
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-9">9</a> |
| 81 |
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-9">9</a> |
| 82 |
<a href="#section-6">6</a>. Informative References ..........................................<a href="#page-9">9</a> |
| 83 |
<a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-10">10</a> |
| 84 |
<a href="#section-8">8</a>. IAB Members ....................................................<a href="#page-10">10</a> |
| 85 |
|
| 86 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Overview</span> |
| 87 |
|
| 88 |
Many IETF protocols make use of commonly defined values that are |
| 89 |
passed within messages or packets. To ensure consistent |
| 90 |
interpretation of these values between independent implementations, |
| 91 |
there is a need to ensure that the values and associated semantic |
| 92 |
intent are uniquely defined. The IETF uses registries to record each |
| 93 |
of the possible values of a protocol parameter and their associated |
| 94 |
semantic intent. These registries, their registration policy, and |
| 95 |
the layout of their content are defined in the so-called "IANA |
| 96 |
Considerations" sections of IETF documents. |
| 97 |
|
| 98 |
The organizational separation between the IETF and its Registry |
| 99 |
Operators parallels ones that are fairly common among standards |
| 100 |
development organizations (SDOs) although less common among |
| 101 |
technology consortia and similar bodies. These functions have been |
| 102 |
separated into different organizations for several reasons. They |
| 103 |
include dealing with administrative issues, addressing concerns about |
| 104 |
maintaining an adequate distance between basic policy and specific |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">McPherson, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
allocations, and avoiding any potential conflicts of interest that |
| 114 |
might arise from commercial or organizational relationships. For |
| 115 |
example, most ISO and ISO/IEC JTC1 standards that require |
| 116 |
registration activities specify a Registration Authority (RA) or |
| 117 |
Maintenance Agency (MA) that, in turn, control the actual |
| 118 |
registration decisions. The databases of what is registered for each |
| 119 |
standard may then be maintained by a secretariat or database function |
| 120 |
associated with the RA or MA or, less frequently, by the secretariat |
| 121 |
of the body that created and maintains the standard itself. |
| 122 |
|
| 123 |
This structural separation of roles exists within several places in |
| 124 |
the IETF framework (e.g., the RFC Editor function). The Internet |
| 125 |
Architecture Board (IAB), on behalf of the IETF, has the |
| 126 |
responsibility to define and manage the relationship with the |
| 127 |
Protocol Registry Operator role. This responsibility includes the |
| 128 |
selection and management of the Protocol Parameter Registry Operator, |
| 129 |
as well as management of the parameter registration process and the |
| 130 |
guidelines for parameter allocation. |
| 131 |
|
| 132 |
As with other SDOs, although it may delegate authority for some |
| 133 |
specific decisions, the IETF asserts authority and responsibility for |
| 134 |
the management of all of its protocol parameters and their |
| 135 |
registries, even while it generally remains isolated from the |
| 136 |
selection of particular values once a registration is approved. This |
| 137 |
document describes the function of these registries as they apply to |
| 138 |
individual protocol parameters defined by the IETF Internet Standards |
| 139 |
Process [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>] to allow for an orderly implementation by the |
| 140 |
Internet Administrative Oversight Committee (IAOC), and others as |
| 141 |
needed, under guidance from the IAB. |
| 142 |
|
| 143 |
Below we provide a description of the requirements for these |
| 144 |
delegated functions, which the IETF traditionally refers to as the |
| 145 |
Internet Assigned Numbers Authority (IANA) function. |
| 146 |
|
| 147 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Roles and Responsibilities Concerning IETF Protocol Parameter</span> |
| 148 |
<span class="h2"> Registries</span> |
| 149 |
|
| 150 |
The IETF's longstanding practice is to outsource the management and |
| 151 |
implementation of some important functions (e.g., [<a href="./rfc5620" title=""RFC Editor Model (Version 1)"">RFC5620</a>]). The |
| 152 |
protocol parameter registry function falls into this category of |
| 153 |
outsourced functions, and what follows here is the description of the |
| 154 |
roles and responsibilities with respect to the registration of IETF |
| 155 |
protocol parameters. |
| 156 |
|
| 157 |
Specifically, this document describes the operation and role of a |
| 158 |
delegated IETF Protocol Parameter Registry Operator, to be selected |
| 159 |
and administered by the IETF Administrative Support Activity (IASA) |
| 160 |
[<a href="./rfc4071" title=""Structure of the IETF Administrative Support Activity (IASA)"">RFC4071</a>]. While there is generally a single Protocol Parameter |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">McPherson, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
Registry Operator, additional Operators may be selected to implement |
| 170 |
specific registries, and that has been done occasionally. Having a |
| 171 |
single Operator facilitates coordination among registries, even those |
| 172 |
that are not obviously related, and also makes it easier to have |
| 173 |
consistency of formats and registry structure, which aids users of |
| 174 |
the registries and assists with quality control. |
| 175 |
|
| 176 |
Many protocols make use of identifiers consisting of constants and |
| 177 |
other well-known values. Even after a protocol has been defined and |
| 178 |
deployment has begun, new values may need to be assigned (e.g., for a |
| 179 |
new option type in DHCP, or a new encryption or authentication |
| 180 |
algorithm for IPsec). To ensure that such quantities have consistent |
| 181 |
values and interpretations in different implementations, their |
| 182 |
assignment must be administered by a central authority. For IETF |
| 183 |
protocols, that role is provided by a delegated Protocol Parameter |
| 184 |
Registry Operator. For any particular protocol parameter there is a |
| 185 |
single delegated Registry Operator. |
| 186 |
|
| 187 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Protocol Parameter Registry Operator Role</span> |
| 188 |
|
| 189 |
The IETF Protocol Parameter Registry function is undertaken under the |
| 190 |
auspices of the Internet Architecture Board. |
| 191 |
|
| 192 |
The roles of the Protocol Parameter Registry Operator are as follows: |
| 193 |
|
| 194 |
o Review and Advise |
| 195 |
|
| 196 |
* A Registry Operator may be requested to review Internet-Drafts |
| 197 |
that are being considered by the Internet Engineering Steering |
| 198 |
Group (IESG), with the objective of offering advice to the IESG |
| 199 |
regarding the contents of the "IANA Considerations" section, |
| 200 |
whether such a section, when required, is clear in terms of |
| 201 |
direction to the Registry Operator, and whether the section is |
| 202 |
consistent with the current published Registry Operator |
| 203 |
guidelines. |
| 204 |
|
| 205 |
o Registry |
| 206 |
|
| 207 |
* To operate a registry of protocol parameter assignments. |
| 208 |
|
| 209 |
* The delegated Registry Operator registers values for Internet |
| 210 |
protocol parameters only as directed by the criteria and |
| 211 |
procedures specified in RFCs, including Proposed, Draft, and full |
| 212 |
Internet Standards, Best Current Practice documents, and other |
| 213 |
RFCs that require protocol parameter assignment. |
| 214 |
|
| 215 |
If values for Internet protocol parameters were not specified, or |
| 216 |
in case of ambiguity, the Registry Operator will continue to |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">McPherson, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
assign and register only those protocol parameters that have |
| 226 |
already been delegated to the Operator, following past and |
| 227 |
current practice for such assignments, unless otherwise directed |
| 228 |
in terms of operating practice by the IESG. In the case of |
| 229 |
ambiguity, the Registry Operator is expected to identify the |
| 230 |
ambiguity to the IAB or IESG as appropriate and either suggest |
| 231 |
better text or ask the appropriate parties for clarification. |
| 232 |
|
| 233 |
* For each protocol parameter, the associated registry includes: |
| 234 |
|
| 235 |
+ a reference to the RFC document that describes the parameter |
| 236 |
and the associated "IANA Considerations" concerning the |
| 237 |
parameter, and |
| 238 |
|
| 239 |
+ for each registration of a protocol parameter value, the source |
| 240 |
of the registration and the date of the registration, if the |
| 241 |
date of registration is known, and |
| 242 |
|
| 243 |
+ any other information specified as being included in the |
| 244 |
registration data in the RFC document that describes the |
| 245 |
parameter. |
| 246 |
|
| 247 |
+ If in doubt or in case of a technical dispute, the Registry |
| 248 |
Operator will seek and follow technical guidance exclusively |
| 249 |
from the IESG. Where appropriate, the IESG will appoint an |
| 250 |
expert to advise the Registry Operator. |
| 251 |
|
| 252 |
* The Registry Operator will work with the IETF to develop any |
| 253 |
missing criteria and procedures over time, which the Registry |
| 254 |
Operator will adopt when so instructed by the IESG. |
| 255 |
|
| 256 |
* Unless special circumstances apply to subsets of the data and |
| 257 |
specific rules are established by IETF consensus, each protocol |
| 258 |
parameter registry operates as a public registry, and the |
| 259 |
contents of the registry are openly available to the public, |
| 260 |
on-line and free of charge. |
| 261 |
|
| 262 |
* The Registry Operator assigns protocol parameter values in |
| 263 |
accordance with the policy associated with the protocol |
| 264 |
parameter, such as "First Come First Served" or "Expert Review" |
| 265 |
[<a href="./rfc5226" title="">RFC5226</a>]. |
| 266 |
|
| 267 |
o Mailing Lists |
| 268 |
|
| 269 |
* The Registry Operator maintains public mailing lists as specified |
| 270 |
in IANA Considerations [<a href="./rfc5226" title="">RFC5226</a>]. Such lists are designated for |
| 271 |
the purpose of review of assignment proposals in conjunction with |
| 272 |
a designated expert review function. In addition, each Protocol |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">McPherson, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
Parameter Registry Operator should maintain a mailing list that |
| 282 |
enables the registry staff of the Registry Operator to be |
| 283 |
contacted by email. |
| 284 |
|
| 285 |
o Liaison Activity |
| 286 |
|
| 287 |
* The Registry Operator will nominate a liaison point of contact. |
| 288 |
The Registry Operator, through this liaison, may be requested to |
| 289 |
provide advice to the IESG on IETF protocol parameters as well as |
| 290 |
the "IANA Considerations" section of each Internet-Draft that is |
| 291 |
being reviewed for publication as an RFC. Where appropriate the |
| 292 |
IESG will appoint an expert to advise the Registry Operator. |
| 293 |
|
| 294 |
o Reporting |
| 295 |
|
| 296 |
* The Registry Operator will submit periodic reports to the IAB |
| 297 |
concerning the operational performance of the registry function. |
| 298 |
As an example of the requirements for such reports, the reader is |
| 299 |
referred to a supplement [<a href="#ref-IAOC_SUPP">IAOC_SUPP</a>] to the "Memorandum of |
| 300 |
Understanding Concerning the Technical Work of the Internet |
| 301 |
Assigned Numbers Authority" [<a href="./rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"">RFC2860</a>] that provides service level |
| 302 |
agreement (SLA) guidelines under which ICANN, the current |
| 303 |
protocol parameter registry, must operate. |
| 304 |
|
| 305 |
* At the request of the chair of the IETF, IAB, or IAOC, the |
| 306 |
Registry Operator will undertake periodic reports to IETF Plenary |
| 307 |
meetings concerning the status of the registry function. |
| 308 |
|
| 309 |
* The Registry Operator will publish an annual report describing |
| 310 |
the status of the function and a summary of performance |
| 311 |
indicators. |
| 312 |
|
| 313 |
o Intellectual Property Rights and the Registry Operator |
| 314 |
|
| 315 |
* All assigned values are to be published and made available free |
| 316 |
of any charges. |
| 317 |
|
| 318 |
* The assignment values may be redistributed without modification. |
| 319 |
|
| 320 |
* Any intellectual property rights of the IETF protocol parameter |
| 321 |
assignment information, including the IETF protocol parameter |
| 322 |
registry and its contents, are to be held by the IETF Trust |
| 323 |
[<a href="./rfc4748" title=""RFC 3978 Update to Recognize the IETF Trust"">RFC4748</a>]. |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">McPherson, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. IAB Role</span> |
| 338 |
|
| 339 |
An Operator of an IETF protocol parameter registry undertakes the |
| 340 |
role as a delegated function under the authority of the IAB. |
| 341 |
|
| 342 |
The IAB has the responsibility to review the current description of |
| 343 |
the registry function from time to time and direct the Registry |
| 344 |
Operator to adopt amendments relating to its role and mode of |
| 345 |
operation according to the best interests of the IETF and the |
| 346 |
Internet community in general. |
| 347 |
|
| 348 |
The IAB has the responsibility to appoint an organization to |
| 349 |
undertake the delegated functions of the Protocol Parameter Registry |
| 350 |
Operator for each IETF protocol parameter. Specifically, the IAB |
| 351 |
defines the role and requirements for the desired functions. The |
| 352 |
IAOC is responsible for identifying a potential vendor, and once |
| 353 |
under agreement, managing the various aspects of the relationships |
| 354 |
with that vendor. To be clear, the IAB is in the deciding role |
| 355 |
(e.g., for appointment and termination), but must work in close |
| 356 |
consultation with the IAOC. |
| 357 |
|
| 358 |
The IAB has the responsibility to determine the terms and conditions |
| 359 |
of this delegated role. Such terms and conditions should ensure that |
| 360 |
the registry operates in a manner that is fully conformant to the |
| 361 |
functions described in this document. In addition, such terms and |
| 362 |
conditions must not restrict the rights and interests of the IETF |
| 363 |
with respect to the registry contents and maintenance. |
| 364 |
|
| 365 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IESG Role</span> |
| 366 |
|
| 367 |
The IESG is responsible for the technical direction regarding entries |
| 368 |
into IETF protocol parameter registries and maintaining the policies |
| 369 |
by which such technical directions are given. Technical direction |
| 370 |
itself is provided through the adoption of directives within the |
| 371 |
"IANA Considerations" section of IETF Stream RFCs or through stand- |
| 372 |
alone "IANA Considerations" RFCs. |
| 373 |
|
| 374 |
The IESG shall verify that Internet-Drafts that are offered for |
| 375 |
publication as IETF Stream RFCs [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>] include "IANA |
| 376 |
Considerations" sections when needed, and that "IANA Considerations" |
| 377 |
sections conform to the current published guidelines. |
| 378 |
|
| 379 |
Since technical assessment is not generally a responsibility of the |
| 380 |
Registry Operator, as part of providing the technical direction the |
| 381 |
IESG is responsible for identifying the technical experts that are |
| 382 |
required to, where appropriate, review registration requests or |
| 383 |
resolve open technical questions that relate to the registration of |
| 384 |
parameters. |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">McPherson, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
At its discretion, the IESG will organize the liaison activities with |
| 394 |
the Registry Operator's liaison point of contact so as to facilitate |
| 395 |
clear communications and effective operation of the registry |
| 396 |
function. |
| 397 |
|
| 398 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Role of the IETF Trust</span> |
| 399 |
|
| 400 |
The IETF Trust [<a href="./rfc4748" title=""RFC 3978 Update to Recognize the IETF Trust"">RFC4748</a>] was formed to act as the administrative |
| 401 |
custodian of all copyrights and other intellectual property rights |
| 402 |
relating to the IETF Standards Process, a function that had |
| 403 |
previously been performed by the Internet Society (ISOC) and the |
| 404 |
Corporation for National Research Initiatives (CNRI). |
| 405 |
|
| 406 |
Any intellectual property rights of IETF protocol parameter |
| 407 |
assignment information, including the registry and its contents, and |
| 408 |
all registry publications, are to be held by the IETF Trust on behalf |
| 409 |
of the IETF. |
| 410 |
|
| 411 |
The IETF Trust may make such regulations as appropriate for the |
| 412 |
redistribution of assignment values and registry publications. |
| 413 |
|
| 414 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Role of the IAOC</span> |
| 415 |
|
| 416 |
The IAOC is responsible for identifying a potential vendor in a |
| 417 |
manner of their choosing, based on IAB consultation, and for managing |
| 418 |
the various aspects of the relationships with that vendor. |
| 419 |
|
| 420 |
In addition, the IAOC has the responsibility to ensure long-term |
| 421 |
access, stability, and uniqueness across all such registries. This |
| 422 |
responsibility is of particular significance in the event that a |
| 423 |
relation with a Protocol Parameter Registry Operator is terminated. |
| 424 |
|
| 425 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Miscellaneous Considerations</span> |
| 426 |
|
| 427 |
While this document has focused on the creation of protocols by the |
| 428 |
IETF, the requirements provided are generically applicable to the |
| 429 |
extended IETF community as well (e.g., Internet Research Task Force |
| 430 |
(IRTF)). |
| 431 |
|
| 432 |
The IESG is responsible for the technical direction of the IETF |
| 433 |
Protocol Parameter registries and maintaining the policies by which |
| 434 |
such technical directions are given. The IESG is responsible, as |
| 435 |
part of the document approval process associated with the IETF Stream |
| 436 |
RFCs [<a href="./rfc4844" title=""The RFC Series and RFC Editor"">RFC4844</a>], for "IANA Considerations" verification. For the |
| 437 |
other RFC streams, the approval bodies are responsible for verifying |
| 438 |
that the documents include "IANA Considerations" sections when |
| 439 |
needed, and that "IANA Considerations" sections conform to the |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">McPherson, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
current published guidelines. In the case that IANA considerations |
| 450 |
in non-IETF document streams lead to a dispute, the IAB makes the |
| 451 |
final decision. |
| 452 |
|
| 453 |
This document talks about "Registry Operator" (singular), and while |
| 454 |
there are stability and economy-of-scale advantages for one single |
| 455 |
Operator, this document does not exclude having different Operators |
| 456 |
for different protocol registries when justified by the |
| 457 |
circumstances. |
| 458 |
|
| 459 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 460 |
|
| 461 |
This document does not propose any new protocols and does not |
| 462 |
introduce any new security considerations. |
| 463 |
|
| 464 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span> |
| 465 |
|
| 466 |
This document requires no direct IANA actions in terms of the |
| 467 |
creation or operation of a protocol parameter registry. However, |
| 468 |
this document does define the roles and responsibilities of various |
| 469 |
bodies who are responsible for, and associated with, the operation of |
| 470 |
protocol parameter registration functions for the IETF. |
| 471 |
|
| 472 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span> |
| 473 |
|
| 474 |
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision |
| 475 |
3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996. |
| 476 |
|
| 477 |
[<a id="ref-RFC2860">RFC2860</a>] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of |
| 478 |
Understanding Concerning the Technical Work of the |
| 479 |
Internet Assigned Numbers Authority", <a href="./rfc2860">RFC 2860</a>, June |
| 480 |
2000. |
| 481 |
|
| 482 |
[<a id="ref-RFC4071">RFC4071</a>] Austein, R., Ed., and B. Wijnen, Ed., "Structure of the |
| 483 |
IETF Administrative Support Activity (IASA)", <a href="https://www.rfc-editor.org/bcp/bcp101">BCP 101</a>, |
| 484 |
<a href="./rfc4071">RFC 4071</a>, April 2005. |
| 485 |
|
| 486 |
[<a id="ref-RFC4748">RFC4748</a>] Bradner, S., Ed., "<a href="./rfc3978">RFC 3978</a> Update to Recognize the IETF |
| 487 |
Trust", <a href="./rfc4748">RFC 4748</a>, October 2006. |
| 488 |
|
| 489 |
[<a id="ref-RFC4844">RFC4844</a>] Daigle, L., Ed., and Internet Architecture Board, "The |
| 490 |
RFC Series and RFC Editor", <a href="./rfc4844">RFC 4844</a>, July 2007. |
| 491 |
|
| 492 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 493 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 494 |
May 2008. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">McPherson, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
[<a id="ref-RFC5620">RFC5620</a>] Kolkman, O., Ed., and IAB, "RFC Editor Model (Version |
| 506 |
1)", <a href="./rfc5620">RFC 5620</a>, August 2009. |
| 507 |
|
| 508 |
[<a id="ref-IAOC_SUPP">IAOC_SUPP</a>] ICANN/IANA-IETF MoU Supplemental Agreement, |
| 509 |
<<a href="http://iaoc.ietf.org/documents/IETF-ICANN_Supplemental_Agreement.pdf">http://iaoc.ietf.org/documents/</a> |
| 510 |
<a href="http://iaoc.ietf.org/documents/IETF-ICANN_Supplemental_Agreement.pdf">IETF-ICANN_Supplemental_Agreement.pdf</a>>. |
| 511 |
|
| 512 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 513 |
|
| 514 |
This document is adapted from "Guidelines for Writing an IANA |
| 515 |
Considerations Section in RFCs" [<a href="./rfc5226" title="">RFC5226</a>], and has been modified to |
| 516 |
include explicit reference to Intellectual Property Rights and the |
| 517 |
roles of the IAB and IESG in relation to the IETF Protocol Parameter |
| 518 |
Registry function. |
| 519 |
|
| 520 |
The Internet Architecture Board acknowledges the assistance provided |
| 521 |
by reviewers of drafts of this document, including Scott Bradner, |
| 522 |
Brian Carpenter, Leslie Daigle, Adrian Farrel, Alfred Hoenes, Paul |
| 523 |
Hoffman, Alexey Melnikov, Thomas Narten, and Ray Pelletier. |
| 524 |
|
| 525 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IAB Members</span> |
| 526 |
|
| 527 |
Internet Architecture Board Members at the time this document was |
| 528 |
approved for publication were: |
| 529 |
|
| 530 |
Marcelo Bagnulo |
| 531 |
Ross Callon |
| 532 |
Spencer Dawkins |
| 533 |
Russ Housley |
| 534 |
John Klensin |
| 535 |
Olaf Kolkman |
| 536 |
Danny McPherson |
| 537 |
Jon Peterson |
| 538 |
Andrei Robachevsky |
| 539 |
Dave Thaler |
| 540 |
Hannes Tschofenig |
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">McPherson, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6220">RFC 6220</a> Role of Registry Operators April 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
Authors' Addresses |
| 562 |
|
| 563 |
Danny McPherson, Editor |
| 564 |
Verisign, Inc. |
| 565 |
EMail: [email protected] |
| 566 |
|
| 567 |
Olaf M. Kolkman, Editor |
| 568 |
NLnet Labs |
| 569 |
EMail: [email protected] |
| 570 |
|
| 571 |
John C Klensin, Editor |
| 572 |
EMail: [email protected] |
| 573 |
|
| 574 |
Geoff Huston, Editor |
| 575 |
APNIC |
| 576 |
EMail: [email protected] |
| 577 |
|
| 578 |
Internet Architecture Board |
| 579 |
EMail: [email protected] |
| 580 |
|
| 581 |
|
| 582 |
|
| 583 |
|
| 584 |
|
| 585 |
|
| 586 |
|
| 587 |
|
| 588 |
|
| 589 |
|
| 590 |
|
| 591 |
|
| 592 |
|
| 593 |
|
| 594 |
|
| 595 |
|
| 596 |
|
| 597 |
|
| 598 |
|
| 599 |
|
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
McPherson, et al. Informational [Page 11] |
| 613 |
</pre> |