idnits 2.17.1 draft-huston-ipv4-iana-registry-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 625. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 602. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 609. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 615. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([IPv4]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 183 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 == There are 4 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 1, 2005) is 6902 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 484 -- Looks like a reference, but probably isn't: '2' on line 486 -- Looks like a reference, but probably isn't: '3' on line 488 -- Looks like a reference, but probably isn't: '4' on line 490 -- Looks like a reference, but probably isn't: '5' on line 494 -- Looks like a reference, but probably isn't: '6' on line 496 -- Looks like a reference, but probably isn't: '7' on line 500 -- Looks like a reference, but probably isn't: '8' on line 502 -- Looks like a reference, but probably isn't: '9' on line 504 -- Looks like a reference, but probably isn't: '10' on line 506 -- Looks like a reference, but probably isn't: '11' on line 510 -- Looks like a reference, but probably isn't: '12' on line 513 -- Looks like a reference, but probably isn't: '13' on line 516 == Missing Reference: 'RFC1918' is mentioned on line 530, but not defined == Missing Reference: 'RFC1356' is mentioned on line 520, but not defined == Missing Reference: 'RFC3068' is mentioned on line 538, but not defined ** Obsolete undefined reference: RFC 3068 (Obsoleted by RFC 7526) == Missing Reference: 'RFC1700' is mentioned on line 527, but not defined ** Obsolete undefined reference: RFC 1700 (Obsoleted by RFC 3232) == Missing Reference: 'RFC1466' is mentioned on line 524, but not defined ** Obsolete undefined reference: RFC 1466 (Obsoleted by RFC 2050) == Missing Reference: 'RFC2050' is mentioned on line 534, but not defined ** Obsolete undefined reference: RFC 2050 (Obsoleted by RFC 7020) == Missing Reference: 'RFC3171' is mentioned on line 541, but not defined ** Obsolete undefined reference: RFC 3171 (Obsoleted by RFC 5771) == Unused Reference: 'AS' is defined on line 573, but no explicit reference was found in the text == Unused Reference: 'IPv6' is defined on line 577, but no explicit reference was found in the text == Unused Reference: 'IPv6-Unicast' is defined on line 579, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'AS' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv4' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6-Unicast' ** Obsolete normative reference: RFC 3330 (Obsoleted by RFC 5735) Summary: 12 errors (**), 0 flaws (~~), 15 warnings (==), 25 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual Submission G. Huston 3 Internet-Draft APNIC 4 Expires: December 3, 2005 June 1, 2005 6 Report on the IANA IPv4 Address Registry 7 draft-huston-ipv4-iana-registry-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on December 3, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This is a report on an analysis of the IPv4 address registry as 41 published by the IANA [IPv4], comparing the contents of that registry 42 with IPv4 allocation data published by the Regional Internet 43 Registries (RIRs), as well as examining the registry from the 44 perspective of consistency of style and content. 46 1. Introduction 48 This is a report on an analysis of the IPv4 address registry as 49 published by the IANA [IPv4], comparing the contents of that registry 50 with IPv4 allocation data published by the Regional Internet 51 Registries (RIRs), as well as examining the registry from the 52 perspective of consistency of style and content. 54 2. IANA IPv4 Address Registry Comments 56 The areas of note with respect to the consistency and accuracy of the 57 IANA IPv4 registry are as follows: 59 1. Registry Completeness 61 The registry is incomplete. There are a number of special 62 reservations of addresses listed in RFC3330 [RFC3330] that also 63 form part of the IPv4 address status. It would be appropriate 64 to include the entries as listed in RFC 3330 in the IANA IPv4 65 registry. This could take the form of notes relating to entries 66 for the blocks "128.0.0.0/8", "169.0.0.0/8", "172.0.0.0/8", 67 "192.0.0.0/8", and "198.0.0.0/8", where components of these 68 blocks are reserved for particular purposes. 70 2. Interpretation of the annotation "IANA - Reserved" 72 A number of registry entries are listed with the purpose of 73 "IANA - Reserved". Some of these address blocks are reserved by 74 Internet Standards actions for particular purposes, while other 75 are held by IANA to be subsequently assigned for general use. 76 The registry should note that if a block is reserved by an 77 Internet Standard for a particular purpose, then the registry 78 entry should reflect this particular status. This comment 79 relating to "special purpose" reservations refers to the entries 80 for the address blocks "0.0.0.0/8", "127.0.0.0/8" and 81 "240.0.0.0/8" through "255.0.0.0/8". In other cases it would 82 appear that the appropriate status description of the address 83 block is "Unallocated". 85 3. Interpretation of registry entry for the "24.0.0.0/8" address 86 block 88 This IANA registry entry is listed as "ARIN - Cable Block". In 89 the interests of consistency and conformance to current use of 90 this address block, the registry description should be "ARIN" 91 without any particular purpose qualification. 93 4. Interpretation of Notes 95 The note relating to "24.0.0.0/8" indicates that this was 96 "Formerly IANA - Jul 95". It would be reasonable to assume that 97 all address blocks are formerly held by IANA, in which case no 98 particular mention of this status with respect to the 24.0.0.0/8 99 block is necessary. The more generic issue here is that there 100 is a valid distinction to be drawn between a current registry 101 status report and the log of previous changes to the registry. 102 It is assumed that the IANA registry file is a description of 103 the current status of the registry, in which case a log of 104 changes to the registry is better managed as a distinct report 105 of the sequence of annotated changes to the registry file, 106 rather than attempting to use the notes in this registry to 107 achieve that purpose. 109 5. Consistency of Registry Contents 111 The address blocks for "173.0.0.0/8 through "187.0.0.0/8", 112 "189.0.0.0/8", and "190.0.0.0/8" have dates of April 2003. It 113 is assumed from the dates that these address blocks were 114 formerly allocated. This raises the question of consistency of 115 registry information, in that there no notes associated with 116 these blocks whereas other formerly allocated blocks are 117 explicitly identified. Again the use of a distinct log of 118 changes to the registry would allow for a more consistent method 119 to capture this data. 121 6. Consistency of References 123 The note entry for "0.0.0.0/8" should refer to RFC3330. 125 The note entry for "014/8" should refer to RFC 1700. 127 The note entries for "224.0.0.0/8" through to "239.0.0.0/8" 128 should refer to RFC3171. 130 The note entries for "240.0.0.0/8" through to "255.0.0.0/8" 131 should refer to RFC1700. 133 7. Ambiguities 135 The entries for "049.0.0.0/8" and "50.0.0.0/8" indicate a 136 purpose of "Joint Technical Command", with a registry date of 137 May 1994, yet the associated note indicates "Returned to IANA 138 Mar 98". It would be reasonable to interpret the current status 139 of these two address blocks as part of the unallocated global 140 unicast address pool. In this case a consistent registry entry 141 for these address blocks would read: 143 049/8 Mar 98 Unallocated 144 050/8 Mar 98 Unallocated 146 8. A reference to a previous allocation to the Joint Technical 147 Command, and the subsequent return to IANA of these address 148 blocks would be more appropriately recorded in a log of changes 149 to the registry. 150 9. RFC 3330 Interpretation 152 The complete IPv4 number status relies on a consistent 153 interpretation of RFC3330. Entries for 39.0.0.0/8, 154 128.0.0.0/16, 191.0.0.0/16, 192.0.0.0/24, and 223.255.255.0/24 155 claim that the "present use" is "Reserved but subject to 156 allocation". Does this imply that these address blocks are 157 reserved, or form part of the general global unicast pool of as- 158 yet-unallocated address blocks? The assumption used here is 159 that these blocks are presently subject to allocation in the 160 same manner as any other currently unallocated address block. 162 10. Maintenance of Assignment information 164 It is noted that the Digital Equipment Corporation no longer 165 exists. This raises the broader question of the currency of the 166 information associated with this registry, and whether the 167 listed entities which received address blocks from IANA are 168 still those entities as listed. 170 11. Accuracy of the Date Field in the registry 172 The date field for "223.0.0.0/8" is April 2003. If this block 173 has not been formally allocated at any time, then what is the 174 reason for this relatively recent date? 176 12. Inconsistencies in the Date field compared to RIR data 178 The date fields associated with many of these entries are 179 inconsistent with records held by the RIRs. The primary source 180 of the dates proposed here is the database of address 181 allocations as maintained by ARIN [ARIN Stats]. Namely: 183 Block IANA Date RIR Date 184 ----- --------- -------- 185 3/8 May 94 23 Feb 88 186 7/8 Apr 95 24 Nov 97 187 9/8 Aug 92 16 Dec 88 188 11/8 May 93 19 Jan 84 189 12/8 Jun 95 23 Aug 83 190 13/8 Sep 91 25 Apr 86 191 16/8 Nov 94 18 May 89 192 17/8 Jul 92 16 Apr 90 193 19/8 May 95 15 Jun 88 194 20/8 Oct 94 04 Sep 89 195 22/8 May 93 26 Jun 89 196 25/8 Jan 95 28 Jan 85 197 34/8 Mar 93 11 Mar 91 198 38/8 Sep 94 16 Apr 91 199 40/8 Jun 94 23 Mar 91 200 43/8 Jan 91 21 Feb 89 201 45/8 Jan 95 09 Sep 91 202 47/8 Jan 91 06 Jan 89 203 48/8 May 95 07 Dec 90 204 51/8 Aug 94 16 Sep 91 205 53/8 Oct 93 17 Mar 92 206 55/8 Apr 95 26 Jan 96 207 56/8 Jun 94 02 Nov 92 208 57/8 May 95 21 Jun 93 209 128/8 May 93 24 Feb 83 210 129/8 May 93 12 Jan 87 211 130/8 May 93 17 Mar 88 212 131/8 May 93 08 Dec 87 213 132/8 May 93 05 Dec 88 214 133/8 May 93 05 Mar 89 215 134/8 May 93 11 May 88 216 135/8 May 93 01 May 93 217 136/8 May 93 15 Jun 88 218 137/8 May 93 03 Jan 89 219 138/8 May 93 11 Apr 89 220 139/8 May 93 29 Apr 88 221 140/8 May 93 03 Jul 89 222 141/8 May 93 26 Mar 90 223 142/8 May 93 26 Mar 90 224 143/8 May 93 21 Dec 89 225 144/8 May 93 11 Jan 90 226 145/8 May 93 27 Nov 90 227 146/8 May 93 29 Nov 90 228 147/8 May 93 09 Jan 89 229 148/8 May 93 30 Jul 90 230 149/8 May 93 09 Apr 90 231 150/8 May 93 08 May 91 232 151/8 May 93 12 Nov 90 233 152/8 May 93 01 Mar 91 234 153/8 May 93 13 Mar 89 235 154/8 May 93 05 Feb 92 236 155/8 May 93 10 Oct 91 237 156/8 May 93 14 Aug 91 238 157/8 May 93 30 Oct 91 239 158/8 May 93 16 May 91 240 159/8 May 93 13 Dec 89 241 160/8 May 93 24 Mar 92 242 161/8 May 93 20 Apr 92 243 162/8 May 93 22 Aug 90 244 163/8 May 93 21 Feb 92 245 164/8 May 93 27 Oct 92 246 165/8 May 93 11 Feb 93 247 166/8 May 93 24 Mar 93 248 167/8 May 93 23 Mar 93 249 168/8 May 93 16 Jul 93 250 169/8 May 93 25 Aug 93 251 170/8 May 93 05 Jun 92 252 171/8 May 93 25 Feb 94 253 192/8 May 93 19 Jan 83 254 193/8 May 93 19 Jan 92 255 194/8 May 93 02 Jun 93 256 196/8 May 93 16 Dec 92 257 198/8 May 93 08 Jan 92 258 202/8 May 93 01 Jan 93 259 203/8 May 93 01 Jan 93 260 215/8 Mar 98 06 Jun 98 262 13. Inconsistency with other address allocation data sources 264 The ARIN Registry lists the address block "7.0.0.0/8" as 265 assigned to the US Department of Defence. IANA records this 266 block as "IANA - Reserved", with the implication that this block 267 is part of the current unallocated pool. 269 The ARIN registry maintains a copy of all IANA allocations, with 270 the exception of the allocation of 46.0.0.0/8, which IANA lists 271 as an allocation to Bolt, Beranek and Newman, and ARIN maintains 272 no allocation information for this address block. This raises 273 the question of how these discrepancies arose, and the follow up 274 question of which source is authoritative for current address 275 status. 277 14. Reference Consistency 279 The IANA IPv4 registry lists as references RFC1466, RFC1700, 280 RFC1918 and RFC3330. RFC1466 has been obsoleted by RFC2050. 281 The references should also include RFC3171. The Public Data 282 registry associated with the entry "14.0.0.0/8" is defined in 283 RFC1356. 285 3. Amended IANA IPv4 Registry 287 The following is an example of a registry format and content that 288 attempts to resolve these inconsistencies. The approach used in this 289 example is to aggregate unallocated /8 prefixes into the largest 290 encompassing aggregate prefix. Where RFC 3330 has described address 291 blocks as "Reserved, but subject to allocation", this example 292 registry assumes that such blocks are currently unallocated in the 293 same fashion as any other unallocated address block. The dates of 294 allocation actions reflect the RIR recorded dates as noted above. 295 Unallocated address blocks have no allocation date. The reference to 296 notes has been treated consistently, as per the notes. 298 IPV4 GLOBAL UNICAST ADDRESS ASSIGNMENTS 300 [last updated 1 June 2005] 302 IPv4 Prefix Allocation Date Note 303 ----------- ---------- ---- ---- 304 0.0.0.0/8 Local Identification 01 Sep 81 [1] 305 1.0.0.0/8 Unallocated 306 2.0.0.0/8 Unallocated 307 3.0.0.0/8 General Electric Company 23 Feb 88 [2] 308 4.0.0.0/8 Bolt Beranek and Newman Inc. 01 Dec 92 [2] 309 6.0.0.0/8 Army Information Systems Center 01 Feb 94 [2] 310 7.0.0.0/8 US-DOD 24 Nov 97 [2] 311 8.0.0.0/8 Bolt Beranek and Newman Inc. 01 Dec 92 [2] 312 9.0.0.0/8 IBM 16 Dec 88 [2] 313 10.0.0.0/8 Private Use 01 Jun 95 [3] 314 11.0.0.0/8 DoD Intel Information Systems 19 Jan 84 [2] 315 12.0.0.0/8 AT&T Bell Laboratories 23 Aug 83 [2] 316 13.0.0.0/8 Xerox Corporation 25 Apr 86 [2] 317 14.0.0.0/8 Public Data Network 01 Jun 91 [4] 318 15.0.0.0/8 Hewlett-Packard Company 01 Jul 94 [2] 319 16.0.0.0/8 Digital Equipment Corporation 18 May 89 [2] 320 17.0.0.0/8 Apple Computer Inc. 16 Apr 94 [2] 321 18.0.0.0/8 MIT 01 Jan 94 [2] 322 19.0.0.0/8 Ford Motor Company 15 Jun 88 [2] 323 20.0.0.0/8 Computer Sciences Corporation 04 Sep 89 [2] 324 21.0.0.0/8 DDN-RVN 01 Jul 91 [2] 325 22.0.0.0/8 Defense Information Systems Agency 26 Jun 89 [2] 326 23.0.0.0/8 Unallocated 327 24.0.0.0/8 ARIN 01 May 01 328 25.0.0.0/8 Royal Signals and Radar Establishment 28 Jan 85 [2] 329 26.0.0.0/8 Defense Information Systems Agency 01 May 95 [2] 330 27.0.0.0/8 Unallocated 331 28.0.0.0/8 DSI-North 01 Jul 92 [2] 332 29.0.0.0/8 Defense Information Systems Agency 01 Jul 91 [2] 333 30.0.0.0/8 Defense Information Systems Agency 01 Jul 91 [2] 334 31.0.0.0/8 Unallocated 335 32.0.0.0/8 Norsk Informasjonsteknology 01 Jun 94 [2] 336 33.0.0.0/8 DLA Systems Automation Center 01 Jan 91 [2] 337 34.0.0.0/8 Halliburton Company 11 Mar 91 [2] 338 35.0.0.0/8 MERIT Computer Network 01 Apr 94 [2] 339 38.0.0.0/8 Performance Systems International 16 Apr 91 [2] 340 40.0.0.0/8 Eli Lily and Company 23 Mar 91 [2] 341 41.0.0.0/8 AfriNIC 14 Apr 05 342 43.0.0.0/8 Japan Inet 21 Feb 89 [2] 343 44.0.0.0/8 Amateur Radio Digital Communications 01 Jul 92 [2] 344 45.0.0.0/8 Interop Show Network 19 Sep 91 [2] 345 46.0.0.0/8 Bolt Beranek and Newman Inc. 01 Dec 92 [2] 346 47.0.0.0/8 Bell-Northern Research 06 Jan 89 [2] 347 48.0.0.0/8 Prudential Securities Inc. 07 Dec 90 [2] 348 49.0.0.0/7 Unallocated 349 51.0.0.0/8 Department of Social Security of UK 16 Sep 91 [2] 350 52.0.0.0/8 E.I. duPont de Nemours and Co., Inc. 19 Dec 91 [2] 351 53.0.0.0/8 Cap Debis CCS 17 Mar 92 [2] 352 54.0.0.0/8 Merck and Co., Inc. 17 Mar 92 [2] 353 55.0.0.0/8 Boeing Computer Services 01 Apr 95 [2] 354 56.0.0.0/8 U.S. Postal Service 02 Nov 92 [2] 355 57.0.0.0/8 SITA 21 Jun 93 [2] 356 58.0.0.0/8 APNIC 01 Apr 04 357 59.0.0.0/8 APNIC 01 Apr 04 358 60.0.0.0/8 APNIC 01 Apr 03 359 61.0.0.0/8 APNIC 01 Apr 97 360 62.0.0.0/8 RIPE NCC 01 Apr 97 361 63.0.0.0/8 ARIN 01 Apr 97 362 64.0.0.0/8 ARIN 01 Jul 99 363 65.0.0.0/8 ARIN 01 Jul 00 364 66.0.0.0/8 ARIN 01 Jul 00 365 67.0.0.0/8 ARIN 01 May 01 366 68.0.0.0/8 ARIN 01 Jun 01 367 69.0.0.0/8 ARIN 01 Aug 02 368 70.0.0.0/8 ARIN 01 Jan 04 369 71.0.0.0/8 ARIN 01 Aug 04 370 72.0.0.0/8 ARIN 01 Aug 04 371 73.0.0.0/8 ARIN 01 Mar 05 372 74.0.0.0/7 Unallocated 373 76.0.0.0/6 Unallocated 374 80.0.0.0/8 RIPE NCC 01 Apr 01 375 81.0.0.0/8 RIPE NCC 01 Apr 01 376 82.0.0.0/8 RIPE NCC 01 Nov 02 377 83.0.0.0/8 RIPE NCC 01 Nov 03 378 84.0.0.0/8 RIPE NCC 01 Nov 03 379 85.0.0.0/8 RIPE NCC 01 Apr 04 380 86.0.0.0/8 RIPE NCC 01 Apr 04 381 87.0.0.0/8 RIPE NCC 01 Apr 04 382 88.0.0.0/8 RIPE NCC 01 Apr 04 383 89.0.0.0/8 Unallocated 384 90.0.0.0/7 Unallocated 385 92.0.0.0/6 Unallocated 386 96.0.0.0/4 Unallocated 387 112.0.0.0/5 Unallocated 388 120.0.0.0/7 Unallocated 389 123.0.0.0/8 Unallocated 390 124.0.0.0/8 APNIC 01 Jan 05 391 125.0.0.0/8 APNIC 01 Jan 05 392 126.0.0.0/8 APNIC 01 Jan 05 393 127.0.0.0/8 Loopback 01 Sep 81 [5] 394 128.0.0.0/8 Various Registries 24 Feb 83 [6],[7] 395 129.0.0.0/8 Various Registries 12 Jan 87 [6] 396 130.0.0.0/8 Various Registries 17 Mar 88 [6] 397 131.0.0.0/8 Various Registries 08 Dec 87 [6] 398 132.0.0.0/8 Various Registries 05 Dec 88 [6] 399 133.0.0.0/8 Various Registries 05 Mar 89 [6] 400 134.0.0.0/8 Various Registries 11 May 86 401 135.0.0.0/8 Various Registries 01 May 93 [6] 402 136.0.0.0/8 Various Registries 15 Jun 88 [6] 403 137.0.0.0/8 Various Registries 03 Jan 89 [6] 404 138.0.0.0/8 Various Registries 11 Apr 89 [6] 405 139.0.0.0/8 Various Registries 29 Apr 88 [6] 406 140.0.0.0/8 Various Registries 03 Jul 89 [6] 407 141.0.0.0/8 Various Registries 26 Mar 90 [6] 408 142.0.0.0/8 Various Registries 26 Mar 90 [6] 409 143.0.0.0/8 Various Registries 21 Dec 89 [6] 410 144.0.0.0/8 Various Registries 11 Jan 90 [6] 411 145.0.0.0/8 Various Registries 27 Nov 90 [6] 412 146.0.0.0/8 Various Registries 29 Nov 90 [6] 413 147.0.0.0/8 Various Registries 09 Jan 89 [6] 414 148.0.0.0/8 Various Registries 30 Jul 90 [6] 415 149.0.0.0/8 Various Registries 09 Apr 90 [6] 416 150.0.0.0/8 Various Registries 08 May 91 [6] 417 151.0.0.0/8 Various Registries 12 Nov 90 [6] 418 152.0.0.0/8 Various Registries 01 Mar 91 [6] 419 153.0.0.0/8 Various Registries 13 Mar 89 [6] 420 154.0.0.0/8 Various Registries 05 Feb 92 [6] 421 155.0.0.0/8 Various Registries 10 Oct 91 [6] 422 156.0.0.0/8 Various Registries 14 Aug 91 [6] 423 157.0.0.0/8 Various Registries 30 Oct 91 [6] 424 158.0.0.0/8 Various Registries 16 May 91 [6] 425 159.0.0.0/8 Various Registries 13 Dec 89 [6] 426 160.0.0.0/8 Various Registries 24 Mar 92 [6] 427 161.0.0.0/8 Various Registries 20 Apr 92 [6] 428 162.0.0.0/8 Various Registries 22 Aug 90 [6] 429 163.0.0.0/8 Various Registries 21 Feb 92 [6] 430 164.0.0.0/8 Various Registries 27 Oct 92 [6] 431 165.0.0.0/8 Various Registries 11 Feb 93 [6] 432 166.0.0.0/8 Various Registries 24 Mar 93 [6] 433 167.0.0.0/8 Various Registries 23 Mar 93 [6] 434 168.0.0.0/8 Various Registries 16 Jul 93 [6] 435 169.0.0.0/8 Various Registries 25 Aug 93 [6],[8] 436 170.0.0.0/8 Various Registries 05 Jun 92 [6] 437 171.0.0.0/8 Various Registries 25 Feb 94 [6] 438 172.0.0.0/8 Various Registries 01 May 93 [6],[9] 439 173.0.0.0/8 Unallocated 440 174.0.0.0/7 Unallocated 441 176.0.0.0/5 Unallocated 442 184.0.0.0/6 Unallocated 443 188.0.0.0/8 Various Registries 01 May 93 [6] 444 189.0.0.0/8 Unallocated 445 190.0.0.0/8 Unallocated 446 191.0.0.0/8 Various Registries 01 May 93 [6] 447 192.0.0.0/8 Various Registries 19 Jan 83 [6],[10] 448 193.0.0.0/8 RIPE NCC 15 Jan 92 449 194.0.0.0/8 RIPE NCC 02 Jun 93 450 195.0.0.0/8 RIPE NCC 01 May 93 451 196.0.0.0/8 Various Registries 16 Dec 92 [6] 452 197.0.0.0/8 Unallocated 453 198.0.0.0/8 Various Registries 08 Jan 92 [6],[11] 454 199.0.0.0/8 ARIN 01 May 93 455 200.0.0.0/8 LACNIC 01 Nov 02 456 201.0.0.0/8 LACNIC 01 Apr 03 457 202.0.0.0/8 APNIC 01 Jan 93 458 203.0.0.0/8 APNIC 01 Jan 93 459 204.0.0.0/8 ARIN 01 Mar 94 460 205.0.0.0/8 ARIN 01 Mar 94 461 206.0.0.0/8 ARIN 01 Apr 95 462 207.0.0.0/8 ARIN 01 Nov 95 463 208.0.0.0/8 ARIN 01 Apr 96 464 209.0.0.0/8 ARIN 01 Jun 96 465 210.0.0.0/8 APNIC 01 Jun 96 466 211.0.0.0/8 APNIC 01 Jun 96 467 212.0.0.0/8 RIPE NCC 01 Oct 97 468 213.0.0.0/8 RIPE NCC 01 Mar 99 469 214.0.0.0/8 US-DOD 01 Mar 98 [2] 470 215.0.0.0/8 US-DOD 06 Jun 98 [2] 471 216.0.0.0/8 ARIN 01 Apr 98 472 217.0.0.0/8 RIPE NCC 01 Jun 00 473 218.0.0.0/8 APNIC 01 Dec 00 474 219.0.0.0/8 APNIC 01 Sep 01 475 220.0.0.0/8 APNIC 01 Dec 01 476 221.0.0.0/8 APNIC 01 Jul 02 477 222.0.0.0/8 APNIC 01 Feb 03 478 223.0.0.0/8 Unallocated 479 224.0.0.0/4 IANA - Multicast 01 Sep 81 [12] 480 240.0.0.0/4 IANA - Reserved 01 Sep 81 [13] 482 Notes: 484 [1] 0.0.0.0/8 reserved for self-identification [RFC3330] 486 [2] Allocation performed by IANA to end user 488 [3] 10.0.0.0/8 reserved for Private-Use Networks [RFC1918] 490 [4] The IANA Public Data Registry is at 491 http://www.iana.org/assignments/public-data-network-numbers 492 [RFC1356] 494 [5] 127.0.0.0/8 is reserved for Loopback [RFC3330] 496 [6] This allocation was undertaken prior to the current RIR 497 system. Address assignment information is shared across 498 the RIRs. 500 [7] 128.0.0.0/16 is Unallocated 502 [8] 169.254.0.0/16 reserved for Link Local [RFC3330] 504 [9] 172.16.0.0/12 reserved for Private-Use Networks [RFC1918] 506 [10] 192.0.2.0/24 reserved for Test-Net [RFC3330] 507 192.88.99.0/24 reserved for 6to4 Relay Anycast [RFC3068] 508 192.168.0.0/16 reserved for Private-Use Networks [RFC1918] 510 [11] 198.18.0.0/15 reserved for Network Interconnect Device 511 Benchmark Testing [RFC3330] 513 [12] The IANA Multicast Registry is at 514 http://www.iana.org/assignments/multicast-addresses 516 [13] Reserved by the IETF [RFC1700] 518 References: 520 [RFC1356] Malis, A., Robinson, D., and R. Ullmann, "Multiprotocol 521 Interconnect on X.25 and ISDN in the Packet Mode", 522 RFC 1356, August 1992. 524 [RFC1466] Gerich, E., "Guidelines for Management of IP Address 525 Space", RFC 1466, May 1993. 527 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", 528 RFC1700, October 1994. 530 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., 531 and E. Lear, "Address Allocation for Private 532 Internets", BCP 5, RFC 1918, February 1996. 534 [RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., 535 and J. Postel, "INTERNET REGISTRY IP ALLOCATION 536 GUIDELINES", BCP 12, RFC 2050, November 1996. 538 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay 539 Routers", RFC 3068, June 2001. 541 [RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper, 542 "IANA Guidelines for IPv4 Multicast Address 543 Assignments", BCP 51, RFC 3171, August 2001. 545 [RFC3330] IANA, "Special-Use IPv4 Addresses", RFC 3330, 546 September 2002. 548 4. Security Considerations 550 Security of the Internet's routing system relies on the ability to 551 authenticate an assertion of unique control of an address block. 552 Measures to authenticate such assertions rely on validation that the 553 address block forms part of an existing allocated address block, and 554 that there is a trustable reference from the IANA address registry to 555 the references Regional Internet Registry (RIR), and a trustable 556 reference from the RIR's registry to a Local Internet Registry or end 557 user Internet Service Provider. 559 The proposed format for the IANA registry is a small step towards the 560 creation of a registry that can be used as a trust point for 561 commencing a chain of address validation. Consideration should be 562 given to IANA registry publication formats that are machine 563 parseable, and also the use of file signatures and associated 564 certificate mechanisms to allow applications to confirm that the 565 registry contents are current, and that they have been published by 566 the IANA. 568 5. References 570 [ARIN Stats] 571 ARIN, "ARIN Stats Report", May 2005. 573 [AS] IANA, "IANA Autonomous System Number Registry", May 2005. 575 [IPv4] IANA, "IANA IPv4 Address Registry", May 2005. 577 [IPv6] IANA, "IANA IPv6 Address Registry", May 2005. 579 [IPv6-Unicast] 580 IANA, "IANA IPv6 Global Unicast Allocations", May 2005. 582 [RFC3330] IANA, "Special-Use IPv4 Addresses", RFC 3330, 583 September 2002. 585 Author's Address 587 Geoff Huston 588 Asia Pacific Network Information Centre 590 Email: gih@apnic.net 591 URI: http://www.apnic.net 593 Intellectual Property Statement 595 The IETF takes no position regarding the validity or scope of any 596 Intellectual Property Rights or other rights that might be claimed to 597 pertain to the implementation or use of the technology described in 598 this document or the extent to which any license under such rights 599 might or might not be available; nor does it represent that it has 600 made any independent effort to identify any such rights. Information 601 on the procedures with respect to rights in RFC documents can be 602 found in BCP 78 and BCP 79. 604 Copies of IPR disclosures made to the IETF Secretariat and any 605 assurances of licenses to be made available, or the result of an 606 attempt made to obtain a general license or permission for the use of 607 such proprietary rights by implementers or users of this 608 specification can be obtained from the IETF on-line IPR repository at 609 http://www.ietf.org/ipr. 611 The IETF invites any interested party to bring to its attention any 612 copyrights, patents or patent applications, or other proprietary 613 rights that may cover technology that may be required to implement 614 this standard. Please address the information to the IETF at 615 ietf-ipr@ietf.org. 617 Disclaimer of Validity 619 This document and the information contained herein are provided on an 620 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 621 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 622 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 623 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 624 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 625 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 627 Copyright Statement 629 Copyright (C) The Internet Society (2005). This document is subject 630 to the rights, licenses and restrictions contained in BCP 78, and 631 except as set forth therein, the authors retain all their rights. 633 Acknowledgment 635 Funding for the RFC Editor function is currently provided by the 636 Internet Society.