idnits 2.17.1 draft-bonica-special-purpose-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 11 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 3 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. == There are 6 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- The draft header indicates that this document obsoletes RFC5736, but the abstract doesn't seem to directly say this. It does mention RFC5736 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 23, 2013) is 4082 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (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 291 -- Looks like a reference, but probably isn't: '2' on line 344 -- Looks like a reference, but probably isn't: '3' on line 589 -- Looks like a reference, but probably isn't: '4' on line 676 == Unused Reference: 'RFC4007' is defined on line 777, but no explicit reference was found in the text == Unused Reference: 'RFC6333' is defined on line 826, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 3068 (Obsoleted by RFC 7526) -- Obsolete informational reference (is this intentional?): RFC 4379 (Obsoleted by RFC 8029) -- Obsolete informational reference (is this intentional?): RFC 4773 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 4843 (Obsoleted by RFC 7343) -- Obsolete informational reference (is this intentional?): RFC 5156 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 5735 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 5736 (Obsoleted by RFC 6890) Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Cotton 3 Internet-Draft L. Vegoda 4 Obsoletes: 4773, 5156, 5735, 5736 Internet Corporation for 5 (if approved) Assigned Names and Numbers 6 Intended status: BCP R. Bonica, Ed. 7 Expires: July 27, 2013 Juniper Networks 8 B. Haberman 9 Johns Hopkins University Applied 10 Physics Lab 11 January 23, 2013 13 Special-Purpose IP Address Registries 14 draft-bonica-special-purpose-07 16 Abstract 18 This memo reiterates the assignment of an IPv4 address block 19 (192.0.0.0/24) to IANA. It also instructs IANA to restructure its 20 IPv4 and IPv6 Special-Purpose Address Registries. Upon 21 restructuring, the aforementioned registries will record all special- 22 purpose address blocks, maintaining a common set of information 23 regarding each address block. 25 This memo obsoletes RFC 4773, RFC 5156, RFC 5735 and RFC 5736. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on July 27, 2013. 44 Copyright Notice 46 Copyright (c) 2013 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 2.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 4 64 2.2. Restructuring of the IPv4 and IPv6 Special-Purpose 65 Address Registries . . . . . . . . . . . . . . . . . . . . 4 66 2.2.1. Information Requirements . . . . . . . . . . . . . . . 5 67 2.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 6 68 2.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 13 69 3. Security Considerations . . . . . . . . . . . . . . . . . . . 19 70 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 71 5. Informative References . . . . . . . . . . . . . . . . . . . . 20 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 74 1. Introduction 76 In order to support new protocols and practices, the IETF 77 occasionally reserves an address block a for special purpose. For 78 example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to 79 represent the local (i.e., "this") network. Likewise, [RFC4291] 80 reserves an IPv6 address block (fe80::/10) to represent link-scoped 81 unicast addresses. 83 Periodically, the IETF publishes an RFC that catalogs special-purpose 84 address blocks. Currently, [RFC5735] catalogs all IPv4 special- 85 purpose address blocks and [RFC5156] catalogs all IPv6 special- 86 purpose address blocks. 88 [RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and 89 instructs IANA to allocate special-purpose address blocks from this 90 space. [RFC5736] also instructs IANA to create an IPv4 Special- 91 Purpose Address Registry that records allocations from this address 92 space. However, [RFC5736] does not instruct IANA to record special- 93 purpose address block reservations from outside of the aforementioned 94 space in the IPv4 Special-Purpose Address Registry. 96 Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to 97 IANA and instructs IANA to allocate special-purpose address blocks 98 from this space. [RFC4773] instructs IANA to create an IPv6 Special- 99 Purpose Address Registry that records allocations from this address 100 space. However, [RFC4773] does not instruct IANA to record special- 101 purpose address block reservations from outside of the aforementioned 102 space in the IPv6 Special-Purpose Address Registry. 104 This memo reiterates the assignment of an IPv4 address block 105 (192.0.0.0/24) to IANA. It also instructs IANA to restructure its 106 IPv4 and IPv6 Special-Purpose Address Registries. Specifically, this 107 memo instructs IANA to record all special-purpose address blocks in 108 the aforementioned registries. These include, but are not limited 109 to, IPv4 allocations from 192.0.0.0/24 and IPv6 allocations from 110 2001:0000::/23. Furthermore, this memo defines: 112 o a common set of information that the registries will maintain 113 regarding each special-purpose address block 115 o a common set of requirements for future entries 117 When the aforementioned registries include all special-purpose 118 address blocks, [RFC5735] and [RFC5156] will become redundant with 119 the registries. Therefore, this memo obsoletes [RFC5735] and 120 [RFC5156]. Because this memo reiterates the assignment of 121 192.0.0.0/24 to IANA, and because it restructures the IPv4 Special- 122 Purpose Address Registry, it obsoletes [RFC5736]. Finally, becaue 123 this memo restructures the IPv6 Special-Purpose Address Registry, it 124 obsoletes [RFC4773]. 126 2. IANA Considerations 128 2.1. Assignment of an IPv4 Address Block to IANA 130 Table 7 of this document records the assignment of an IPv4 address 131 block (192.0.0.0/24) to IANA for IETF protocol assignments. This 132 address allocation to IANA is intended to support IETF protocol 133 assignments. A more general view of the roles of IANA with respect 134 to address allocation functions is documented in Sections 4.1 and 4.3 135 [RFC2860]. 137 This document directs IANA to designate special purpose address 138 blocks in compliance with [RFC2860]. 140 2.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address 141 Registries 143 IANA will restructure the following registries: 145 o IPv4 Special-Purpose Address Registry 147 o IPv6 Special-Purpose Address Registry 149 The IPv4 Special-Purpose Address Registry will record all IPv4 150 special-purpose address blocks. These reservations will include, but 151 not be limited to, allocations from the 192.0.0.0/24 address block. 152 Likewise, the IPv6 Special-Purpose Address Registry will record all 153 IPv6 special-purpose address blocks. These reservations will 154 include, but not be limited to, allocations from the 2001:0000::/23 155 address block. 157 Section 2.2.1 of this document describes information that both 158 registries will maintain for each entry. Initially, IANA will 159 populate the IPv4 Special-Purpose Address Registry with information 160 taken from Section 2.2.2 of this document. Likewise, IANA will 161 populate the IPv6 Special-Purpose Address Registry with information 162 taken from Section 2.2.3 of this document. 164 IANA will update the aforementioned registries as requested in the 165 "IANA Considerations" section of a document that has passed IETF 166 Review [RFC5226]. The "IANA Considerations" section must include all 167 of the information specified in Section 2.2.1 of this document. 169 2.2.1. Information Requirements 171 The IPv4 and IPv6 Special-Purpose Address Registries will maintain 172 the following information regarding each entry: 174 o Address Block - A block of IPv4 or IPv6 addresses that has been 175 registered for a special-purpose 177 o Name - A descriptive name for the special-purpose address block 179 o RFC - The RFC through which the special-purpose address block was 180 requested 182 o Allocation Date - The date upon which the special purpose address 183 block was allocated 185 o Termination Date - The date upon which the allocation is to be 186 terminated. This field is applicable for limited-use allocations 187 only. 189 o Source - A boolean value indicating whether an address from the 190 allocated special-purpose address block is valid when used as the 191 source address of an IP datagram that transits two devices 193 o Destination - A boolean value indicating whether an address from 194 the allocated special-purpose address block is valid when used as 195 the destination address of an IP datagram that transits two 196 devices 198 o Forwardable - A boolean value indicating whether a router may 199 forward an IP datagram whose destination address is drawn from the 200 allocated special-purpose address block between external 201 interfaces. 203 o Global - A boolean value indicating whether an IP datagram whose 204 destination address is drawn from the allocated special-purpose 205 address block is forwardable beyond a specified administrative 206 domain. 208 o Reserved-by-protocol - A boolean value indicating whether the 209 special-purpose address block is reserved by IP, itself. This 210 value is "TRUE" if the RFC that created the special-purpose 211 address block requires all compliant IP implementations to behave 212 in a special way when processing packets either to or from 213 addresses contained by the address block. 215 If the value of "Destination" is FALSE, the values of "Forwardable" 216 and "Global" must also be false. 218 2.2.2. IPv4 Special-Purpose Address Registry Entries 220 Table 1 though Table 16, below, represent entries with which the IANA 221 will initially populate the IPv4 Special-Purpose Address Registry. 223 +----------------------+---------------------------+ 224 | Attribute | Value | 225 +----------------------+---------------------------+ 226 | Address Block | 0.0.0.0/8 | 227 | Name | "This" Network | 228 | RFC | [RFC1122] Section 3.2.1.3 | 229 | Allocation Date | September, 1981 | 230 | Termination Date | N/A | 231 | Source | True | 232 | Destination | False | 233 | Forwardable | False | 234 | Global | False | 235 | Reserved-by-protocol | True | 236 +----------------------+---------------------------+ 238 Table 1: "This" Network 240 +----------------------+---------------+ 241 | Attribute | Value | 242 +----------------------+---------------+ 243 | Address Block | 10.0.0.0/8 | 244 | Name | Private-Use | 245 | RFC | [RFC1918] | 246 | Allocation Date | February 1996 | 247 | Termination Date | N/A | 248 | Source | True | 249 | Destination | True | 250 | Forwardable | True | 251 | Global | False | 252 | Reserved-by-protocol | False | 253 +----------------------+---------------+ 255 Table 2: Private-Use Networks 257 +----------------------+----------------------+ 258 | Attribute | Value | 259 +----------------------+----------------------+ 260 | Address Block | 100.64.0.0/10 | 261 | Name | Shared Address Space | 262 | RFC | [RFC6598] | 263 | Allocation Date | April 2012 | 264 | Termination Date | N/A | 265 | Source | True | 266 | Destination | True | 267 | Forwardable | True | 268 | Global | False | 269 | Reserved-by-protocol | False | 270 +----------------------+----------------------+ 272 Table 3: Shared Address Space 274 +----------------------+---------------------------+ 275 | Attribute | Value | 276 +----------------------+---------------------------+ 277 | Address Block | 127.0.0.0/8 | 278 | Name | Loopback | 279 | RFC | [RFC1122] Section 3.2.1.3 | 280 | Allocation Date | September 1981 | 281 | Termination Date | N/A | 282 | Source | False [1] | 283 | Destination | False [1] | 284 | Forwardable | False [1] | 285 | Global | False [1] | 286 | Reserved-by-protocol | True | 287 +----------------------+---------------------------+ 289 Table 4: Loopback 291 [1] Several protocols have been granted exceptions to this rule. For 292 examples, see [RFC4379] and [RFC5884] 293 +----------------------+----------------+ 294 | Attribute | Value | 295 +----------------------+----------------+ 296 | Address Block | 169.254.0.0/16 | 297 | Name | Link Local | 298 | RFC | [RFC3927] | 299 | Allocation Date | May 2005 | 300 | Termination Date | N/A | 301 | Source | True | 302 | Destination | True | 303 | Forwardable | False | 304 | Global | False | 305 | Reserved-by-protocol | True | 306 +----------------------+----------------+ 308 Table 5: Link Local 310 +----------------------+---------------+ 311 | Attribute | Value | 312 +----------------------+---------------+ 313 | Address Block | 172.16.0.0/12 | 314 | Name | Private-Use | 315 | RFC | [RFC1122] | 316 | Allocation Date | February 1996 | 317 | Termination Date | N/A | 318 | Source | True | 319 | Destination | True | 320 | Forwardable | True | 321 | Global | False | 322 | Reserved-by-protocol | False | 323 +----------------------+---------------+ 325 Table 6: Private-Use Networks 327 +----------------------+-------------------------------+ 328 | Attribute | Value | 329 +----------------------+-------------------------------+ 330 | Address Block | 192.0.0.0/24 [2] | 331 | Name | IETF Protocol Assignments | 332 | RFC | Section 2.1 of this document. | 333 | Allocation Date | January 2010 | 334 | Termination Date | N/A | 335 | Source | False | 336 | Destination | False | 337 | Forwardable | False | 338 | Global | False | 339 | Reserved-by-protocol | False | 340 +----------------------+-------------------------------+ 342 Table 7: IETF Protocol Assignments 344 [2] Not useable unless by virtue of a more specific reservation. 346 +----------------------+------------------------------+ 347 | Attribute | Value | 348 +----------------------+------------------------------+ 349 | Address Block | 192.0.0.0/29 | 350 | Name | DS-Lite | 351 | RFC | Section 2.1 of this document | 352 | Allocation Date | June 2011 | 353 | Termination Date | N/A | 354 | Source | True | 355 | Destination | True | 356 | Forwardable | True | 357 | Global | False | 358 | Reserved-by-protocol | False | 359 +----------------------+------------------------------+ 361 Table 8: DS-Lite 363 +----------------------+----------------------------+ 364 | Attribute | Value | 365 +----------------------+----------------------------+ 366 | Address Block | 192.0.2.0/24 | 367 | Name | Documentation (TEST-NET-1) | 368 | RFC | [RFC5737] | 369 | Allocation Date | January 2010 | 370 | Termination Date | N/A | 371 | Source | False | 372 | Destination | False | 373 | Forwardable | False | 374 | Global | False | 375 | Reserved-by-protocol | False | 376 +----------------------+----------------------------+ 378 Table 9: TEST-NET-1 380 +----------------------+--------------------+ 381 | Attribute | Value | 382 +----------------------+--------------------+ 383 | Address Block | 192.88.99.0/24 | 384 | Name | 6to4 Relay Anycast | 385 | RFC | [RFC3068] | 386 | Allocation Date | June 2001 | 387 | Termination Date | N/A | 388 | Source | True | 389 | Destination | True | 390 | Forwardable | True | 391 | Global | True | 392 | Reserved-by-protocol | False | 393 +----------------------+--------------------+ 395 Table 10: 6to4 Relay Anycast 397 +----------------------+----------------+ 398 | Attribute | Value | 399 +----------------------+----------------+ 400 | Address Block | 192.168.0.0/16 | 401 | Name | Private-Use | 402 | RFC | [RFC1918] | 403 | Allocation Date | February 1996 | 404 | Termination Date | N/A | 405 | Source | True | 406 | Destination | True | 407 | Forwardable | True | 408 | Global | False | 409 | Reserved-by-protocol | False | 410 +----------------------+----------------+ 412 Table 11: Private-Use Networks 414 +----------------------+---------------+ 415 | Attribute | Value | 416 +----------------------+---------------+ 417 | Address Block | 198.18.0.0/15 | 418 | Name | Benchmarking | 419 | RFC | [RFC2544] | 420 | Allocation Date | March 1999 | 421 | Termination Date | N/A | 422 | Source | True | 423 | Destination | True | 424 | Forwardable | True | 425 | Global | False | 426 | Reserved-by-protocol | False | 427 +----------------------+---------------+ 429 Table 12: Network Interconnect Device Benchmark Testing 430 +----------------------+----------------------------+ 431 | Attribute | Value | 432 +----------------------+----------------------------+ 433 | Address Block | 198.51.100.0/24 | 434 | Name | Documentation (TEST-NET-2) | 435 | RFC | [RFC5737] | 436 | Allocation Date | January 2010 | 437 | Termination Date | N/A | 438 | Source | False | 439 | Destination | False | 440 | Forwardable | False | 441 | Global | False | 442 | Reserved-by-protocol | False | 443 +----------------------+----------------------------+ 445 Table 13: TEST-NET-2 447 +----------------------+----------------------------+ 448 | Attribute | Value | 449 +----------------------+----------------------------+ 450 | Address Block | 203.0.113.0/24 | 451 | Name | Documentation (TEST-NET-3) | 452 | RFC | [RFC5737] | 453 | Allocation Date | January 2010 | 454 | Termination Date | N/A | 455 | Source | False | 456 | Destination | False | 457 | Forwardable | False | 458 | Global | False | 459 | Reserved-by-protocol | False | 460 +----------------------+----------------------------+ 462 Table 14: TEST-NET-3 464 +----------------------+---------------------+ 465 | Attribute | Value | 466 +----------------------+---------------------+ 467 | Address Block | 240.0.0.0/4 | 468 | Name | Reserved | 469 | RFC | [RFC1112] Section 4 | 470 | Allocation Date | August 1989 | 471 | Termination Date | N/A | 472 | Source | False | 473 | Destination | False | 474 | Forwardable | False | 475 | Global | False | 476 | Reserved-by-protocol | True | 477 +----------------------+---------------------+ 479 Table 15: Reserved for Future Use 481 +----------------------+---------------------+ 482 | Attribute | Value | 483 +----------------------+---------------------+ 484 | Address Block | 255.255.255.255/32 | 485 | Name | Limited Broadcast | 486 | RFC | [RFC0919] Section 7 | 487 | Allocation Date | October 1984 | 488 | Termination Date | N/A | 489 | Source | False | 490 | Destination | True | 491 | Forwardable | False | 492 | Global | False | 493 | Reserved-by-protocol | False | 494 +----------------------+---------------------+ 496 Table 16: Limited Broadcast 498 2.2.3. IPv6 Special-Purpose Address Registry Entries 500 Table 17 through Table 28, below, represent entries with which the 501 IANA will initially populate the IPv6 Special-Purpose Address 502 Registry. 504 +----------------------+------------------+ 505 | Attribute | Value | 506 +----------------------+------------------+ 507 | Address Block | ::1/128 | 508 | Name | Loopback Address | 509 | RFC | [RFC4291] | 510 | Allocation Date | February 2006 | 511 | Termination Date | N/A | 512 | Source | False | 513 | Destination | False | 514 | Forwardable | False | 515 | Global | False | 516 | Reserved-by-protocol | True | 517 +----------------------+------------------+ 519 Table 17: Loopback Address 521 +----------------------+---------------------+ 522 | Attribute | Value | 523 +----------------------+---------------------+ 524 | Address Block | ::/128 | 525 | Name | Unspecified Address | 526 | RFC | [RFC4291] | 527 | Allocation Date | February 2006 | 528 | Termination Date | N/A | 529 | Source | True | 530 | Destination | False | 531 | Forwardable | False | 532 | Global | False | 533 | Reserved-by-protocol | True | 534 +----------------------+---------------------+ 536 Table 18: Unspecified Address 538 +----------------------+---------------------+ 539 | Attribute | Value | 540 +----------------------+---------------------+ 541 | Address Block | ::FFFF:0:0/96 | 542 | Name | IPv4-mapped Address | 543 | RFC | [RFC4291] | 544 | Allocation Date | February 2006 | 545 | Termination Date | N/A | 546 | Source | False | 547 | Destination | False | 548 | Forwardable | False | 549 | Global | False | 550 | Reserved-by-protocol | True | 551 +----------------------+---------------------+ 553 Table 19: IPv4-mapped Address 555 +----------------------+----------------------------+ 556 | Attribute | Value | 557 +----------------------+----------------------------+ 558 | Address Block | 0100::/64 | 559 | Name | Discard-Only Address Block | 560 | RFC | [RFC6666] | 561 | Allocation Date | June 2012 | 562 | Termination Date | N/A | 563 | Source | True | 564 | Destination | True | 565 | Forwardable | True | 566 | Global | False | 567 | Reserved-by-protocol | False | 568 +----------------------+----------------------------+ 570 Table 20: Discard-Only Prefix 572 +----------------------+---------------------------+ 573 | Attribute | Value | 574 +----------------------+---------------------------+ 575 | Address Block | 2001:0000::/23 | 576 | Name | IETF Protocol Assignments | 577 | RFC | [RFC2928] | 578 | Allocation Date | September 2000 | 579 | Termination Date | N/A | 580 | Source | False[3] | 581 | Destination | False[3] | 582 | Forwardable | False[3] | 583 | Global | False[3] | 584 | Reserved-by-protocol | False | 585 +----------------------+---------------------------+ 587 Table 21: IETF Protocol Assignments 589 [3] Unless allowed by a more specific allocation 591 +----------------------+----------------+ 592 | Attribute | Value | 593 +----------------------+----------------+ 594 | Address Block | 2001:0000::/32 | 595 | Name | TEREDO | 596 | RFC | [RFC4380] | 597 | Allocation Date | January 2006 | 598 | Termination Date | N/A | 599 | Source | True | 600 | Destination | True | 601 | Forwardable | True | 602 | Global | False | 603 | Reserved-by-protocol | False | 604 +----------------------+----------------+ 606 Table 22: TEREDO 608 +----------------------+----------------+ 609 | Attribute | Value | 610 +----------------------+----------------+ 611 | Address Block | 2001:0002::/48 | 612 | Name | Benchmarking | 613 | RFC | [RFC5180] | 614 | Allocation Date | April 2008 | 615 | Termination Date | N/A | 616 | Source | True | 617 | Destination | True | 618 | Forwardable | True | 619 | Global | False | 620 | Reserved-by-protocol | False | 621 +----------------------+----------------+ 623 Table 23: Benchmarking 625 +----------------------+---------------+ 626 | Attribute | Value | 627 +----------------------+---------------+ 628 | Address Block | 2001:db8::/32 | 629 | Name | Documentation | 630 | RFC | [RFC3849] | 631 | Allocation Date | July 2004 | 632 | Termination Date | N/A | 633 | Source | False | 634 | Destination | False | 635 | Forwardable | False | 636 | Global | False | 637 | Reserved-by-protocol | False | 638 +----------------------+---------------+ 640 Table 24: Documentation 642 +----------------------+--------------+ 643 | Attribute | Value | 644 +----------------------+--------------+ 645 | Address Block | 2001:10::/28 | 646 | Name | ORCHID | 647 | RFC | [RFC4843] | 648 | Allocation Date | March 2007 | 649 | Termination Date | March 2014 | 650 | Source | False | 651 | Destination | False | 652 | Forwardable | False | 653 | Global | False | 654 | Reserved-by-protocol | False | 655 +----------------------+--------------+ 657 Table 25: ORCHID 659 +----------------------+---------------+ 660 | Attribute | Value | 661 +----------------------+---------------+ 662 | Address Block | 2002::/16 [4] | 663 | Name | 6to4 | 664 | RFC | [RFC3056] | 665 | Allocation Date | February 2001 | 666 | Termination Date | N/A | 667 | Source | True | 668 | Destination | True | 669 | Forwardable | True | 670 | Global | N/A[4] | 671 | Reserved-by-protocol | False | 672 +----------------------+---------------+ 674 Table 26: 6to4 676 [4] See [RFC3056] for details. 678 +----------------------+--------------+ 679 | Attribute | Value | 680 +----------------------+--------------+ 681 | Address Block | FC00::/7 | 682 | Name | Unique-Local | 683 | RFC | [RFC4193] | 684 | Allocation Date | October 2005 | 685 | Termination Date | N/A | 686 | Source | True | 687 | Destination | True | 688 | Forwardable | True | 689 | Global | False | 690 | Reserved-by-protocol | False | 691 +----------------------+--------------+ 693 Table 27: Unique-Local 695 +----------------------+-----------------------+ 696 | Attribute | Value | 697 +----------------------+-----------------------+ 698 | Address Block | FE80::/10 | 699 | Name | Linked-Scoped Unicast | 700 | RFC | [RFC4291] | 701 | Allocation Date | February 2006 | 702 | Termination Date | N/A | 703 | Source | True | 704 | Destination | True | 705 | Forwardable | False | 706 | Global | False | 707 | Reserved-by-protocol | True | 708 +----------------------+-----------------------+ 710 Table 28: Linked-Scoped Unicast 712 3. Security Considerations 714 Security of the Internet's routing system relies on the ability to 715 authenticate an assertion of unique control of an address block. 716 Measures to authenticate such assertions rely on validation that the 717 address block forms part of an existing allocated address block, and 718 that there is a trustable and unique reference in the IANA address 719 registries. 721 The proposed registry is intended to provide an authoritative source 722 of information regarding the currency and intended purpose of special 723 purpose address blocks that are designated from the IANA-administered 724 Special Purpose registry. This is a small step towards the creation 725 of a comprehensive registry framework that can be used as a trust 726 point for commencing a chain of address validation. Consideration 727 should be given to IANA registry publication formats that are machine 728 parseable, and also the use of file signatures and associated 729 certificate mechanisms to allow applications to confirm that the 730 registry contents are current, and that they have been published by 731 the IANA. 733 4. Acknowledgements 735 The authors thank Geoff Huston and Randy Bush for their helpful 736 comments. The authors also express their gratitude to an anonymous 737 donor, without whom this document would not have been written. 739 5. Informative References 741 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 742 RFC 919, October 1984. 744 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 745 RFC 1112, August 1989. 747 [RFC1122] Braden, R., "Requirements for Internet Hosts - 748 Communication Layers", STD 3, RFC 1122, October 1989. 750 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 751 E. Lear, "Address Allocation for Private Internets", 752 BCP 5, RFC 1918, February 1996. 754 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 755 Network Interconnect Devices", RFC 2544, March 1999. 757 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 758 Understanding Concerning the Technical Work of the 759 Internet Assigned Numbers Authority", RFC 2860, June 2000. 761 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 762 IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. 764 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 765 via IPv4 Clouds", RFC 3056, February 2001. 767 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", 768 RFC 3068, June 2001. 770 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 771 Reserved for Documentation", RFC 3849, July 2004. 773 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 774 Configuration of IPv4 Link-Local Addresses", RFC 3927, 775 May 2005. 777 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 778 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 779 March 2005. 781 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 782 Addresses", RFC 4193, October 2005. 784 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 785 Architecture", RFC 4291, February 2006. 787 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 788 Label Switched (MPLS) Data Plane Failures", RFC 4379, 789 February 2006. 791 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 792 Network Address Translations (NATs)", RFC 4380, 793 February 2006. 795 [RFC4773] Huston, G., "Administration of the IANA Special Purpose 796 IPv6 Address Block", RFC 4773, December 2006. 798 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 799 for Overlay Routable Cryptographic Hash Identifiers 800 (ORCHID)", RFC 4843, April 2007. 802 [RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, 803 April 2008. 805 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 806 Dugatkin, "IPv6 Benchmarking Methodology for Network 807 Interconnect Devices", RFC 5180, May 2008. 809 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 810 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 811 May 2008. 813 [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", 814 BCP 153, RFC 5735, January 2010. 816 [RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special 817 Purpose Address Registry", RFC 5736, January 2010. 819 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 820 Reserved for Documentation", RFC 5737, January 2010. 822 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 823 "Bidirectional Forwarding Detection (BFD) for MPLS Label 824 Switched Paths (LSPs)", RFC 5884, June 2010. 826 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 827 Stack Lite Broadband Deployments Following IPv4 828 Exhaustion", RFC 6333, August 2011. 830 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 831 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 832 Space", BCP 153, RFC 6598, April 2012. 834 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 835 RFC 6666, August 2012. 837 Authors' Addresses 839 Michelle Cotton 840 Internet Corporation for Assigned Names and Numbers 841 12025 Waterfront Drive, Suite 300 842 Los Angeles, CA 90094-2536 843 USA 845 Phone: +310-823-9358 846 Fax: 847 Email: michelle.cotton@icann.org 848 URI: http://www.icann.org/ 850 Leo Vegoda 851 Internet Corporation for Assigned Names and Numbers 852 12025 Waterfront Drive, Suite 300 853 LosAngeles, CA 90094-2536 854 USA 856 Phone: +310-823-9358 857 Fax: 858 Email: leo.vegoda@icann.org 859 URI: http://www.icann.org/ 860 Ronald P Bonica (editor) 861 Juniper Networks 862 2251 Corporate Park Drive 863 Herndon, Virginia 20171 864 USA 866 Email: ron.bonica@verizon.net 868 Brian Haberman 869 Johns Hopkins University Applied Physics Lab 870 11100 Johns Hopkins Road 871 Laurel, Maryland 20723-6099 872 USA 874 Email: brian@innovationslab.net