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) G. Huston
Request for Comments: 5736 APNIC
Category: Informational M. Cotton
ISSN: 2070-1721 L. Vegoda
ICANN
January 2010
<span class="h1">IANA IPv4 Special Purpose Address Registry</span>
Abstract
This is a direction to IANA concerning the creation and management of
the IANA IPv4 Special Purpose Address Registry.
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/rfc5736">http://www.rfc-editor.org/info/rfc5736</a>.
Copyright Notice
Copyright (c) 2010 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">Huston, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5736">RFC 5736</a> IPv4 Special Registry January 2010</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. IANA IPv4 Special Purpose Address Block . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. Informative References . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This is a direction to [<a href="#ref-IANA" title=""IANA Matrix for Protocol Parameter Assignment/ Registration Procedures"">IANA</a>] concerning the creation and management
of the IANA IPv4 Special Purpose Address Registry. The registry will
be used for recording IETF protocol assignments from 192.0.0.0/24 and
any other address prefixes allocated to the registry in the future,
as described in <a href="#section-3">Section 3</a>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA IPv4 Special Purpose Address Block</span>
[<a id="ref-RFC5735">RFC5735</a>] records the assignment of an IPv4 address prefix to IANA
for IETF protocol assignments.
192.0.0.0/24 - This block is reserved for IETF protocol
assignments.
This address allocation to IANA is intended to support IETF protocol
assignments. A more general view of the roles of IANA with respect
to address allocation functions is documented in [<a href="./rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"">RFC2860</a>]:
4.3. [...] Note that [...] (b) assignments of specialised address
blocks (such as multicast or anycast blocks), and (c) experimental
assignments are not considered to be policy issues, and shall
remain subject to the provisions of this <a href="#section-4">Section 4</a>. (For purposes
of this MOU, the term "assignments" includes allocations.)
The reference to <a href="#section-4">Section 4</a> here is to the general technical work for
the IANA as described in [<a href="./rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"">RFC2860</a>]:
4.1. The IANA will assign and register Internet protocol
parameters only as directed by the criteria and procedures
specified in RFCs, including Proposed, Draft, and full Internet
Standards and Best Current Practice documents, and any other RFC
that calls for IANA assignment.
This document directs IANA to designate special purpose address
blocks in compliance with [<a href="./rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"">RFC2860</a>].
<span class="grey">Huston, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5736">RFC 5736</a> IPv4 Special Registry January 2010</span>
This document directs IANA to open an IPv4 Special Purpose Address
Registry for the management of these IANA-designated address blocks.
Special Purpose registrations to be made from this registry include
addresses for IETF protocol assignments and other special purpose
cases, as documented in IESG-reviewed RFCs, according to the
provisions described in <a href="./rfc2860#section-4.1">Section 4.1 of [RFC2860]</a>.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
IANA maintains an "IANA IPv4 Special Purpose Address Registry". The
registry records current IANA address designations from the IANA-
managed IPv4 Special Purpose address pool.
This recommendation concerns the management of the address pool used
for IETF protocol assignments as documented in [<a href="./rfc5735" title=""Special Use IPv4 Addresses"">RFC5735</a>] -- namely,
192.0.0.0/24. Following the policies outlined in [<a href="./rfc5226" title="">RFC5226</a>], further
assignments of address space to IANA for subsequent designation of
address prefixes for the purposes listed here shall be undertaken
only through an IETF Review action.
IANA may make Special Purpose address designations to support testing
or experimental usage activities initiated by the IETF, or for
specialised use of a designated address block in a context (e.g.,
anycast) associated with an Internet Standards Track protocol. All
such address designations must be documented in the "IANA
Considerations" section of an IESG-reviewed RFC.
The IANA IPv4 Special Purpose Address Registry records, for all
current address designations undertaken by IANA:
1. The designated address prefix.
2. The RFC that called for the IANA address designation.
3. The date the designation was made.
4. The date the use designation is to be terminated (if specified as
a limited-use designation).
5. The nature of the purpose of the designated address (e.g.,
unicast experiment or protocol service anycast).
6. For experimental unicast applications and otherwise as
appropriate, the registry will also identify the entity and
related contact details to whom the address designation has been
made.
<span class="grey">Huston, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5736">RFC 5736</a> IPv4 Special Registry January 2010</span>
7. The registry will also note, for each designation, the intended
routing scope of the address, indicating whether the address is
intended to be routable only in scoped, local, or private
contexts, or whether the address prefix is intended to be routed
globally.
8. The date in the IANA registry is the date of the IANA action,
i.e., the day IANA records the allocation.
The IANA registry notes, as a general comment, that address prefixes
listed in the IPv4 Special Purpose Address Registry are not
guaranteed routability in any particular local or global context.
IANA will not maintain further sub-registries for any IPv4 Special
Purpose address block designated according to this direction.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Security of the Internet's routing system relies on the ability to
authenticate an assertion of unique control of an address block.
Measures to authenticate such assertions rely on validation that the
address block forms part of an existing allocated address block, and
that there is a trustable and unique reference in the IANA address
registries.
This registry is intended to provide an authoritative source of
information regarding the currency and intended purpose of IPv4
Special Purpose address blocks that are designated from the IANA-
administered IPv4 Special Purpose address pool. This is a small step
towards the creation of a comprehensive registry framework that can
be used as a trust point for commencing a chain of address
validation. Consideration should be given to the use of file
signatures and associated certificate mechanisms to allow
applications to confirm that the registry contents are current, and
that they have been published by the IANA.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
This document is based on [<a href="./rfc4773" title=""Administration of the IANA Special Purpose IPv6 Address Block"">RFC4773</a>], which was prepared with the
assistance of Leslie Daigle, Brian Haberman, Bob Hinden, David
Kessens, Kurt Lindqvist, Thomas Narten, and Paul Wilson. While all
these individuals were not explicitly consulted in the preparation of
this document, their original contribution is acknowledged here.
<span class="grey">Huston, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5736">RFC 5736</a> IPv4 Special Registry January 2010</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span>
[<a id="ref-IANA">IANA</a>] IANA, "IANA Matrix for Protocol Parameter Assignment/
Registration Procedures",
<<a href="http://www.iana.org/numbers.html">http://www.iana.org/numbers.html</a>>.
[<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-RFC4773">RFC4773</a>] Huston, G., "Administration of the IANA Special Purpose
IPv6 Address Block", <a href="./rfc4773">RFC 4773</a>, December 2006.
[<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-RFC5735">RFC5735</a>] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
<a href="https://www.rfc-editor.org/bcp/bcp153">BCP 153</a>, <a href="./rfc5735">RFC 5735</a>, January 2010.
<span class="grey">Huston, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5736">RFC 5736</a> IPv4 Special Registry January 2010</span>
Authors' Addresses
Geoff Huston
Asia Pacific Network Information Centre
PO Box 2131
Milton, QLD 4064
Australia
Phone: +61-7-3858-3100
EMail: gih@apnic.net
URI: <a href="http://www.apnic.net/">http://www.apnic.net/</a>
Michelle Cotton
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
USA
Phone: +1-310-823-9358
EMail: michelle.cotton@icann.org
URI: <a href="http://www.iana.org/">http://www.iana.org/</a>
Leo Vegoda
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
USA
Phone: +1-310-823-9358
EMail: leo.vegoda@icann.org
URI: <a href="http://www.iana.org/">http://www.iana.org/</a>
Huston, et al. Informational [Page 6]
</pre>
|
