1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Internet Engineering Task Force (IETF) R. Housley
Request for Comments: 7249 Vigil Security
Category: Informational May 2014
ISSN: 2070-1721
<span class="h1">Internet Numbers Registries</span>
Abstract
<a href="./rfc7020">RFC 7020</a> provides information about the Internet Numbers Registry
System and how it is used in the distribution of autonomous system
(AS) numbers and globally unique unicast Internet Protocol (IP)
address space.
This companion document identifies the IANA registries that are part
of the Internet Numbers Registry System at this time.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7249">http://www.rfc-editor.org/info/rfc7249</a>.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Housley Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7249">RFC 7249</a> Internet Numbers Registries May 2014</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
In accordance with the IETF-IANA Memorandum of Understanding
[<a href="./rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"">RFC2860</a>], <a href="./rfc7020">RFC 7020</a> [<a href="./rfc7020" title=""The Internet Numbers Registry System"">RFC7020</a>] provides information about the Internet
Numbers Registry System and how it is used in the distribution of
autonomous system (AS) numbers and globally unique unicast Internet
Protocol (IP) address space.
This companion document identifies the IANA registries that are part
of the Internet Numbers Registry System at this time.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Internet Numbers Registries</span>
Three IANA registries are associated with the Internet Numbers
Registry System: "Autonomous System (AS) Numbers", "IANA IPv4 Address
Space Registry", and "IPv6 Global Unicast Address Assignments".
However, in each case, there are special-purpose values, and those
special-purpose values are outside the Internet Numbers Registry
System.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Autonomous System Numbers</span>
For historical reasons, there are 16-bit AS numbers and 32-bit AS
numbers. However, the 16-bit AS numbers are really just zero through
65535 of the 32-bit AS number space.
The allocation and registration functions for all non-reserved AS
numbers are handled by the Internet Numbers Registry System in
accordance with policies developed by the Regional Internet
Registries (RIRs) in accordance with their processes.
Some special-purpose AS numbers have been reserved. <a href="#section-3">Section 3</a> of
this document establishes an IANA registry for special-purpose AS
Numbers that have already been reserved. Future additions to this
registry can be made through "IETF Review" as defined in [<a href="./rfc5226" title="">RFC5226</a>].
Once a reservation is approved, it is recorded in the special-purpose
AS numbers registry with a reference to the IESG-approved RFC that
documents the reservation.
<span class="grey">Housley Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7249">RFC 7249</a> Internet Numbers Registries May 2014</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. IPv4 Addresses</span>
The allocation and registration functions for all non-reserved,
globally unique unicast IPv4 addresses are handled by the Internet
Numbers Registry System in accordance with policies developed by the
RIRs in accordance with their processes.
Reservations of special-purpose IPv4 addresses can be found in the
IANA registry [<a href="#ref-IANA-IPv4-Reg">IANA-IPv4-Reg</a>]. Future additions to this registry can
be made through "IETF Review" as defined in [<a href="./rfc5226" title="">RFC5226</a>]. Once a
reservation is approved, it is recorded in the special-purpose IPv4
address registry with a reference to the IESG-approved RFC that
documents the reservation.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IPv6 Addresses</span>
The vast bulk of the IPv6 address space (approximately 7/8ths of the
whole address space) is reserved by the IETF [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>], with the
expectation that further assignment of globally unique unicast
address space will be made from this reserved space in accordance
with future needs.
The allocation and registration functions for all non-reserved
globally unique unicast IPv6 addresses are handled by the Internet
Numbers Registry System in accordance with policies developed by the
RIRs in accordance with their processes.
Reservations of special-purpose IPv6 addresses can be found in the
IANA registry [<a href="#ref-IANA-IPv6-Reg">IANA-IPv6-Reg</a>]. Future additions to this registry can
be made through "IETF Review" as defined in [<a href="./rfc5226" title="">RFC5226</a>]. Once a
reservation is approved, it is recorded in the special-purpose IPv6
address registry with a reference to the IESG-approved RFC that
documents the reservation.
<span class="grey">Housley Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7249">RFC 7249</a> Internet Numbers Registries May 2014</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
IANA has created the "Special-Purpose AS Numbers" registry. Future
additions to this registry can be made through "IETF Review" as
defined in [<a href="./rfc5226" title="">RFC5226</a>]. At this time, the special-purpose AS numbers
are:
AS Numbers Reason for Reservation
--------------------- -------------------------------------------
0 Reserved by [<a href="#ref-AS0-PROCESS">AS0-PROCESS</a>]
23456 AS_TRANS; reserved by [<a href="./rfc6793" title=""BGP Support for Four-Octet Autonomous System (AS) Number Space"">RFC6793</a>]
64496-64511 For documentation and sample code; reserved
by [<a href="./rfc5398" title=""Autonomous System (AS) Number Reservation for Documentation Use"">RFC5398</a>]
64512-65534 For private use; reserved by [<a href="./rfc6996" title=""Autonomous System (AS) Reservation for Private Use"">RFC6996</a>]
65535 Reserved by [<a href="./rfc1930" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">RFC1930</a>]
65536-65551 For documentation and sample code; reserved
by [<a href="./rfc5398" title=""Autonomous System (AS) Number Reservation for Documentation Use"">RFC5398</a>]
4200000000-4294967294 For private use; reserved by [<a href="./rfc6996" title=""Autonomous System (AS) Reservation for Private Use"">RFC6996</a>]
4294967295 Reserved by [<a href="#ref-LAST-AS-RES">LAST-AS-RES</a>]
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document identifies the IANA registries that are part of the
Internet Numbers Registry System at the time of publication. It does
not change the security posture of the Internet in any way.
Network operators should take care that special-purpose numbers and
addresses are used on the public Internet in a manner that is
consistent with their reserved purpose.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-RFC2860">RFC2860</a>] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Internet
Assigned Numbers Authority", <a href="./rfc2860">RFC 2860</a>, June 2000.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, May
2008.
[<a id="ref-RFC7020">RFC7020</a>] Housley, R., Curran, J., Huston, G., and D. Conrad, "The
Internet Numbers Registry System", <a href="./rfc7020">RFC 7020</a>, August 2013.
<span class="grey">Housley Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7249">RFC 7249</a> Internet Numbers Registries May 2014</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-AS0-PROCESS">AS0-PROCESS</a>]
Kumari, W., Bush, R., Schiller, H., and K. Patel,
"Codification of AS 0 processing", Work in Progress, August
2012.
[<a id="ref-IANA-IPv4-Reg">IANA-IPv4-Reg</a>]
IANA, "IANA IPv4 Special-Purpose Address Registry",
<<a href="http://www.iana.org/assignments/iana-ipv4-special-registry">http://www.iana.org/assignments/</a>
<a href="http://www.iana.org/assignments/iana-ipv4-special-registry">iana-ipv4-special-registry</a>>.
[<a id="ref-IANA-IPv6-Reg">IANA-IPv6-Reg</a>]
IANA, "IANA IPv6 Special-Purpose Address Registry",
<<a href="http://www.iana.org/assignments/iana-ipv6-special-registry">http://www.iana.org/assignments/</a>
<a href="http://www.iana.org/assignments/iana-ipv6-special-registry">iana-ipv6-special-registry</a>>.
[<a id="ref-LAST-AS-RES">LAST-AS-RES</a>]
Haas, J. and J. Mitchell, "Reservation of Last Autonomous
System (AS) Numbers", Work in Progress, April 2014.
[<a id="ref-RFC1930">RFC1930</a>] Hawkinson, J. and T. Bates, "Guidelines for creation,
selection, and registration of an Autonomous System (AS)",
<a href="https://www.rfc-editor.org/bcp/bcp6">BCP 6</a>, <a href="./rfc1930">RFC 1930</a>, March 1996.
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
[<a id="ref-RFC5398">RFC5398</a>] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", <a href="./rfc5398">RFC 5398</a>, December 2008.
[<a id="ref-RFC6793">RFC6793</a>] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
Autonomous System (AS) Number Space", <a href="./rfc6793">RFC 6793</a>, December
2012.
[<a id="ref-RFC6996">RFC6996</a>] Mitchell, J., "Autonomous System (AS) Reservation for
Private Use", <a href="https://www.rfc-editor.org/bcp/bcp6">BCP 6</a>, <a href="./rfc6996">RFC 6996</a>, July 2013.
Acknowledgements
Many thanks to Jari Arkko, Scott Bradner, Brian Carpenter, David
Conrad, John Curran, David Farmer, Adrian Farrel, Stephen Farrell,
Brian Haberman, Geoff Huston, George Michaelson, S. Moonesamy, and
Thomas Narten for their insightful review and comment.
<span class="grey">Housley Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7249">RFC 7249</a> Internet Numbers Registries May 2014</span>
Author's Address
Russell Housley
Vigil Security, LLC
918 Spring Knoll Drive
Herndon, VA 20170
USA
EMail: housley@vigilsec.com
Housley Informational [Page 6]
</pre>
|
