Debian Codegraph @

rfc7120.html

raw
1 <pre>Internet Engineering Task Force (IETF) M. Cotton
2 Request for Comments: 7120 ICANN
3 BCP: 100 January 2014
4 Obsoletes: <a href="./rfc4020">4020</a>
5 Category: Best Current Practice
6 ISSN: 2070-1721
7
8
9 <span class="h1">Early IANA Allocation of Standards Track Code Points</span>
10
11 Abstract
12
13 This memo describes the process for early allocation of code points
14 by IANA from registries for which "Specification Required", "RFC
15 Required", "IETF Review", or "Standards Action" policies apply. This
16 process can be used to alleviate the problem where code point
17 allocation is needed to facilitate desired or required implementation
18 and deployment experience prior to publication of an RFC, which would
19 normally trigger code point allocation. The procedures in this
20 document are intended to apply only to IETF Stream documents.
21
22 This document obsoletes <a href="./rfc4020">RFC 4020</a>.
23
24 Status of This Memo
25
26 This memo documents an Internet Best Current Practice.
27
28 This document is a product of the Internet Engineering Task Force
29 (IETF). It represents the consensus of the IETF community. It has
30 received public review and has been approved for publication by the
31 Internet Engineering Steering Group (IESG). Further information on
32 BCPs is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
33
34 Information about the current status of this document, any errata,
35 and how to provide feedback on it may be obtained at
36 <a href="http://www.rfc-editor.org/info/rfc7120">http://www.rfc-editor.org/info/rfc7120</a>.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2014 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. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-2">2</a>. Conditions for Early Allocation . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
76 <a href="#section-3">3</a>. Process for Early Allocation . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
77 <a href="#section-3.1">3.1</a>. Request . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
78 <a href="#section-3.2">3.2</a>. Follow-Up . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
79 <a href="#section-3.3">3.3</a>. Expiry . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
80 <a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
81 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
82 <a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
83 <a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
84 <a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
85 <a href="#appendix-A">Appendix A</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 In protocol specifications documented in RFCs, there is often a need
116 to allocate code points for various objects, messages, or other
117 protocol entities so that implementations can interoperate. Many of
118 these code point spaces have registries handled by the Internet
119 Assigned Number Authority (IANA). Several IETF policies for IANA
120 allocation of protocol parameters are described in <a href="./rfc5226">RFC 5226</a>
121 [<a href="./rfc5226" title="">RFC5226</a>]. Some of them, such as "First Come First Served" or
122 "Expert Review", do not require a formal IETF action before the IANA
123 performs allocation. However, in situations where code points are a
124 scarce resource and/or the IETF community has consensus to retain
125 tight control of the registry content, policies such as "IETF Review"
126 (formerly "IETF Consensus"), or "Standards Action" have been used.
127 Such allocation policies present a problem in situations where
128 implementation and/or deployment experience are desired or required
129 before the document becomes an RFC.
130
131 To break the deadlock, document authors often choose some "seemingly
132 unused" code points, often by selecting the next available value from
133 the registry; this is problematic because these may turn out to be
134 different from those later assigned by IANA. To make this problem
135 worse, "pre-RFC" implementations are often developed and deployed
136 based on these code point selections. This creates several potential
137 interoperability problems between early implementations and
138 implementations of the final standard, as described below:
139
140 1. IANA allocates code points different from those that early
141 implementations assumed would be allocated. Early
142 implementations won't interoperate with standard ones.
143
144 2. IANA allocates code points for one extension while a "pre-RFC"
145 implementation of a different extension chooses the same code
146 point. The different extensions will collide on the same code
147 point in the field.
148
149 This gets in the way of the main purpose of standards; namely, to
150 facilitate interoperable implementations.
151
152 It is easy to say that pre-RFC implementations should be kept private
153 and should not be deployed; however, both the length of the standards
154 process and the immense value of early implementations and early
155 deployments suggest that finding a better solution is worthwhile. As
156 an example, in the case of documents produced by Working Groups in
157 the Routing Area, a pre-RFC implementation is highly desirable and
158 sometimes even required [<a href="./rfc4794" title="&quot;RFC 1264 Is Obsolete&quot;">RFC4794</a>], and early deployments provide
159 useful feedback on the technical and operational quality of the
160 specification.
161
162
163
164 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
167
168
169 This memo addresses the early allocation of code points so that
170 reservations are made in the IANA registries before the publication
171 of an RFC. The early allocation mechanisms are applied only to
172 spaces whose allocation policy is "Specification Required" (where an
173 RFC is used as the stable reference), "RFC Required", "IETF Review",
174 or "Standards Action". For an explanation of these allocation
175 policies, see [<a href="./rfc5226" title="">RFC5226</a>].
176
177 A policy for IANA early allocations was previously described in
178 [<a href="./rfc4020" title="&quot;Early IANA Allocation of Standards Track Code Points&quot;">RFC4020</a>]. This document obsoletes <a href="./rfc4020">RFC 4020</a> and includes other
179 registration procedures regarding the types of registries that can
180 qualify for early allocation. The procedures in this document are
181 intended to apply only to IETF Stream documents.
182
183 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conditions for Early Allocation</span>
184
185 The following conditions must hold before a request for early
186 allocation of code points will be considered by IANA:
187
188 a. The code points must be from a space designated as "RFC
189 Required", "IETF Review", or "Standards Action". Additionally,
190 requests for early assignment of code points from a
191 "Specification Required" registry are allowed if the
192 specification will be published as an RFC.
193
194 b. The format, semantics, processing, and other rules related to
195 handling the protocol entities defined by the code points
196 (henceforth called "specifications") must be adequately described
197 in an Internet-Draft.
198
199 c. The specifications of these code points must be stable; i.e., if
200 there is a change, implementations based on the earlier and later
201 specifications must be seamlessly interoperable.
202
203 d. The Working Group chairs and Area Directors (ADs) judge that
204 there is sufficient interest in the community for early (pre-RFC)
205 implementation and deployment, or that failure to make an early
206 allocation might lead to contention for the code point in the
207 field.
208
209 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Process for Early Allocation</span>
210
211 There are three processes associated with early allocation: making
212 the request for code points; following up on the request; and
213 revoking an early allocation. It cannot be emphasized enough that
214 these processes must have a minimal impact on IANA itself, or they
215 will not be feasible.
216
217
218
219
220 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
223
224
225 The processes described below assume that the document in question is
226 the product of an IETF Working Group (WG). If this is not the case,
227 replace "WG chairs" below with "Shepherding Area Director".
228
229 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Request</span>
230
231 The process for requesting and obtaining early allocation of code
232 points is as follows:
233
234 1. The authors (editors) of the document submit a request for early
235 allocation to the Working Group chairs, specifying which code
236 points require early allocation and to which document they should
237 be assigned.
238
239 2. The WG chairs determine whether the conditions for early
240 allocations described in <a href="#section-2">Section 2</a> are met, particularly
241 conditions (c) and (d).
242
243 3. The WG chairs gauge whether there is consensus within the WG that
244 early allocation is appropriate for the given document.
245
246 4. If steps 2) and 3) are satisfied, the WG chairs request approval
247 from the Area Director(s). The Area Director(s) may apply
248 judgement to the request, especially if there is a risk of
249 registry depletion.
250
251 5. If the Area Directors approve step 4), the WG chairs request IANA
252 to make an early allocation.
253
254 6. IANA makes an allocation from the appropriate registry, marking
255 it as "Temporary", valid for a period of one year from the date
256 of allocation. The date of first allocation and the date of
257 expiry are also recorded in the registry and made visible to the
258 public.
259
260 Note that Internet-Drafts should not include a specific value of a
261 code point until IANA has completed the early allocation for this
262 value.
263
264 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Follow-Up</span>
265
266 It is the responsibility of the document authors and the Working
267 Group chairs to review changes in the document, and especially in the
268 specifications of the code points for which early allocation was
269 requested, to ensure that the changes are backward compatible.
270
271
272
273
274
275
276 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
279
280
281 If at some point changes that are not backward compatible are
282 nonetheless required, a decision needs to be made as to whether
283 previously allocated code points must be deprecated (see <a href="#section-3.3">Section 3.3</a>
284 for more information on code point deprecation). The considerations
285 include aspects such as the possibility of existing deployments of
286 the older implementations and, hence, the possibility for a collision
287 between older and newer implementations in the field.
288
289 If the document progresses to the point at which IANA normally makes
290 code point allocations, it is the responsibility of the authors and
291 the WG chairs to remind IANA that there were early allocations and of
292 the code point values allocated in the IANA Considerations section of
293 the RFC-to-be. Allocation is then just a matter of removing the
294 "Temporary" tag from the allocation description.
295
296 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Expiry</span>
297
298 As described in <a href="#section-3.1">Section 3.1</a>, each temporary assignment is recorded in
299 the registry with the date of expiry of the assignment. If an early
300 allocation expires before the document progresses to the point where
301 IANA normally makes allocations, the authors and WG chairs may repeat
302 the process described in <a href="#section-3.1">Section 3.1</a> to request renewal of the code
303 points. At most, one renewal request may be made; thus, authors
304 should choose carefully when the original request is to be made.
305
306 As an exception to the above rule, under rare circumstances, more
307 than one allocation renewal may be justified. All such further
308 renewal requests must be reviewed by the IESG. The renewal request
309 to the IESG must include the reasons why such further renewal is
310 necessary and the WG's plans regarding the specification.
311
312 If a follow-up request is not made, or the document fails to progress
313 to an RFC, the assignment will remain visible in the registry, but
314 the temporary assignment will be shown to have expired as indicated
315 by the expiry date. The WG chairs are responsible for informing IANA
316 that the expired assignments are not required and that the code
317 points are to be marked "deprecated".
318
319 A deprecated code point is not marked as allocated for use as
320 described in any document (that is, it is not allocated) and is not
321 available for allocation in a future document. The WG chairs may
322 inform IANA that a deprecated code point can be completely
323 de-allocated (i.e., made available for new allocations) at any time
324 after it has been deprecated. Factors influencing this decision will
325 include whether there may be implementations using the previous
326 temporary allocation and the availability of other unallocated code
327 points in the registry.
328
329
330
331
332 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
335
336
337 Implementers and deployers need to be aware that deprecation and
338 de-allocation could take place at any time after expiry; therefore,
339 an expired early allocation is best considered as deprecated.
340
341 It is not IANA's responsibility to track the status of allocations,
342 their expirations, or when they may be re-allocated.
343
344 Note that if a document is submitted for review to the IESG, and at
345 the time of submission some early allocations are valid (not
346 expired), these allocations must not be considered to have expired
347 while the document is under IESG consideration or is awaiting
348 publication in the RFC Editor's queue after approval by the IESG.
349
350 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
351
352 This document defines procedures for early allocation of code points
353 in the registries with the "Specification Required", "RFC Required",
354 "IETF Review", and "Standards Action" policies and as such directly
355 affects IANA. This document removes the need for registries to be
356 marked as specifically allowing early allocation. IANA has updated
357 impacted registries by removing any such markings.
358
359 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
360
361 It is important to keep in mind that denial-of-service attacks on
362 IANA are possible as a result of the processes defined in this memo.
363 There are two that are immediately obvious: depletion of code space
364 by early allocations and process overloading of IANA itself. The
365 processes described here attempt to alleviate both of these potential
366 attacks, but they are subject to scrutiny by IANA to ensure that they
367 work. IANA may at any time request that the IESG suspend the
368 procedures described in this document.
369
370 There is a significant concern that the procedures in this document
371 could be used as an end-run on the IETF process to achieve code point
372 allocation when an RFC will not be published. For example, a WG or a
373 WG chair might be pressured to obtain an early allocation for a
374 protocol extension for a particular company or for another Standards
375 Development Organization even though it might be predicted that an
376 IETF LC or IESG Evaluation would reject the approach that is
377 documented. The requirement for AD consent of early review is an
378 important safeguard, and ADs with any concern are strongly
379 recommended to escalate the issue for IESG-wide discussion.
380
381
382
383
384
385
386
387
388 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
391
392
393 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
394
395 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
396
397 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
398 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
399 May 2008.
400
401 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
402
403 [<a id="ref-RFC4020">RFC4020</a>] Kompella, K. and A. Zinin, "Early IANA Allocation of
404 Standards Track Code Points", <a href="https://www.rfc-editor.org/bcp/bcp100">BCP 100</a>, <a href="./rfc4020">RFC 4020</a>,
405 February 2005.
406
407 [<a id="ref-RFC4794">RFC4794</a>] Fenner, B., "<a href="./rfc1264">RFC 1264</a> Is Obsolete", <a href="./rfc4794">RFC 4794</a>,
408 December 2006.
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Cotton 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="./rfc7120">RFC 7120</a> Early IANA Allocation January 2014</span>
447
448
449 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgments</span>
450
451 Many thanks to Bert Wijnen, Adrian Farrel, and Bill Fenner for their
452 input on <a href="./rfc4020">RFC 4020</a>. Thank you to Kireeti Kompella and Alex Zinin for
453 authoring <a href="./rfc4020">RFC 4020</a>. Thank you to Adrian Farrel, Stewart Bryant, Leo
454 Vegoda, John Klensin, Subramanian Moonesamy, Loa Andersson, Tom
455 Petch, Robert Sparks, Eric Rosen, Amanda Baber, and Pearl Liang for
456 their reviews of this document.
457
458 Author's Address
459
460 Michelle Cotton
461 Internet Corporation for Assigned Names and Numbers
462 12025 Waterfront Drive, Suite 300
463 Los Angeles, CA 90094-2536
464 United States of America
465
466 Phone: +1-310-823-5800
467 EMail: [email protected]
468 URI: <a href="http://www.icann.org/">http://www.icann.org/</a>
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 Cotton Best Current Practice [Page 9]
501 </pre>