Debian Codegraph @

rfc5226.html

raw
1 <pre>Network Working Group T. Narten
2 Request for Comments: 5226 IBM
3 BCP: 26 H. Alvestrand
4 Obsoletes: <a href="./rfc2434">2434</a> Google
5 Category: Best Current Practice May 2008
6
7
8 <span class="h1">Guidelines for Writing an IANA Considerations Section in RFCs</span>
9
10 Status of This Memo
11
12 This document specifies an Internet Best Current Practices for the
13 Internet Community, and requests discussion and suggestions for
14 improvements. Distribution of this memo is unlimited.
15
16 Abstract
17
18 Many protocols make use of identifiers consisting of constants and
19 other well-known values. Even after a protocol has been defined and
20 deployment has begun, new values may need to be assigned (e.g., for a
21 new option type in DHCP, or a new encryption or authentication
22 transform for IPsec). To ensure that such quantities have consistent
23 values and interpretations across all implementations, their
24 assignment must be administered by a central authority. For IETF
25 protocols, that role is provided by the Internet Assigned Numbers
26 Authority (IANA).
27
28 In order for IANA to manage a given namespace prudently, it needs
29 guidelines describing the conditions under which new values can be
30 assigned or when modifications to existing values can be made. If
31 IANA is expected to play a role in the management of a namespace,
32 IANA must be given clear and concise instructions describing that
33 role. This document discusses issues that should be considered in
34 formulating a policy for assigning values to a namespace and provides
35 guidelines for authors on the specific text that must be included in
36 documents that place demands on IANA.
37
38 This document obsoletes <a href="./rfc2434">RFC 2434</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Why Management of a Namespace May Be Necessary ..................<a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Designated Experts ..............................................<a href="#page-4">4</a>
62 <a href="#section-3.1">3.1</a>. The Motivation for Designated Experts ......................<a href="#page-4">4</a>
63 <a href="#section-3.2">3.2</a>. The Role of the Designated Expert ..........................<a href="#page-5">5</a>
64 <a href="#section-3.3">3.3</a>. Designated Expert Reviews ..................................<a href="#page-7">7</a>
65 <a href="#section-4">4</a>. Creating a Registry .............................................<a href="#page-8">8</a>
66 <a href="#section-4.1">4.1</a>. Well-Known IANA Policy Definitions .........................<a href="#page-9">9</a>
67 <a href="#section-4.2">4.2</a>. What to Put in Documents That Create a Registry ...........<a href="#page-12">12</a>
68 <a href="#section-4.3">4.3</a>. Updating IANA Guidelines for Existing Registries ..........<a href="#page-15">15</a>
69 <a href="#section-5">5</a>. Registering New Values in an Existing Registry .................<a href="#page-15">15</a>
70 <a href="#section-5.1">5.1</a>. What to Put in Documents When Registering Values ..........<a href="#page-15">15</a>
71 <a href="#section-5.2">5.2</a>. Updating Registrations ....................................<a href="#page-17">17</a>
72 <a href="#section-5.3">5.3</a>. Overriding Registration Procedures ........................<a href="#page-17">17</a>
73 <a href="#section-6">6</a>. Miscellaneous Issues ...........................................<a href="#page-18">18</a>
74 <a href="#section-6.1">6.1</a>. When There Are No IANA Actions ............................<a href="#page-18">18</a>
75 <a href="#section-6.2">6.2</a>. Namespaces Lacking Documented Guidance ....................<a href="#page-19">19</a>
76 <a href="#section-6.3">6.3</a>. After-the-Fact Registrations ..............................<a href="#page-19">19</a>
77 <a href="#section-6.4">6.4</a>. Reclaiming Assigned Values ................................<a href="#page-19">19</a>
78 <a href="#section-7">7</a>. Appeals ........................................................<a href="#page-20">20</a>
79 <a href="#section-8">8</a>. Mailing Lists ..................................................<a href="#page-20">20</a>
80 <a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-20">20</a>
81 <a href="#section-10">10</a>. Changes Relative to <a href="./rfc2434">RFC 2434</a> ..................................<a href="#page-21">21</a>
82 <a href="#section-11">11</a>. Acknowledgments ...............................................<a href="#page-22">22</a>
83 <a href="#section-12">12</a>. References ....................................................<a href="#page-22">22</a>
84 <a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-22">22</a>
85 <a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-22">22</a>
86
87 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
88
89 Many protocols make use of fields that contain constants and other
90 well-known values (e.g., the Protocol field in the IP header [<a href="#ref-IP" title="&quot;Internet Protocol&quot;">IP</a>] or
91 MIME media types [<a href="#ref-MIME-REG" title="&quot;Media Type Specifications and Registration Procedures&quot;">MIME-REG</a>]). Even after a protocol has been defined
92 and deployment has begun, new values may need to be assigned (e.g., a
93 new option type in DHCP [<a href="#ref-DHCP-OPTIONS" title="&quot;DHCP Options and BOOTP Vendor Extensions&quot;">DHCP-OPTIONS</a>] or a new encryption or
94 authentication transform for IPsec [<a href="#ref-IPSEC" title="&quot;Security Architecture for the Internet Protocol&quot;">IPSEC</a>]). To ensure that such
95 fields have consistent values and interpretations in different
96 implementations, their assignment must be administered by a central
97 authority. For IETF protocols, that role is provided by the Internet
98 Assigned Numbers Authority (IANA) [<a href="#ref-IANA-MOU" title="&quot;Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority&quot;">IANA-MOU</a>].
99
100 In this document, we call the set of possible values for such a field
101 a "namespace"; its actual value may be a text string, a number, or
102 another kind of value. The binding or association of a specific
103 value with a particular purpose within a namespace is called an
104 assigned number (or assigned value, or sometimes a "code point",
105
106
107
108 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
111
112
113 "protocol constant", or "protocol parameter"). Each assignment of a
114 value in a namespace is called a registration.
115
116 In order for IANA to manage a given namespace prudently, it needs
117 guidelines describing the conditions under which new values should be
118 assigned or when (and how) modifications to existing values can be
119 made. This document provides guidelines to authors on what sort of
120 text should be added to their documents in order to provide IANA
121 clear guidelines, and it reviews issues that should be considered in
122 formulating an appropriate policy for assigning numbers to name
123 spaces.
124
125 Not all namespaces require centralized administration. In some
126 cases, it is possible to delegate a namespace in such a way that
127 further assignments can be made independently and with no further
128 (central) coordination. In the Domain Name System, for example, IANA
129 only deals with assignments at the higher levels, while subdomains
130 are administered by the organization to which the space has been
131 delegated. As another example, Object Identifiers (OIDs) as defined
132 by the ITU are also delegated [<a href="#ref-ASSIGNED" title="&quot;Assigned Numbers: RFC 1700 is Replaced by an On-line Database&quot;">ASSIGNED</a>]; IANA manages the subtree
133 rooted at "iso.org.dod.internet" (1.3.6.1) . When a namespace is
134 delegated, the scope of IANA is limited to the parts of the namespace
135 where IANA has authority.
136
137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
138 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
139 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-KEYWORDS" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">KEYWORDS</a>].
140 For this document, "the specification" as used by <a href="./rfc2119">RFC 2119</a> refers to
141 the processing of protocol documents within the IETF standards
142 process.
143
144 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Why Management of a Namespace May Be Necessary</span>
145
146 One issue to consider in managing a namespace is its size. If the
147 space is small and limited in size, assignments must be made
148 carefully to prevent exhaustion of the space. If the space is
149 essentially unlimited, on the other hand, potential exhaustion will
150 probably not be a practical concern at all. Even when the space is
151 essentially unlimited, however, it is usually desirable to have at
152 least a minimal review prior to assignment in order to:
153
154 - prevent the hoarding of or unnecessary wasting of values. For
155 example, if the space consists of text strings, it may be
156 desirable to prevent entities from obtaining large sets of
157 strings that correspond to desirable names (e.g., existing
158 company names).
159
160
161
162
163
164 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
167
168
169 - provide a sanity check that the request actually makes sense and
170 is necessary. Experience has shown that some level of minimal
171 review from a subject matter expert is useful to prevent
172 assignments in cases where the request is malformed or not
173 actually needed (i.e., an existing assignment for an essentially
174 equivalent service already exists).
175
176 A second consideration is whether it makes sense to delegate the
177 namespace in some manner. This route should be pursued when
178 appropriate, as it lessens the burden on IANA for dealing with
179 assignments.
180
181 A third, and perhaps most important, consideration concerns potential
182 impact on the interoperability of unreviewed extensions. Proposed
183 protocol extensions generally benefit from community review; indeed,
184 review is often essential to avoid future interoperability problems
185 [<a href="#ref-PROTOCOL-EXT" title="&quot;Design Considerations for Protocol Extensions&quot;">PROTOCOL-EXT</a>].
186
187 When the namespace is essentially unlimited and there are no
188 potential interoperability issues, assigned numbers can safely be
189 given out to anyone without any subjective review. In such cases,
190 IANA can make assignments directly, provided that IANA is given
191 specific instructions on what types of requests it should grant, and
192 what information must be provided as part of a well-formed request
193 for an assigned number.
194
195 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Designated Experts</span>
196
197 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. The Motivation for Designated Experts</span>
198
199 It should be noted that IANA does not create or define assignment
200 policy itself; rather, it carries out policies that have been defined
201 by others and published in RFCs. IANA must be given a set of
202 guidelines that allow it to make allocation decisions with minimal
203 subjectivity and without requiring any technical expertise with
204 respect to the protocols that make use of a registry.
205
206 In many cases, some review of prospective allocations is appropriate,
207 and the question becomes who should perform the review and what is
208 the purpose of the review. One might think that an IETF working
209 group (WG) familiar with the namespace at hand should be consulted.
210 In practice, however, WGs eventually disband, so they cannot be
211 considered a permanent evaluator. It is also possible for namespaces
212 to be created through individual submission documents, for which no
213 WG is ever formed.
214
215
216
217
218
219
220 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
223
224
225 One way to ensure community review of prospective assignments is to
226 have the requester submit a document for publication as an RFC. Such
227 an action helps ensure that the specification is publicly and
228 permanently available, and it allows some review of the specification
229 prior to publication and assignment of the requested code points.
230 This is the preferred way of ensuring review, and is particularly
231 important if any potential interoperability issues can arise. For
232 example, some assignments are not just assignments, but also involve
233 an element of protocol specification. A new option may define fields
234 that need to be parsed and acted on, which (if specified poorly) may
235 not fit cleanly with the architecture of other options or the base
236 protocols on which they are built.
237
238 In some cases, however, the burden of publishing an RFC in order to
239 get an assignment is excessive. However, it is generally still
240 useful (and sometimes necessary) to discuss proposed additions on a
241 mailing list dedicated to the purpose (e.g., the [email protected]
242 for media types) or on a more general mailing list (e.g., that of a
243 current or former IETF WG). Such a mailing list provides a way for
244 new registrations to be publicly reviewed prior to getting assigned,
245 or gives advice to persons wanting help in understanding what a
246 proper registration should contain.
247
248 While discussion on a mailing list can provide valuable technical
249 feedback, opinions may vary and discussions may continue for some
250 time without clear resolution. In addition, IANA cannot participate
251 in all of these mailing lists and cannot determine if or when such
252 discussions reach consensus. Therefore, IANA relies on a "designated
253 expert" for advice regarding the specific question of whether an
254 assignment should be made. The designated expert is an individual
255 who is responsible for carrying out an appropriate evaluation and
256 returning a recommendation to IANA.
257
258 It should be noted that a key motivation for having designated
259 experts is for the IETF to provide IANA with a subject matter expert
260 to whom the evaluation process can be delegated. IANA forwards
261 requests for an assignment to the expert for evaluation, and the
262 expert (after performing the evaluation) informs IANA as to whether
263 or not to make the assignment or registration.
264
265 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. The Role of the Designated Expert</span>
266
267 The designated expert is responsible for initiating and coordinating
268 the appropriate review of an assignment request. The review may be
269 wide or narrow, depending on the situation and the judgment of the
270 designated expert. This may involve consultation with a set of
271 technology experts, discussion on a public mailing list, consultation
272 with a working group (or its mailing list if the working group has
273
274
275
276 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
279
280
281 disbanded), etc. Ideally, the designated expert follows specific
282 review criteria as documented with the protocol that creates or uses
283 the namespace. (See the IANA Considerations sections of [<a href="./rfc3748" title="&quot;Extensible Authentication Protocol (EAP)&quot;">RFC3748</a>]
284 and [<a href="./rfc3575" title="&quot;IANA Considerations for RADIUS (Remote Authentication Dial In User Service)&quot;">RFC3575</a>] for examples that have been done for specific
285 namespaces.)
286
287 Designated experts are expected to be able to defend their decisions
288 to the IETF community, and the evaluation process is not intended to
289 be secretive or bestow unquestioned power on the expert. Experts are
290 expected to apply applicable documented review or vetting procedures,
291 or in the absence of documented criteria, follow generally accepted
292 norms, e.g., those in <a href="#section-3.3">Section 3.3</a>.
293
294 <a href="#section-5.2">Section 5.2</a> discusses disputes and appeals in more detail.
295
296 Designated experts are appointed by the IESG (normally upon
297 recommendation by the relevant Area Director). They are typically
298 named at the time a document creating or updating a namespace is
299 approved by the IESG, but as experts originally appointed may later
300 become unavailable, the IESG will appoint replacements if necessary.
301
302 For some registries, it has proven useful to have multiple designated
303 experts. Sometimes those experts work together in evaluating a
304 request, while in other cases additional experts serve as backups.
305 In cases of disagreement among those experts, it is the
306 responsibility of those experts to make a single clear recommendation
307 to IANA. It is not appropriate for IANA to resolve disputes among
308 experts. In extreme situations (e.g., deadlock), the IESG may need
309 to step in to resolve the problem.
310
311 In registries where a pool of experts evaluates requests, the pool
312 should have a single chair responsible for defining how requests are
313 to be assigned to and reviewed by experts. In some cases, the expert
314 pool may consist of a primary and backups, with the backups involved
315 only when the primary expert is unavailable. In other cases, IANA
316 might assign requests to individual members in sequential or
317 approximate random order. In the event that IANA finds itself having
318 received conflicting advice from its experts, it is the
319 responsibility of the pool's chair to resolve the issue and provide
320 IANA with clear instructions.
321
322 Since the designated experts are appointed by the IESG, they may be
323 removed by the IESG.
324
325
326
327
328
329
330
331
332 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
335
336
337 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Designated Expert Reviews</span>
338
339 In the eight years since <a href="./rfc2434">RFC 2434</a> was published and has been put to
340 use, experience has led to the following observations:
341
342 - A designated expert must respond in a timely fashion, normally
343 within a week for simple requests to a few weeks for more
344 complex ones. Unreasonable delays can cause significant
345 problems for those needing assignments, such as when products
346 need code points to ship. This is not to say that all reviews
347 can be completed under a firm deadline, but they must be
348 started, and the requester and IANA should have some
349 transparency into the process if an answer cannot be given
350 quickly.
351
352 - If a designated expert does not respond to IANA's requests
353 within a reasonable period of time, either with a response or
354 with a reasonable explanation for the delay (e.g., some requests
355 may be particularly complex), and if this is a recurring event,
356 IANA must raise the issue with the IESG. Because of the
357 problems caused by delayed evaluations and assignments, the IESG
358 should take appropriate actions to ensure that the expert
359 understands and accepts his or her responsibilities, or appoint
360 a new expert.
361
362 - The designated expert is not required to personally bear the
363 burden of evaluating and deciding all requests, but acts as a
364 shepherd for the request, enlisting the help of others as
365 appropriate. In the case that a request is denied, and
366 rejecting the request is likely to be controversial, the expert
367 should have the support of other subject matter experts. That
368 is, the expert must be able to defend a decision to the
369 community as a whole.
370
371 In the case where a designated expert is used, but there are no
372 specific documented criteria for performing an evaluation, the
373 presumption should be that a code point should be granted, unless
374 there is a compelling reason to the contrary. Possible reasons to
375 deny a request include:
376
377 - scarcity of code points, where the finite remaining code points
378 should be prudently managed, or when a request for a large
379 number of code points is made, when a single code point is the
380 norm.
381
382 - documentation is not of sufficient clarity to evaluate or ensure
383 interoperability.
384
385
386
387
388 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
391
392
393 - the code point is needed for a protocol extension, but the
394 extension is not consistent with the documented (or generally
395 understood) architecture of the base protocol being extended,
396 and would be harmful to the protocol if widely deployed. It is
397 not the intent that "inconsistencies" refer to minor differences
398 "of a personal preference nature". Instead, they refer to
399 significant differences such as inconsistencies with the
400 underlying security model, implying a change to the semantics of
401 an existing message type or operation, requiring unwarranted
402 changes in deployed systems (compared with alternate ways of
403 achieving a similar result), etc.
404
405 - the extension would cause problems with existing deployed
406 systems.
407
408 - the extension would conflict with one under active development
409 by the IETF, and having both would harm rather than foster
410 interoperability.
411
412 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Creating a Registry</span>
413
414 Creating a registry involves describing the namespaces to be created,
415 an initial set of assignments (if appropriate), and guidelines on how
416 future assignments are to be made.
417
418 Once a registry has been created, IANA records assignments that have
419 been made. The following labels describe the status of an individual
420 (or range) of assignments:
421
422 Private Use: Private use only (not assigned), as described in
423 <a href="#section-4.1">Section 4.1</a>.
424
425 Experimental: Available for experimental use as described in
426 [<a href="#ref-EXPERIMENTATION" title="&quot;Assigning Experimental and Testing Numbers Considered Useful&quot;">EXPERIMENTATION</a>]. IANA does not record specific
427 assignments for any particular use.
428
429 Unassigned: Unused and available for assignment via documented
430 procedures.
431
432 Reserved: Not to be assigned. Reserved values are held for
433 special uses, such as to extend the namespace when it become
434 exhausted. Reserved values are not available for general
435 assignment.
436
437
438
439
440
441
442
443
444 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
447
448
449 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Well-Known IANA Policy Definitions</span>
450
451 The following are some defined policies, some of which are in use
452 today. These cover a range of typical policies that have been used
453 to date to describe the procedure for assigning new values in a
454 namespace. It is not required that documents use these terms; the
455 actual requirement is that the instructions to IANA are clear and
456 unambiguous. However, use of these terms is RECOMMENDED where
457 possible, since their meaning is widely understood.
458
459 Private Use - For private or local use only, with the type and
460 purpose defined by the local site. No attempt is made to
461 prevent multiple sites from using the same value in
462 different (and incompatible) ways. There is no need for
463 IANA to review such assignments (since IANA does not record
464 them) and assignments are not generally useful for broad
465 interoperability. It is the responsibility of the sites
466 making use of the Private Use range to ensure that no
467 conflicts occur (within the intended scope of use).
468
469 Examples: Site-specific options in DHCP [<a href="#ref-DHCP-IANA" title="&quot;Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types&quot;">DHCP-IANA</a>], Fibre
470 Channel Port Type Registry [<a href="./rfc4044" title="&quot;Fibre Channel Management MIB&quot;">RFC4044</a>], Exchange Types in the
471 IKEv2 header [<a href="./rfc4306" title="&quot;Internet Key Exchange (IKEv2) Protocol&quot;">RFC4306</a>].
472
473 Experimental Use - Similar to private or local use only, with the
474 purpose being to facilitate experimentation. See
475 [<a href="#ref-EXPERIMENTATION" title="&quot;Assigning Experimental and Testing Numbers Considered Useful&quot;">EXPERIMENTATION</a>] for details.
476
477 Example: Experimental Values in IPv4, IPv6, ICMPv4, ICMPv6,
478 UDP, and TCP Headers [<a href="./rfc4727" title="&quot;Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers&quot;">RFC4727</a>].
479
480 Hierarchical Allocation - Delegated managers can assign values
481 provided they have been given control over that part of the
482 namespace. IANA controls the higher levels of the namespace
483 according to one of the other policies.
484
485 Examples: DNS names, Object Identifiers, IP addresses.
486
487 First Come First Served - Assignments are made to anyone on a
488 first come, first served basis. There is no substantive
489 review of the request, other than to ensure that it is
490 well-formed and doesn't duplicate an existing assignment.
491 However, requests must include a minimal amount of clerical
492 information, such as a point of contact (including an email
493 address) and a brief description of how the value will be
494 used. Additional information specific to the type of value
495 requested may also need to be provided, as defined by the
496 namespace. For numbers, the exact value is generally
497
498
499
500 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
503
504
505 assigned by IANA; with names, specific text strings can
506 usually be requested.
507
508 Examples: SASL mechanism names [<a href="./rfc4422" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">RFC4422</a>], LDAP Protocol
509 Mechanisms, and LDAP Syntax [<a href="./rfc4520" title="&quot;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)&quot;">RFC4520</a>].
510
511 Expert Review (or Designated Expert) - approval by a Designated
512 Expert is required. The required documentation and review
513 criteria for use by the Designated Expert should be provided
514 when defining the registry. For example, see Sections <a href="#section-6">6</a> and
515 7.2 in [<a href="./rfc3748" title="&quot;Extensible Authentication Protocol (EAP)&quot;">RFC3748</a>].
516
517 Examples: EAP Method Types [<a href="./rfc3748" title="&quot;Extensible Authentication Protocol (EAP)&quot;">RFC3748</a>], HTTP Digest AKA
518 algorithm versions [<a href="./rfc4169" title="&quot;Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2&quot;">RFC4169</a>], URI schemes [<a href="./rfc4395" title="&quot;Guidelines and Registration Procedures for New URI Schemes&quot;">RFC4395</a>], GEOPRIV
519 Location Types [<a href="./rfc4589" title="&quot;Location Types Registry&quot;">RFC4589</a>].
520
521 Specification Required - Values and their meanings must be
522 documented in a permanent and readily available public
523 specification, in sufficient detail so that interoperability
524 between independent implementations is possible. When used,
525 Specification Required also implies use of a Designated
526 Expert, who will review the public specification and
527 evaluate whether it is sufficiently clear to allow
528 interoperable implementations. The intention behind
529 "permanent and readily available" is that a document can
530 reasonably be expected to be findable and retrievable long
531 after IANA assignment of the requested value. Publication
532 of an RFC is an ideal means of achieving this requirement,
533 but Specification Required is intended to also cover the
534 case of a document published outside of the RFC path. For
535 RFC publication, the normal RFC review process is expected
536 to provide the necessary review for interoperability, though
537 the Designated Expert may be a particularly well-qualified
538 person to perform such a review.
539
540 Examples: Diffserv-aware TE Bandwidth Constraints Model
541 Identifiers [<a href="./rfc4124" title="&quot;Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering&quot;">RFC4124</a>], TLS ClientCertificateType Identifiers
542 [<a href="./rfc4346" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.1&quot;">RFC4346</a>], ROHC Profile Identifiers [<a href="./rfc4995" title="&quot;The RObust Header Compression (ROHC) Framework&quot;">RFC4995</a>].
543
544 RFC Required - RFC publication (either as an IETF submission or as
545 an RFC Editor Independent submission [<a href="./rfc3932" title="&quot;The IESG and RFC Editor Documents: Procedures&quot;">RFC3932</a>]) suffices.
546 Unless otherwise specified, any type of RFC is sufficient
547 (e.g., Informational, Experimental, Standards Track, etc.).
548
549
550
551
552
553
554
555
556 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
559
560
561 IETF Review - (Formerly called "IETF Consensus" in
562 [<a href="#ref-IANA-CONSIDERATIONS" title="">IANA-CONSIDERATIONS</a>]) New values are assigned only through
563 RFCs that have been shepherded through the IESG as AD-
564 Sponsored or IETF WG Documents [<a href="./rfc3932" title="&quot;The IESG and RFC Editor Documents: Procedures&quot;">RFC3932</a>] [<a href="./rfc3978" title="&quot;IETF Rights in Contributions&quot;">RFC3978</a>]. The
565 intention is that the document and proposed assignment will
566 be reviewed by the IESG and appropriate IETF WGs (or
567 experts, if suitable working groups no longer exist) to
568 ensure that the proposed assignment will not negatively
569 impact interoperability or otherwise extend IETF protocols
570 in an inappropriate or damaging manner.
571
572 To ensure adequate community review, such documents are
573 shepherded through the IESG as AD-sponsored (or WG)
574 documents with an IETF Last Call.
575
576 Examples: IPSECKEY Algorithm Types [<a href="./rfc4025" title="&quot;A Method for Storing IPsec Keying Material in DNS&quot;">RFC4025</a>],
577 Accounting-Auth-Method AVP values in DIAMETER [<a href="./rfc4005" title="&quot;Diameter Network Access Server Application&quot;">RFC4005</a>], TLS
578 Handshake Hello Extensions [<a href="./rfc4366" title="&quot;Transport Layer Security (TLS) Extensions&quot;">RFC4366</a>].
579
580 Standards Action - Values are assigned only for Standards Track
581 RFCs approved by the IESG.
582
583 Examples: BGP message types [<a href="./rfc4271" title="&quot;A Border Gateway Protocol 4 (BGP-4)&quot;">RFC4271</a>], Mobile Node
584 Identifier option types [<a href="./rfc4283" title="&quot;Mobile Node Identifier Option for Mobile IPv6 (MIPv6)&quot;">RFC4283</a>], DCCP Packet Types
585 [<a href="./rfc4340" title="&quot;Datagram Congestion Control Protocol (DCCP)&quot;">RFC4340</a>].
586
587 IESG Approval - New assignments may be approved by the IESG.
588 Although there is no requirement that the request be
589 documented in an RFC, the IESG has discretion to request
590 documents or other supporting materials on a case-by-case
591 basis.
592
593 IESG Approval is not intended to be used often or as a
594 "common case"; indeed, it has seldom been used in practice
595 during the period <a href="./rfc2434">RFC 2434</a> was in effect. Rather, it is
596 intended to be available in conjunction with other policies
597 as a fall-back mechanism in the case where one of the other
598 allowable approval mechanisms cannot be employed in a timely
599 fashion or for some other compelling reason. IESG Approval
600 is not intended to circumvent the public review processes
601 implied by other policies that could have been employed for
602 a particular assignment. IESG Approval would be
603 appropriate, however, in cases where expediency is desired
604 and there is strong consensus for making the assignment
605 (e.g., WG consensus).
606
607
608
609
610
611
612 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
615
616
617 The following guidelines are suggested for any evaluation
618 under IESG Approval:
619
620 - The IESG can (and should) reject a request if another path
621 for registration is available that is more appropriate and
622 there is no compelling reason to use that path.
623
624 - Before approving a request, the community should be
625 consulted, via a "call for comments" that provides as much
626 information as is reasonably possible about the request.
627
628 Examples: IPv4 Multicast address assignments [<a href="./rfc3171" title="&quot;IANA Guidelines for IPv4 Multicast Address Assignments&quot;">RFC3171</a>], IPv4
629 IGMP Type and Code values [<a href="./rfc3228" title="&quot;IANA Considerations for IPv4 Internet Group Management Protocol (IGMP)&quot;">RFC3228</a>], Mobile IPv6 Mobility
630 Header Type and Option values [<a href="./rfc3775" title="&quot;Mobility Support in IPv6&quot;">RFC3775</a>].
631
632 It should be noted that it often makes sense to partition a namespace
633 into multiple categories, with assignments within each category
634 handled differently. For example, many protocols now partition
635 namespaces into two (or even more) parts, where one range is reserved
636 for Private or Experimental Use, while other ranges are reserved for
637 globally unique assignments assigned following some review process.
638 Dividing a namespace into ranges makes it possible to have different
639 policies in place for different ranges.
640
641 Examples: LDAP [<a href="./rfc4520" title="&quot;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)&quot;">RFC4520</a>], Pseudowire Edge to Edge Emulation (PWE3)
642 [<a href="./rfc4446" title="&quot;IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)&quot;">RFC4446</a>].
643
644 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. What to Put in Documents That Create a Registry</span>
645
646 The previous sections presented some issues that should be considered
647 in formulating a policy for assigning values in namespaces. It is
648 the working group and/or document author's job to formulate an
649 appropriate policy and specify it in the appropriate document. In
650 almost all cases, having an explicit "IANA Considerations" section is
651 appropriate. The following and later sections define what is needed
652 for the different types of IANA actions.
653
654 Documents that create a new namespace (or modify the definition of an
655 existing space) and that expect IANA to play a role in maintaining
656 that space (e.g., serving as a repository for registered values) MUST
657 provide clear instructions on details of the namespace. In
658 particular, instructions MUST include:
659
660 1) The name of the registry (or sub-registry) being created and/or
661 maintained. The name will appear on the IANA web page and will
662 be referred to in future documents that need to allocate a
663 value from the new space. The full name (and abbreviation, if
664 appropriate) should be provided. It is highly desirable that
665
666
667
668 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
671
672
673 the chosen name not be easily confusable with the name of
674 another registry. When creating a sub-registry, the registry
675 that it is a part of should be clearly identified. When
676 referring to an already existing registry, providing a URL to
677 precisely identify the registry is helpful. All such URLs,
678 however, will be removed from the RFC prior to final
679 publication. For example, documents could contain: [TO BE
680 REMOVED: This registration should take place at the following
681 location: <a href="http://www.iana">http://www.iana</a>.org/assignments/foobar-registry]
682
683 2) What information must be provided as part of a request in order
684 to assign a new value. This information may include the need
685 to document relevant security considerations, if any.
686
687 3) The review process that will apply to all future requests for a
688 value from the namespace.
689
690 Note: When a Designated Expert is used, documents MUST NOT name
691 the Designated Expert in the document itself; instead, the name
692 should be relayed to the appropriate Area Director at the time
693 the document is sent to the IESG for approval.
694
695 If the request should also be reviewed on a specific public
696 mailing list (such as the [email protected] for media types),
697 that mailing address should be specified. Note, however, that
698 when mailing lists are specified, the requirement for a
699 Designated Expert MUST also be specified (see <a href="#section-3">Section 3</a>).
700
701 If IANA is expected to make assignments without requiring an
702 outside review, sufficient guidance MUST be provided so that
703 the requests can be evaluated with minimal subjectivity.
704
705 4) The size, format, and syntax of registry entries. When
706 creating a new name/number space, authors must describe any
707 technical requirements on registry (and sub-registry) values
708 (e.g., valid ranges for integers, length limitations on
709 strings, etc.) as well as the exact format in which registry
710 values should be displayed. For number assignments, one should
711 specify whether values are to be recorded in decimal,
712 hexadecimal, or some other format. For strings, the encoding
713 format should be specified (e.g., ASCII, UTF8, etc.). Authors
714 should also clearly specify what fields to record in the
715 registry.
716
717 5) Initial assignments and reservations. Clear instructions
718 should be provided to identify any initial assignments or
719 registrations. In addition, any ranges that are to be reserved
720
721
722
723
724 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
727
728
729 for "Private Use", "Reserved", "Unassigned", etc. should be
730 clearly indicated.
731
732 When specifying the process for making future assignments, it is
733 quite acceptable to pick one (or more) of the example policies listed
734 in <a href="#section-4.1">Section 4.1</a> and refer to it by name. Indeed, this is the
735 preferred mechanism in those cases where the sample policies provide
736 the desired level of review. It is also acceptable to cite one of
737 the above policies and include additional guidelines for what kind of
738 considerations should be taken into account by the review process.
739 For example, RADIUS [<a href="./rfc3575" title="&quot;IANA Considerations for RADIUS (Remote Authentication Dial In User Service)&quot;">RFC3575</a>] specifies the use of a Designated
740 Expert, but includes specific additional criteria the Designated
741 Expert should follow.
742
743 For example, a document could say something like:
744
745 This document defines a new DHCP option, entitled "FooBar" (see
746 Section y), assigned a value of TBD1 from the DHCP Option space
747 [to be removed upon publication:
748 <a href="http://www.iana">http://www.iana</a>.org/assignments/bootp-dhcp-parameters]
749 [<a href="#ref-DHCP-OPTIONS" title="&quot;DHCP Options and BOOTP Vendor Extensions&quot;">DHCP-OPTIONS</a>] [<a href="#ref-DHCP-IANA" title="&quot;Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types&quot;">DHCP-IANA</a>]:
750
751 Data
752 Tag Name Length Meaning
753 ---- ---- ------ -------
754 TBD1 FooBar N FooBar server
755
756 The FooBar option also defines an 8-bit FooType field, for which
757 IANA is to create and maintain a new sub-registry entitled
758 "FooType values" under the FooBar option. Initial values for the
759 DHCP FooBar FooType registry are given below; future assignments
760 are to be made through Expert Review [<a href="#ref-IANA-CONSIDERATIONS" title="">IANA-CONSIDERATIONS</a>].
761 Assignments consist of a DHCP FooBar FooType name and its
762 associated value.
763
764 Value DHCP FooBar FooType Name Definition
765 ---- ------------------------ ----------
766 0 Reserved
767 1 Frobnitz See Section y.1
768 2 NitzFrob See Section y.2
769 3-254 Unassigned
770 255 Reserved
771
772 For examples of documents that provide detailed guidance to IANA
773 on the issue of assigning numbers, consult [<a href="./rfc2929" title="&quot;Domain Name System (DNS) IANA Considerations&quot;">RFC2929</a>], [<a href="./rfc3575" title="&quot;IANA Considerations for RADIUS (Remote Authentication Dial In User Service)&quot;">RFC3575</a>],
774 [<a href="./rfc3968" title="&quot;The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)&quot;">RFC3968</a>], and [<a href="./rfc4520" title="&quot;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)&quot;">RFC4520</a>].
775
776
777
778
779
780 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
783
784
785 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Updating IANA Guidelines for Existing Registries</span>
786
787 Updating the registration process for an already existing (i.e.,
788 previously created) namespace (whether created explicitly or
789 implicitly) follows a process similar to that used when creating a
790 new namespace. That is, a document is produced that makes reference
791 to the existing namespace and then provides detailed guidelines for
792 handling assignments in each individual namespace. Such documents
793 are normally processed as Best Current Practices (BCPs)
794 [<a href="#ref-IETF-PROCESS" title="&quot;The Internet Standards Process -- Revision 3&quot;">IETF-PROCESS</a>].
795
796 Example documents that updated the guidelines for managing (then)
797 pre-existing registries include: [<a href="./rfc2929" title="&quot;Domain Name System (DNS) IANA Considerations&quot;">RFC2929</a>], [<a href="./rfc3228" title="&quot;IANA Considerations for IPv4 Internet Group Management Protocol (IGMP)&quot;">RFC3228</a>], and [<a href="./rfc3575" title="&quot;IANA Considerations for RADIUS (Remote Authentication Dial In User Service)&quot;">RFC3575</a>].
798
799 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Registering New Values in an Existing Registry</span>
800
801 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. What to Put in Documents When Registering Values</span>
802
803 Often, documents request an assignment from an already existing
804 namespace (i.e., one created by a previously published RFC). In such
805 cases:
806
807 - Documents should clearly identify the namespace in which each
808 value is to be registered. If the registration goes into a
809 sub-registry, the author should clearly describe where the
810 assignment or registration should go. It is helpful to use the
811 exact namespace name as listed on the IANA web page (and
812 defining RFC), and cite the RFC where the namespace is defined.
813
814 Note 1: There is no need to mention what the assignment policy
815 for new assignments is, as that should be clear from the
816 references.
817
818 Note 2: When referring to an existing registry, providing a URL
819 to precisely identify the registry is helpful. Such URLs,
820 however, should usually be removed from the RFC prior to final
821 publication, since IANA URLs are not guaranteed to be stable in
822 the future. In cases where it is important to include a URL in
823 the document, IANA should concur on its inclusion.
824
825 As an example, documents could contain: [TO BE REMOVED: This
826 registration should take place at the following location:
827 <a href="http://www.iana">http://www.iana</a>.org/assignments/foobar-registry]
828
829 - Each value requested should be given a unique reference. When
830 the value is numeric, use the notation: TBD1, TBD2, etc.
831 Throughout the document where an actual IANA-assigned value
832 should be filled in, use the "TBDx" notation. This helps ensure
833
834
835
836 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
839
840
841 that the final RFC has the correct assigned values inserted in
842 all of the relevant places where the value is expected to appear
843 in the final document. For values that are text strings, a
844 specific name can be suggested. IANA will normally assign the
845 name, unless it conflicts with a name already in use.
846
847 - Normally, the values to be used are chosen by IANA and documents
848 should specify values of "TBD". However, in some cases, a value
849 may have been used for testing or in early implementations. In
850 such cases, it is acceptable to include text suggesting what
851 specific value should be used (together with the reason for the
852 choice). For example, one might include the text "the value XXX
853 is suggested as it is used in implementations". However, it
854 should be noted that suggested values are just that; IANA will
855 attempt to assign them, but may find that impossible, if the
856 proposed number has already been assigned for some other use.
857
858 For some registries, IANA has a long-standing policy prohibiting
859 assignment of names or codes on a vanity or organization name
860 basis, e.g., codes are always assigned sequentially unless there
861 is a strong reason for making an exception. Nothing in this
862 document is intended to change those policies or prevent their
863 future application.
864
865 - The IANA Considerations section should summarize all of the IANA
866 actions, with pointers to the relevant sections elsewhere in the
867 document as appropriate. When multiple values are requested, it
868 is generally helpful to include a summary table. It is also
869 helpful for this table to be in the same format as it should
870 appear on the IANA web site. For example:
871
872 Value Description Reference
873 -------- ------------------- ---------
874 TBD1 Foobar [RFCXXXX]
875
876 Note: In cases where authors feel that including the full table is
877 too verbose or repetitive, authors should still include the table,
878 but may include a note asking that the table be removed prior to
879 publication of the final RFC.
880
881 As an example, the following text could be used to request assignment
882 of a DHCPv6 option number:
883
884 IANA has assigned an option code value of TBD1 to the DNS
885 Recursive Name Server option and an option code value of TBD2 to
886 the Domain Search List option from the DHCP option code space
887 defined in <a href="./rfc3315#section-24.3">Section&nbsp;24.3 of RFC 3315</a>.
888
889
890
891
892 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
895
896
897 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Updating Registrations</span>
898
899 Registrations are a request to assign a new value, including the
900 related information needed to evaluate and document the request.
901 Even after a number has been assigned, some types of registrations
902 contain additional information that may need to be updated over time.
903 For example, MIME media types, character sets, and language tags,
904 etc. typically include more information than just the registered
905 value itself. Example information can include point-of-contact
906 information, security issues, pointers to updates, literature
907 references, etc. In such cases, the document defining the namespace
908 must clearly state who is responsible for maintaining and updating a
909 registration. In different cases, it may be appropriate to specify
910 one or more of the following:
911
912 - Let the author update the registration, subject to the same
913 constraints and review as with new registrations.
914
915 - Allow some mechanism to attach comments to the registration, for
916 cases where others have significant objections to claims in a
917 registration, but the author does not agree to change the
918 registration.
919
920 - Designate the IESG, a Designated Expert, or another entity as
921 having the right to change the registrant associated with a
922 registration and any requirements or conditions on doing so.
923 This is mainly to get around the problem when a registrant
924 cannot be reached in order to make necessary updates.
925
926 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Overriding Registration Procedures</span>
927
928 Since <a href="./rfc2434">RFC 2434</a> was published, experience has shown that the
929 documented IANA considerations for individual protocols do not always
930 adequately cover the reality after the protocol is deployed. For
931 example, many older routing protocols do not have documented,
932 detailed IANA considerations. In addition, documented IANA
933 considerations are sometimes found to be too stringent to allow even
934 working group documents (for which there is strong consensus) to
935 obtain code points from IANA in advance of actual RFC publication.
936 In other cases, the documented procedures are unclear or neglected to
937 cover all the cases. In order to allow assignments in individual
938 cases where there is strong IETF consensus that an allocation should
939 go forward, but the documented procedures do not support such an
940 assignment, the IESG is granted authority to approve assignments in
941 such cases. The intention is not to overrule properly documented
942 procedures, or to obviate the need for protocols to properly document
943 their IANA considerations. Instead, the intention is to permit
944 assignments in individual cases where it is obvious that the
945
946
947
948 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
951
952
953 assignment should just be made, but updating the IANA process just to
954 assign a particular code point is viewed as too heavy a burden.
955
956 In general, the IETF would like to see deficient IANA registration
957 procedures for a namespace revised through the IETF standards
958 process, but not at the cost of unreasonable delay for needed
959 assignments. If the IESG has had to take the action in this section,
960 it is a strong indicator that the IANA registration procedures should
961 be updated, possibly in parallel with ongoing protocol work.
962
963 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Miscellaneous Issues</span>
964
965 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. When There Are No IANA Actions</span>
966
967 Before an Internet-Draft can be published as an RFC, IANA needs to
968 know what actions (if any) it needs to perform. Experience has shown
969 that it is not always immediately obvious whether a document has no
970 IANA actions, without reviewing the document in some detail. In
971 order to make it clear to IANA that it has no actions to perform (and
972 that the author has consciously made such a determination), such
973 documents should include an IANA Considerations section that states:
974
975 This document has no IANA actions.
976
977 This statement, or an equivalent, must only be inserted after the WG
978 or individual submitter has carefully verified it to be true. Using
979 such wording as a matter of "boilerplate" or without careful
980 consideration can lead to incomplete or incorrect IANA actions being
981 performed.
982
983 If a specification makes use of values from a namespace that is not
984 managed by IANA, it may be useful to note this fact, e.g., with
985 wording such as:
986
987 The values of the Foobar parameter are assigned by the Barfoo
988 registry on behalf of the Rabfoo Forum. Therefore, this document
989 has no IANA actions.
990
991 In some cases, the absence of IANA-assigned values may be considered
992 valuable information for future readers; in other cases, it may be
993 considered of no value once the document has been approved, and may
994 be removed before archival publication. This choice should be made
995 clear in the draft, for example, by including a sentence such as
996
997 [RFC Editor: please remove this section prior to publication.]
998
999 or
1000
1001
1002
1003
1004 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1007
1008
1009 [RFC Editor: please do not remove this section.]
1010
1011 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Namespaces Lacking Documented Guidance</span>
1012
1013 For all existing RFCs that either explicitly or implicitly rely on
1014 IANA to evaluate assignments without specifying a precise evaluation
1015 policy, IANA (in consultation with the IESG) will continue to decide
1016 what policy is appropriate. Changes to existing policies can always
1017 be initiated through the normal IETF consensus process.
1018
1019 All future RFCs that either explicitly or implicitly rely on IANA to
1020 register or otherwise manage namespace assignments MUST provide
1021 guidelines for managing the namespace.
1022
1023 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. After-the-Fact Registrations</span>
1024
1025 Occasionally, IANA becomes aware that an unassigned value from a
1026 managed namespace is in use on the Internet or that an assigned value
1027 is being used for a different purpose than originally registered.
1028 IANA will not condone such misuse; i.e., procedures of the type
1029 described in this document MUST be applied to such cases. In the
1030 absence of specifications to the contrary, values may only be
1031 reassigned for a different purpose with the consent of the original
1032 assignee (when possible) and with due consideration of the impact of
1033 such a reassignment. In cases of likely controversy, consultation
1034 with the IESG is advised.
1035
1036 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Reclaiming Assigned Values</span>
1037
1038 Reclaiming previously assigned values for reuse is tricky, because
1039 doing so can lead to interoperability problems with deployed systems
1040 still using the assigned values. Moreover, it can be extremely
1041 difficult to determine the extent of deployment of systems making use
1042 of a particular value. However, in cases where the namespace is
1043 running out of unassigned values and additional ones are needed, it
1044 may be desirable to attempt to reclaim unused values. When
1045 reclaiming unused values, the following (at a minimum) should be
1046 considered:
1047
1048 - Attempts should be made to contact the original party to which a
1049 value is assigned, to determine if the value was ever used, and
1050 if so, the extent of deployment. (In some cases, products were
1051 never shipped or have long ceased being used. In other cases,
1052 it may be known that a value was never actually used at all.)
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1063
1064
1065 - Reassignments should not normally be made without the
1066 concurrence of the original requester. Reclamation under such
1067 conditions should only take place where there is strong evidence
1068 that a value is not widely used, and the need to reclaim the
1069 value outweighs the cost of a hostile reclamation. In any case,
1070 IESG Approval is needed in this case.
1071
1072 - It may be appropriate to write up the proposed action and
1073 solicit comments from relevant user communities. In some cases,
1074 it may be appropriate to write an RFC that goes through a formal
1075 IETF process (including IETF Last Call) as was done when DHCP
1076 reclaimed some of its "Private Use" options [<a href="./rfc3942" title="&quot;Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options&quot;">RFC3942</a>].
1077
1078 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Appeals</span>
1079
1080 Appeals of registration decisions made by IANA can be made using the
1081 normal IETF appeals process as described in Section 6.5 of
1082 [<a href="#ref-IETF-PROCESS" title="&quot;The Internet Standards Process -- Revision 3&quot;">IETF-PROCESS</a>]. Specifically, appeals should be directed to the
1083 IESG, followed (if necessary) by an appeal to the IAB, etc.
1084
1085 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Mailing Lists</span>
1086
1087 All IETF mailing lists associated with evaluating or discussing
1088 assignment requests as described in this document are subject to
1089 whatever rules of conduct and methods of list management are
1090 currently defined by Best Current Practices or by IESG decision.
1091
1092 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
1093
1094 Information that creates or updates a registration needs to be
1095 authenticated and authorized. IANA updates registries according to
1096 instructions in published RFCs and from the IESG. It also may accept
1097 clarifications from document authors, relevant WG chairs, Designated
1098 Experts, and mail list participants, too.
1099
1100 Information concerning possible security vulnerabilities of a
1101 protocol may change over time. Likewise, security vulnerabilities
1102 related to how an assigned number is used (e.g., if it identifies a
1103 protocol) may change as well. As new vulnerabilities are discovered,
1104 information about such vulnerabilities may need to be attached to
1105 existing registrations, so that users are not misled as to the true
1106 security issues surrounding the use of a registered number.
1107
1108 An analysis of security issues is generally required for all
1109 protocols that make use of parameters (data types, operation codes,
1110 keywords, etc.) used in IETF protocols or registered by IANA. Such
1111 security considerations are usually included in the protocol document
1112 [<a href="./rfc3552" title="&quot;Guidelines for Writing RFC Text on Security Considerations&quot;">RFC3552</a>]. It is the responsibility of the IANA considerations
1113
1114
1115
1116 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1119
1120
1121 associated with a particular registry to specify what (if any)
1122 security considerations must be provided when assigning new values,
1123 and the process for reviewing such claims.
1124
1125 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Changes Relative to <a href="./rfc2434">RFC 2434</a></span>
1126
1127 Changes include:
1128
1129 - Major reordering of text to expand descriptions and to better
1130 group topics such as "updating registries" vs. "creating new
1131 registries", in order to make it easier for authors to find the
1132 text most applicable to their needs.
1133
1134 - Numerous editorial changes to improve readability.
1135
1136 - Changed the term "IETF Consensus" to "IETF Review" and added
1137 more clarifications. History has shown that people see the
1138 words "IETF Consensus" (without consulting the actual
1139 definition) and are quick to make incorrect assumptions about
1140 what the term means in the context of IANA Considerations.
1141
1142 - Added "RFC Required" to list of defined policies.
1143
1144 - Much more explicit directions and examples of "what to put in
1145 RFCs".
1146
1147 - "Specification Required" now implies use of a Designated Expert
1148 to evaluate specs for sufficient clarity.
1149
1150 - Significantly changed the wording in <a href="#section-3">Section 3</a>. Main purpose is
1151 to make clear that Expert Reviewers are accountable to the
1152 community, and to provide some guidance for review criteria in
1153 the default case.
1154
1155 - Changed wording to remove any special appeals path. The normal
1156 <a href="./rfc2026">RFC 2026</a> appeals path is used.
1157
1158 - Added a section about reclaiming unused value.
1159
1160 - Added a section on after-the-fact registrations.
1161
1162 - Added a section indicating that mailing lists used to evaluate
1163 possible assignments (e.g., by a Designated Expert) are subject
1164 to normal IETF rules.
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
1178
1179 This document has benefited from specific feedback from Jari Arkko,
1180 Marcelo Bagnulo Braun, Brian Carpenter, Michelle Cotton, Spencer
1181 Dawkins, Barbara Denny, Miguel Garcia, Paul Hoffman, Russ Housley,
1182 John Klensin, Allison Mankin, Blake Ramsdell, Mark Townsley, Magnus
1183 Westerlund, and Bert Wijnen.
1184
1185 The original acknowledgments section in <a href="./rfc2434">RFC 2434</a> was:
1186
1187 Jon Postel and Joyce Reynolds provided a detailed explanation on what
1188 IANA needs in order to manage assignments efficiently, and patiently
1189 provided comments on multiple versions of this document. Brian
1190 Carpenter provided helpful comments on earlier versions of the
1191 document. One paragraph in the Security Considerations section was
1192 borrowed from [<a href="#ref-MIME-REG" title="&quot;Media Type Specifications and Registration Procedures&quot;">MIME-REG</a>].
1193
1194 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
1195
1196 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
1197
1198 [<a id="ref-KEYWORDS">KEYWORDS</a>] Bradner, S., "Key words for use in RFCs to
1199 Indicate Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
1200 March 1997.
1201
1202 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
1203
1204 [<a id="ref-ASSIGNED">ASSIGNED</a>] Reynolds, J., Ed., "Assigned Numbers: <a href="./rfc1700">RFC 1700</a>
1205 is Replaced by an On-line Database", <a href="./rfc3232">RFC 3232</a>,
1206 January 2002.
1207
1208 [<a id="ref-DHCP-OPTIONS">DHCP-OPTIONS</a>] Alexander, S. and R. Droms, "DHCP Options and
1209 BOOTP Vendor Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
1210
1211 [<a id="ref-DHCP-IANA">DHCP-IANA</a>] Droms, R., "Procedures and IANA Guidelines for
1212 Definition of New DHCP Options and Message
1213 Types", <a href="https://www.rfc-editor.org/bcp/bcp43">BCP 43</a>, <a href="./rfc2939">RFC 2939</a>, September 2000.
1214
1215 [<a id="ref-EXPERIMENTATION">EXPERIMENTATION</a>] Narten, T., "Assigning Experimental and Testing
1216 Numbers Considered Useful", <a href="https://www.rfc-editor.org/bcp/bcp82">BCP 82</a>, <a href="./rfc3692">RFC 3692</a>,
1217 January 2004.
1218
1219 [<a id="ref-IANA-CONSIDERATIONS">IANA-CONSIDERATIONS</a>] Narten, T. and H. Alvestrand, "Guidelines for
1220 Writing an IANA Considerations Section in
1221 RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998.
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1231
1232
1233 [<a id="ref-IANA-MOU">IANA-MOU</a>] Carpenter, B., Baker, F., and M. Roberts,
1234 "Memorandum of Understanding Concerning the
1235 Technical Work of the Internet Assigned Numbers
1236 Authority", <a href="./rfc2860">RFC 2860</a>, June 2000.
1237
1238 [<a id="ref-IETF-PROCESS">IETF-PROCESS</a>] Bradner, S., "The Internet Standards Process --
1239 Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
1240
1241 [<a id="ref-IP">IP</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC</a>
1242 <a href="./rfc791">791</a>, September 1981.
1243
1244 [<a id="ref-IPSEC">IPSEC</a>] Kent, S. and K. Seo, "Security Architecture for
1245 the Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December
1246 2005.
1247
1248 [<a id="ref-MIME-REG">MIME-REG</a>] Freed, N. and J. Klensin, "Media Type
1249 Specifications and Registration Procedures",
1250 <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
1251
1252 [<a id="ref-PROTOCOL-EXT">PROTOCOL-EXT</a>] Carpenter, B. and B. Aboba, "Design
1253 Considerations for Protocol Extensions", Work
1254 in Progress, December 2007.
1255
1256 [<a id="ref-RFC2929">RFC2929</a>] Eastlake 3rd, D., Brunner-Williams, E., and B.
1257 Manning, "Domain Name System (DNS) IANA
1258 Considerations", <a href="https://www.rfc-editor.org/bcp/bcp42">BCP 42</a>, <a href="./rfc2929">RFC 2929</a>, September
1259 2000.
1260
1261 [<a id="ref-RFC3171">RFC3171</a>] Albanna, Z., Almeroth, K., Meyer, D., and M.
1262 Schipper, "IANA Guidelines for IPv4 Multicast
1263 Address Assignments", <a href="https://www.rfc-editor.org/bcp/bcp51">BCP 51</a>, <a href="./rfc3171">RFC 3171</a>, August
1264 2001.
1265
1266 [<a id="ref-RFC3228">RFC3228</a>] Fenner, B., "IANA Considerations for IPv4
1267 Internet Group Management Protocol (IGMP)", <a href="https://www.rfc-editor.org/bcp/bcp57">BCP</a>
1268 <a href="https://www.rfc-editor.org/bcp/bcp57">57</a>, <a href="./rfc3228">RFC 3228</a>, February 2002.
1269
1270 [<a id="ref-RFC3552">RFC3552</a>] Rescorla, E. and B. Korver, "Guidelines for
1271 Writing RFC Text on Security Considerations",
1272 <a href="https://www.rfc-editor.org/bcp/bcp72">BCP 72</a>, <a href="./rfc3552">RFC 3552</a>, July 2003.
1273
1274 [<a id="ref-RFC3575">RFC3575</a>] Aboba, B., "IANA Considerations for RADIUS
1275 (Remote Authentication Dial In User Service)",
1276 <a href="./rfc3575">RFC 3575</a>, July 2003.
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1287
1288
1289 [<a id="ref-RFC3748">RFC3748</a>] Aboba, B., Blunk, L., Vollbrecht, J., Carlson,
1290 J., and H. Levkowetz, Ed., "Extensible
1291 Authentication Protocol (EAP)", <a href="./rfc3748">RFC 3748</a>, June
1292 2004.
1293
1294 [<a id="ref-RFC3775">RFC3775</a>] Johnson, D., Perkins, C., and J. Arkko,
1295 "Mobility Support in IPv6", <a href="./rfc3775">RFC 3775</a>, June
1296 2004.
1297
1298 [<a id="ref-RFC3932">RFC3932</a>] Alvestrand, H., "The IESG and RFC Editor
1299 Documents: Procedures", <a href="https://www.rfc-editor.org/bcp/bcp92">BCP 92</a>, <a href="./rfc3932">RFC 3932</a>,
1300 October 2004.
1301
1302 [<a id="ref-RFC3942">RFC3942</a>] Volz, B., "Reclassifying Dynamic Host
1303 Configuration Protocol version 4 (DHCPv4)
1304 Options", <a href="./rfc3942">RFC 3942</a>, November 2004.
1305
1306 [<a id="ref-RFC3968">RFC3968</a>] Camarillo, G., "The Internet Assigned Number
1307 Authority (IANA) Header Field Parameter
1308 Registry for the Session Initiation Protocol
1309 (SIP)", <a href="https://www.rfc-editor.org/bcp/bcp98">BCP 98</a>, <a href="./rfc3968">RFC 3968</a>, December 2004.
1310
1311 [<a id="ref-RFC3978">RFC3978</a>] Bradner, S., Ed., "IETF Rights in
1312 Contributions", <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, <a href="./rfc3978">RFC 3978</a>, March 2005.
1313
1314 [<a id="ref-RFC4005">RFC4005</a>] Calhoun, P., Zorn, G., Spence, D., and D.
1315 Mitton, "Diameter Network Access Server
1316 Application", <a href="./rfc4005">RFC 4005</a>, August 2005.
1317
1318 [<a id="ref-RFC4025">RFC4025</a>] Richardson, M., "A Method for Storing IPsec
1319 Keying Material in DNS", <a href="./rfc4025">RFC 4025</a>, March 2005.
1320
1321 [<a id="ref-RFC4044">RFC4044</a>] McCloghrie, K., "Fibre Channel Management MIB",
1322 <a href="./rfc4044">RFC 4044</a>, May 2005.
1323
1324 [<a id="ref-RFC4124">RFC4124</a>] Le Faucheur, F., Ed., "Protocol Extensions for
1325 Support of Diffserv-aware MPLS Traffic
1326 Engineering", <a href="./rfc4124">RFC 4124</a>, June 2005.
1327
1328 [<a id="ref-RFC4169">RFC4169</a>] Torvinen, V., Arkko, J., and M. Naslund,
1329 "Hypertext Transfer Protocol (HTTP) Digest
1330 Authentication Using Authentication and Key
1331 Agreement (AKA) Version-2", <a href="./rfc4169">RFC 4169</a>, November
1332 2005.
1333
1334 [<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Ed., Li, T., Ed., and S. Hares,
1335 Ed., "A Border Gateway Protocol 4 (BGP-4)", <a href="./rfc4271">RFC</a>
1336 <a href="./rfc4271">4271</a>, January 2006.
1337
1338
1339
1340 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1343
1344
1345 [<a id="ref-RFC4283">RFC4283</a>] Patel, A., Leung, K., Khalil, M., Akhtar, H.,
1346 and K. Chowdhury, "Mobile Node Identifier
1347 Option for Mobile IPv6 (MIPv6)", <a href="./rfc4283">RFC 4283</a>,
1348 November 2005.
1349
1350 [<a id="ref-RFC4306">RFC4306</a>] Kaufman, C., Ed., "Internet Key Exchange
1351 (IKEv2) Protocol", <a href="./rfc4306">RFC 4306</a>, December 2005.
1352
1353 [<a id="ref-RFC4340">RFC4340</a>] Kohler, E., Handley, M., and S. Floyd,
1354 "Datagram Congestion Control Protocol (DCCP)",
1355 <a href="./rfc4340">RFC 4340</a>, March 2006.
1356
1357 [<a id="ref-RFC4346">RFC4346</a>] Dierks, T. and E. Rescorla, "The Transport
1358 Layer Security (TLS) Protocol Version 1.1", <a href="./rfc4346">RFC</a>
1359 <a href="./rfc4346">4346</a>, April 2006.
1360
1361 [<a id="ref-RFC4366">RFC4366</a>] Blake-Wilson, S., Nystrom, M., Hopwood, D.,
1362 Mikkelsen, J., and T. Wright, "Transport Layer
1363 Security (TLS) Extensions", <a href="./rfc4366">RFC 4366</a>, April
1364 2006.
1365
1366 [<a id="ref-RFC4395">RFC4395</a>] Hansen, T., Hardie, T., and L. Masinter,
1367 "Guidelines and Registration Procedures for New
1368 URI Schemes", <a href="https://www.rfc-editor.org/bcp/bcp115">BCP 115</a>, <a href="./rfc4395">RFC 4395</a>, February 2006.
1369
1370 [<a id="ref-RFC4422">RFC4422</a>] Melnikov, A., Ed., and K. Zeilenga, Ed.,
1371 "Simple Authentication and Security Layer
1372 (SASL)", <a href="./rfc4422">RFC 4422</a>, June 2006.
1373
1374 [<a id="ref-RFC4446">RFC4446</a>] Martini, L., "IANA Allocations for Pseudowire
1375 Edge to Edge Emulation (PWE3)", <a href="https://www.rfc-editor.org/bcp/bcp116">BCP 116</a>, <a href="./rfc4446">RFC</a>
1376 <a href="./rfc4446">4446</a>, April 2006.
1377
1378 [<a id="ref-RFC4520">RFC4520</a>] Zeilenga, K., "Internet Assigned Numbers
1379 Authority (IANA) Considerations for the
1380 Lightweight Directory Access Protocol (LDAP)",
1381 <a href="https://www.rfc-editor.org/bcp/bcp64">BCP 64</a>, <a href="./rfc4520">RFC 4520</a>, June 2006.
1382
1383 [<a id="ref-RFC4589">RFC4589</a>] Schulzrinne, H. and H. Tschofenig, "Location
1384 Types Registry", <a href="./rfc4589">RFC 4589</a>, July 2006.
1385
1386 [<a id="ref-RFC4727">RFC4727</a>] Fenner, B., "Experimental Values In IPv4, IPv6,
1387 ICMPv4, ICMPv6, UDP, and TCP Headers", <a href="./rfc4727">RFC</a>
1388 <a href="./rfc4727">4727</a>, November 2006.
1389
1390 [<a id="ref-RFC4995">RFC4995</a>] Jonsson, L-E., Pelletier, G., and K. Sandlund,
1391 "The RObust Header Compression (ROHC)
1392 Framework", <a href="./rfc4995">RFC 4995</a>, July 2007.
1393
1394
1395
1396 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1399
1400
1401 Authors' Addresses
1402
1403 Thomas Narten
1404 IBM Corporation
1405 3039 Cornwallis Ave.
1406 PO Box 12195 - BRQA/502
1407 Research Triangle Park, NC 27709-2195
1408
1409 Phone: 919-254-7798
1410 EMail: [email protected]
1411
1412
1413 Harald Tveit Alvestrand
1414 Google
1415 Beddingen 10
1416 Trondheim, 7014
1417 Norway
1418
1419 EMail: [email protected]
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Narten &amp; Alvestrand Best Current Practice [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc5226">RFC 5226</a> IANA Considerations Section in RFCs May 2008</span>
1455
1456
1457 Full Copyright Statement
1458
1459 Copyright (C) The IETF Trust (2008).
1460
1461 This document is subject to the rights, licenses and restrictions
1462 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
1463 retain all their rights.
1464
1465 This document and the information contained herein are provided on an
1466 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1467 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1468 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1469 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1470 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1471 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1472
1473 Intellectual Property
1474
1475 The IETF takes no position regarding the validity or scope of any
1476 Intellectual Property Rights or other rights that might be claimed to
1477 pertain to the implementation or use of the technology described in
1478 this document or the extent to which any license under such rights
1479 might or might not be available; nor does it represent that it has
1480 made any independent effort to identify any such rights. Information
1481 on the procedures with respect to rights in RFC documents can be
1482 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1483
1484 Copies of IPR disclosures made to the IETF Secretariat and any
1485 assurances of licenses to be made available, or the result of an
1486 attempt made to obtain a general license or permission for the use of
1487 such proprietary rights by implementers or users of this
1488 specification can be obtained from the IETF on-line IPR repository at
1489 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1490
1491 The IETF invites any interested party to bring to its attention any
1492 copyrights, patents or patent applications, or other proprietary
1493 rights that may cover technology that may be required to implement
1494 this standard. Please address the information to the IETF at
1495 [email protected].
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 Narten &amp; Alvestrand Best Current Practice [Page 27]
1509 </pre>