idnits 2.17.00 (12 Aug 2021) /tmp/idnits54308/draft-bchv-rfc6890bis-03.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 15 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 10 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 6, 2017) is 1930 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 687 -- Looks like a reference, but probably isn't: '2' on line 853 -- Looks like a reference, but probably isn't: '3' on line 792 -- Looks like a reference, but probably isn't: '4' on line 795 -- Looks like a reference, but probably isn't: '5' on line 797 -- Looks like a reference, but probably isn't: '6' on line 867 -- Looks like a reference, but probably isn't: '7' on line 903 -- Obsolete informational reference (is this intentional?): RFC 4379 (Obsoleted by RFC 8029) -- Obsolete informational reference (is this intentional?): RFC 4843 (Obsoleted by RFC 7343) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Bonica 3 Internet-Draft Juniper Networks 4 Obsoletes: 6890 (if approved) M. Cotton 5 Intended status: Best Current Practice ICANN 6 Expires: August 10, 2017 B. Haberman 7 Johns Hopkins University 8 L. Vegoda 9 ICANN 10 February 6, 2017 12 Special-Purpose IP Address Registries 13 draft-bchv-rfc6890bis-03 15 Abstract 17 This memo updates the IANA IPv6 Special-Purpose Address Registries to 18 address issues raised by the definition of a global prefix. For 19 completeness, this memo contains all the assignments made by RFC 6890 20 to the IANA Special-Purpose Address Registries. 22 This memo obsoletes RFC 6890. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 10, 2017. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 60 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 3 62 3.2. Restructuring of the IPv4 and IPv6 Special-Purpose 63 Address Registries . . . . . . . . . . . . . . . . . . . 3 64 3.2.1. Information Requirements . . . . . . . . . . . . . . 4 65 3.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 5 66 3.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 15 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . 25 68 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 69 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 70 6.1. Normative References . . . . . . . . . . . . . . . . . . 26 71 6.2. Informative References . . . . . . . . . . . . . . . . . 26 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 74 1. Introduction 76 In order to support new protocols and practices, the IETF 77 occasionally reserves an address block for a 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 Several issues have been raised with the documentation of some of the 84 special-purpose address blocks in [RFC6890]. Specifically, the 85 definition of global provided in [RFC6890] was misleading as it 86 slightly differed from the generally accepted definition of "global 87 scope" (i.e., the ability to forward beyond the boundaries of an 88 administrative domain, described as "global unicast" in the IPv6 89 addressing architecture [RFC4291]). 91 This memo reiterates the assignments made to the IPv4 and IPv6 92 Special-Purpose Address Registries and augments the fields contained 93 within the registries in order to address the confusion raised by the 94 definition of "global". 96 This memo obsoletes [RFC6890]. 98 2. Requirements Language 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 3. IANA Considerations 106 3.1. Assignment of an IPv4 Address Block to IANA 108 Table 7 of this document records the assignment of an IPv4 address 109 block (192.0.0.0/24) to IANA for IETF protocol assignments. This 110 address allocation to IANA is intended to support IETF protocol 111 assignments. A more general view of the roles of IANA with respect 112 to address allocation functions is documented in Sections 4.1 and 4.3 113 [RFC2860]. 115 IANA has designated special-purpose address blocks in compliance with 116 [RFC2860]. 118 3.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address 119 Registries 121 IANA has restructured the following registries: 123 IPv4 Special-Purpose Address Registry 125 IPv6 Special-Purpose Address Registry 127 The IPv4 Special-Purpose Address Registry records all IPv4 special- 128 purpose address blocks. These reservations include, but are not 129 limited to, allocations from the 192.0.0.0/24 address block. 130 Likewise, the IPv6 Special-Purpose Address Registry records all IPv6 131 special-purpose address blocks. These reservations include, but are 132 not limited to, allocations from the 2001:0000::/23 address block, 133 which is a globally scoped address block. 135 Section 3.2.1 of this document describes information that both 136 registries will maintain for each entry. IANA has populated the IPv4 137 Special-Purpose Address Registry with information taken from 138 Section 3.2.2 of this document. Likewise, IANA has populated the 139 IPv6 Special-Purpose Address Registry with information taken from 140 Section 3.2.3 of this document. 142 IANA will update the aforementioned registries as requested in the 143 "IANA Considerations" section of a document that has passed IETF 144 Review [RFC5226]. The "IANA Considerations" section MUST include all 145 of the information specified in Section 3.2.1 of this document. 147 3.2.1. Information Requirements 149 The IPv4 and IPv6 Special-Purpose Address Registries maintain the 150 following information regarding each entry: 152 Address Block - A block of IPv4 or IPv6 addresses that has been 153 registered for a special purpose. 155 Name - A descriptive name for the special-purpose address block. 157 RFC - The RFC through which the special-purpose address block was 158 requested. 160 Allocation Date - The date upon which the special-purpose address 161 block was allocated. 163 Termination Date - The date upon which the allocation is to be 164 terminated. This field is applicable for limited-use allocations 165 only. 167 Source - A boolean value indicating whether an address from the 168 allocated special-purpose address block is valid when used as the 169 source address of an IP datagram that transits two devices. 171 Destination - A boolean value indicating whether an address from 172 the allocated special-purpose address block is valid when used as 173 the destination address of an IP datagram that transits two 174 devices. 176 Forwardable - A boolean value indicating whether a router may 177 forward an IP datagram whose destination address is drawn from the 178 allocated special-purpose address block between external 179 interfaces (i.e., different administrative domains). 181 Globally Reachable - A boolean value indicating whether an IP 182 datagram whose destination address is drawn from the allocated 183 special-purpose address block is forwardable beyond a specified 184 administrative domain. 186 Reserved-by-Protocol - A boolean value indicating whether the 187 special-purpose address block is reserved by IP, itself. This 188 value is "TRUE" if the RFC that created the special-purpose 189 address block requires all compliant IP implementations to behave 190 in a special way when processing packets either to or from 191 addresses contained by the address block. 193 If the value of "Destination" is FALSE, the values of "Forwardable" 194 and "Globally Reachable" must also be FALSE. 196 3.2.2. IPv4 Special-Purpose Address Registry Entries 198 Table 1 through Table 22, below, represent entries with which IANA 199 has initially populated the IPv4 Special-Purpose Address Registry. 201 +----------------------+-----------------------------+ 202 | Attribute | Value | 203 +----------------------+-----------------------------+ 204 | Address Block | 0.0.0.0/8 | 205 | Name | "This host on this network" | 206 | RFC | [RFC1122], Section 3.2.1.3 | 207 | Allocation Date | September 1981 | 208 | Termination Date | N/A | 209 | Source | True | 210 | Destination | False | 211 | Forwardable | False | 212 | Globally Reachable | False | 213 | Reserved-by-Protocol | True | 214 +----------------------+-----------------------------+ 216 Table 1: This host on this network 218 +----------------------+---------------+ 219 | Attribute | Value | 220 +----------------------+---------------+ 221 | Address Block | 10.0.0.0/8 | 222 | Name | Private-Use | 223 | RFC | [RFC1918] | 224 | Allocation Date | February 1996 | 225 | Termination Date | N/A | 226 | Source | True | 227 | Destination | True | 228 | Forwardable | True | 229 | Globally Reachable | False | 230 | Reserved-by-Protocol | False | 231 +----------------------+---------------+ 233 Table 2: Private-Use Networks 235 +----------------------+----------------------+ 236 | Attribute | Value | 237 +----------------------+----------------------+ 238 | Address Block | 100.64.0.0/10 | 239 | Name | Shared Address Space | 240 | RFC | [RFC6598] | 241 | Allocation Date | April 2012 | 242 | Termination Date | N/A | 243 | Source | True | 244 | Destination | True | 245 | Forwardable | True | 246 | Globally Reachable | False | 247 | Reserved-by-Protocol | False | 248 +----------------------+----------------------+ 250 Table 3: Shared Address Space 252 +----------------------+----------------------------+ 253 | Attribute | Value | 254 +----------------------+----------------------------+ 255 | Address Block | 127.0.0.0/8 | 256 | Name | Loopback | 257 | RFC | [RFC1122], Section 3.2.1.3 | 258 | Allocation Date | September 1981 | 259 | Termination Date | N/A | 260 | Source | False [1] | 261 | Destination | False [1] | 262 | Forwardable | False [1] | 263 | Globally Reachable | False [1] | 264 | Reserved-by-Protocol | True | 265 +----------------------+----------------------------+ 267 Table 4: Loopback 269 [1] Several protocols have been granted exceptions to this rule. For 270 examples, see [RFC4379] and [RFC5884]. 272 +----------------------+----------------+ 273 | Attribute | Value | 274 +----------------------+----------------+ 275 | Address Block | 169.254.0.0/16 | 276 | Name | Link Local | 277 | RFC | [RFC3927] | 278 | Allocation Date | May 2005 | 279 | Termination Date | N/A | 280 | Source | True | 281 | Destination | True | 282 | Forwardable | False | 283 | Globally Reachable | False | 284 | Reserved-by-Protocol | True | 285 +----------------------+----------------+ 287 Table 5: Link Local 289 +----------------------+---------------+ 290 | Attribute | Value | 291 +----------------------+---------------+ 292 | Address Block | 172.16.0.0/12 | 293 | Name | Private-Use | 294 | RFC | [RFC1918] | 295 | Allocation Date | February 1996 | 296 | Termination Date | N/A | 297 | Source | True | 298 | Destination | True | 299 | Forwardable | True | 300 | Globally Reachable | False | 301 | Reserved-by-Protocol | False | 302 +----------------------+---------------+ 304 Table 6: Private-Use Networks 306 +----------------------+------------------------------+ 307 | Attribute | Value | 308 +----------------------+------------------------------+ 309 | Address Block | 192.0.0.0/24 [2] | 310 | Name | IETF Protocol Assignments | 311 | RFC | Section 2.1 of this document | 312 | Allocation Date | January 2010 | 313 | Termination Date | N/A | 314 | Source | False | 315 | Destination | False | 316 | Forwardable | False | 317 | Globally Reachable | False | 318 | Reserved-by-Protocol | False | 319 +----------------------+------------------------------+ 321 Table 7: IETF Protocol Assignments 323 [2] Not usable unless by virtue of a more specific reservation. 325 +----------------------+--------------------------------+ 326 | Attribute | Value | 327 +----------------------+--------------------------------+ 328 | Address Block | 192.0.0.0/29 | 329 | Name | IPv4 Service Continuity Prefix | 330 | RFC | [RFC7335] | 331 | Allocation Date | June 2011 | 332 | Termination Date | N/A | 333 | Source | True | 334 | Destination | True | 335 | Forwardable | True | 336 | Globally Reachable | False | 337 | Reserved-by-Protocol | False | 338 +----------------------+--------------------------------+ 340 Table 8: IPv4 Service Continuity 342 +----------------------+--------------------+ 343 | Attribute | Value | 344 +----------------------+--------------------+ 345 | Address Block | 192.0.0.8/32 | 346 | Name | IPv4 dummy address | 347 | RFC | [RFC7600] | 348 | Allocation Date | March 2015 | 349 | Termination Date | N/A | 350 | Source | True | 351 | Destination | False | 352 | Forwardable | False | 353 | Globally Reachable | False | 354 | Reserved-by-Protocol | False | 355 +----------------------+--------------------+ 357 Table 9: IPv4 Dummy Address 359 +----------------------+-------------------------------+ 360 | Attribute | Value | 361 +----------------------+-------------------------------+ 362 | Address Block | 192.0.0.9/32 | 363 | Name | Port Control Protocol Anycast | 364 | RFC | [RFC7723] | 365 | Allocation Date | October 2015 | 366 | Termination Date | N/A | 367 | Source | True | 368 | Destination | True | 369 | Forwardable | True | 370 | Globally Reachable | True | 371 | Reserved-by-Protocol | False | 372 +----------------------+-------------------------------+ 374 Table 10: PCP Anycast 376 +----------------------+--------------------------------+ 377 | Attribute | Value | 378 +----------------------+--------------------------------+ 379 | Address Block | 192.0.0.170/32, 192.0.0.171/32 | 380 | Name | NAT64/DNS64 Discovery | 381 | RFC | [RFC7050] | 382 | Allocation Date | February 2013 | 383 | Termination Date | N/A | 384 | Source | False | 385 | Destination | False | 386 | Forwardable | False | 387 | Globally Reachable | False | 388 | Reserved-by-Protocol | True | 389 +----------------------+--------------------------------+ 391 Table 11: NAT64/DNS64 Discovery 393 +----------------------+----------------------------+ 394 | Attribute | Value | 395 +----------------------+----------------------------+ 396 | Address Block | 192.0.2.0/24 | 397 | Name | Documentation (TEST-NET-1) | 398 | RFC | [RFC5737] | 399 | Allocation Date | January 2010 | 400 | Termination Date | N/A | 401 | Source | False | 402 | Destination | False | 403 | Forwardable | False | 404 | Globally Reachable | False | 405 | Reserved-by-Protocol | False | 406 +----------------------+----------------------------+ 408 Table 12: TEST-NET-1 410 +----------------------+-----------------+ 411 | Attribute | Value | 412 +----------------------+-----------------+ 413 | Address Block | 192.31.196.0/24 | 414 | Name | AS112-v4 | 415 | RFC | [RFC7535] | 416 | Allocation Date | December 2014 | 417 | Termination Date | N/A | 418 | Source | True | 419 | Destination | True | 420 | Forwardable | True | 421 | Globally Reachable | True | 422 | Reserved-by-Protocol | False | 423 +----------------------+-----------------+ 425 Table 13: AS112 - IPv4 427 +----------------------+-----------------+ 428 | Attribute | Value | 429 +----------------------+-----------------+ 430 | Address Block | 192.52.193.0/24 | 431 | Name | AMT | 432 | RFC | [RFC7450] | 433 | Allocation Date | December 2014 | 434 | Termination Date | N/A | 435 | Source | True | 436 | Destination | True | 437 | Forwardable | True | 438 | Globally Reachable | True | 439 | Reserved-by-Protocol | False | 440 +----------------------+-----------------+ 442 Table 14: Automatic Multicast Tunneling 444 +----------------------+-------------------------------+ 445 | Attribute | Value | 446 +----------------------+-------------------------------+ 447 | Address Block | 192.88.99.0/24 | 448 | Name | Deprecated 6to4 Relay Anycast | 449 | RFC | [RFC7526] | 450 | Allocation Date | June 2001 | 451 | Termination Date | March 2015 | 452 | Source | N/A | 453 | Destination | N/A | 454 | Forwardable | N/A | 455 | Globally Reachable | N/A | 456 | Reserved-by-Protocol | N/A | 457 +----------------------+-------------------------------+ 459 Table 15: 6to4 Relay Anycast 461 +----------------------+----------------+ 462 | Attribute | Value | 463 +----------------------+----------------+ 464 | Address Block | 192.168.0.0/16 | 465 | Name | Private-Use | 466 | RFC | [RFC1918] | 467 | Allocation Date | February 1996 | 468 | Termination Date | N/A | 469 | Source | True | 470 | Destination | True | 471 | Forwardable | True | 472 | Globally Reachable | False | 473 | Reserved-by-Protocol | False | 474 +----------------------+----------------+ 476 Table 16: Private-Use Networks 478 +----------------------+-----------------+ 479 | Attribute | Value | 480 +----------------------+-----------------+ 481 | Address Block | 192.175.48.0/24 | 482 | Name | Private-Use | 483 | RFC | [RFC7534] | 484 | Allocation Date | January 1996 | 485 | Termination Date | N/A | 486 | Source | True | 487 | Destination | True | 488 | Forwardable | True | 489 | Globally Reachable | True | 490 | Reserved-by-Protocol | False | 491 +----------------------+-----------------+ 493 Table 17: Direct Delegation AS112 Service 495 +----------------------+---------------+ 496 | Attribute | Value | 497 +----------------------+---------------+ 498 | Address Block | 198.18.0.0/15 | 499 | Name | Benchmarking | 500 | RFC | [RFC2544] | 501 | Allocation Date | March 1999 | 502 | Termination Date | N/A | 503 | Source | True | 504 | Destination | True | 505 | Forwardable | True | 506 | Globally Reachable | False | 507 | Reserved-by-Protocol | False | 508 +----------------------+---------------+ 510 Table 18: Network Interconnect Device Benchmark Testing 511 +----------------------+----------------------------+ 512 | Attribute | Value | 513 +----------------------+----------------------------+ 514 | Address Block | 198.51.100.0/24 | 515 | Name | Documentation (TEST-NET-2) | 516 | RFC | [RFC5737] | 517 | Allocation Date | January 2010 | 518 | Termination Date | N/A | 519 | Source | False | 520 | Destination | False | 521 | Forwardable | False | 522 | Globally Reachable | False | 523 | Reserved-by-Protocol | False | 524 +----------------------+----------------------------+ 526 Table 19: TEST-NET-2 528 +----------------------+----------------------------+ 529 | Attribute | Value | 530 +----------------------+----------------------------+ 531 | Address Block | 203.0.113.0/24 | 532 | Name | Documentation (TEST-NET-3) | 533 | RFC | [RFC5737] | 534 | Allocation Date | January 2010 | 535 | Termination Date | N/A | 536 | Source | False | 537 | Destination | False | 538 | Forwardable | False | 539 | Globally Reachable | False | 540 | Reserved-by-Protocol | False | 541 +----------------------+----------------------------+ 543 Table 20: TEST-NET-3 545 +----------------------+----------------------+ 546 | Attribute | Value | 547 +----------------------+----------------------+ 548 | Address Block | 240.0.0.0/4 | 549 | Name | Reserved | 550 | RFC | [RFC1112], Section 4 | 551 | Allocation Date | August 1989 | 552 | Termination Date | N/A | 553 | Source | False | 554 | Destination | False | 555 | Forwardable | False | 556 | Globally Reachable | False | 557 | Reserved-by-Protocol | True | 558 +----------------------+----------------------+ 560 Table 21: Reserved for Future Use 562 +----------------------+----------------------+ 563 | Attribute | Value | 564 +----------------------+----------------------+ 565 | Address Block | 255.255.255.255/32 | 566 | Name | Limited Broadcast | 567 | RFC | [RFC0919], Section 7 | 568 | Allocation Date | October 1984 | 569 | Termination Date | N/A | 570 | Source | False | 571 | Destination | True | 572 | Forwardable | False | 573 | Globally Reachable | False | 574 | Reserved-by-Protocol | True | 575 +----------------------+----------------------+ 577 Table 22: Limited Broadcast 579 3.2.3. IPv6 Special-Purpose Address Registry Entries 581 Table 23 through Table 41, below, represent entries with which the 582 IANA has initially populated the IPv6 Special-Purpose Address 583 Registry. 585 +----------------------+------------------+ 586 | Attribute | Value | 587 +----------------------+------------------+ 588 | Address Block | ::1/128 | 589 | Name | Loopback Address | 590 | RFC | [RFC4291] | 591 | Allocation Date | February 2006 | 592 | Termination Date | N/A | 593 | Source | False | 594 | Destination | False | 595 | Forwardable | False | 596 | Globally Reachable | False | 597 | Reserved-by-Protocol | True | 598 +----------------------+------------------+ 600 Table 23: Loopback Address 602 +----------------------+---------------------+ 603 | Attribute | Value | 604 +----------------------+---------------------+ 605 | Address Block | ::/128 | 606 | Name | Unspecified Address | 607 | RFC | [RFC4291] | 608 | Allocation Date | February 2006 | 609 | Termination Date | N/A | 610 | Source | True | 611 | Destination | False | 612 | Forwardable | False | 613 | Globally Reachable | False | 614 | Reserved-by-Protocol | True | 615 +----------------------+---------------------+ 617 Table 24: Unspecified Address 619 +----------------------+---------------------+ 620 | Attribute | Value | 621 +----------------------+---------------------+ 622 | Address Block | ::ffff:0:0/96 | 623 | Name | IPv4-mapped Address | 624 | RFC | [RFC4291] | 625 | Allocation Date | February 2006 | 626 | Termination Date | N/A | 627 | Source | False | 628 | Destination | False | 629 | Forwardable | False | 630 | Globally Reachable | False | 631 | Reserved-by-Protocol | True | 632 +----------------------+---------------------+ 634 Table 25: IPv4-Mapped Address 636 +----------------------+---------------------+ 637 | Attribute | Value | 638 +----------------------+---------------------+ 639 | Address Block | 64:ff9b::/96 | 640 | Name | IPv4-IPv6 Translat. | 641 | RFC | [RFC6052] | 642 | Allocation Date | October 2010 | 643 | Termination Date | N/A | 644 | Source | True | 645 | Destination | True | 646 | Forwardable | True | 647 | Globally Reachable | True | 648 | Reserved-by-Protocol | False | 649 +----------------------+---------------------+ 651 Table 26: IPv4-IPv6 Translation Address 653 +----------------------+----------------------------+ 654 | Attribute | Value | 655 +----------------------+----------------------------+ 656 | Address Block | 100::/64 | 657 | Name | Discard-Only Address Block | 658 | RFC | [RFC6666] | 659 | Allocation Date | June 2012 | 660 | Termination Date | N/A | 661 | Source | True | 662 | Destination | True | 663 | Forwardable | True | 664 | Globally Reachable | False | 665 | Reserved-by-Protocol | False | 666 +----------------------+----------------------------+ 668 Table 27: Discard-Only Prefix 670 +----------------------+---------------------------+ 671 | Attribute | Value | 672 +----------------------+---------------------------+ 673 | Address Block | 2001::/23 | 674 | Name | IETF Protocol Assignments | 675 | RFC | [RFC2928] | 676 | Allocation Date | September 2000 | 677 | Termination Date | N/A | 678 | Source | False[1] | 679 | Destination | False[1] | 680 | Forwardable | False[1] | 681 | Globally Reachable | False[1] | 682 | Reserved-by-Protocol | False | 683 +----------------------+---------------------------+ 685 Table 28: IETF Protocol Assignments 687 [1] Unless allowed by a more specific allocation. 689 +----------------------+--------------+ 690 | Attribute | Value | 691 +----------------------+--------------+ 692 | Address Block | 2001::/32 | 693 | Name | TEREDO | 694 | RFC | [RFC4380] | 695 | Allocation Date | January 2006 | 696 | Termination Date | N/A | 697 | Source | True | 698 | Destination | True | 699 | Forwardable | True | 700 | Globally Reachable | N/A [2] | 701 | Reserved-by-Protocol | False | 702 +----------------------+--------------+ 704 Table 29: TEREDO 706 [2] See [RFC4380] for details. 708 +----------------------+-------------------------------+ 709 | Attribute | Value | 710 +----------------------+-------------------------------+ 711 | Address Block | 2001:1::1/128 | 712 | Name | Port Control Protocol Anycast | 713 | RFC | [RFC7723] | 714 | Allocation Date | November 2015 | 715 | Termination Date | N/A | 716 | Source | True | 717 | Destination | True | 718 | Forwardable | True | 719 | Globally Reachable | True | 720 | Reserved-by-Protocol | False | 721 +----------------------+-------------------------------+ 723 Table 30: Port Control Protocol Anycast 724 +----------------------+--------------+ 725 | Attribute | Value | 726 +----------------------+--------------+ 727 | Address Block | 2001:2::/48 | 728 | Name | Benchmarking | 729 | RFC | [RFC5180] | 730 | Allocation Date | April 2008 | 731 | Termination Date | N/A | 732 | Source | True | 733 | Destination | True | 734 | Forwardable | True | 735 | Globally Reachable | False | 736 | Reserved-by-Protocol | False | 737 +----------------------+--------------+ 739 Table 31: Benchmarking 741 +----------------------+---------------+ 742 | Attribute | Value | 743 +----------------------+---------------+ 744 | Address Block | 2001:3::/32 | 745 | Name | AMT | 746 | RFC | [RFC7450] | 747 | Allocation Date | December 2014 | 748 | Termination Date | N/A | 749 | Source | True | 750 | Destination | True | 751 | Forwardable | True | 752 | Globally Reachable | True | 753 | Reserved-by-Protocol | False | 754 +----------------------+---------------+ 756 Table 32: Automatic Multicast Tunneling 758 +----------------------+-----------------+ 759 | Attribute | Value | 760 +----------------------+-----------------+ 761 | Address Block | 2001:4:112::/48 | 762 | Name | AS112-v6 | 763 | RFC | [RFC7535] | 764 | Allocation Date | December 2014 | 765 | Termination Date | N/A | 766 | Source | True | 767 | Destination | True | 768 | Forwardable | True | 769 | Globally Reachable | True | 770 | Reserved-by-Protocol | False | 771 +----------------------+-----------------+ 773 Table 33: AS112 - IPv6 775 +----------------------+------------------------------------------+ 776 | Attribute | Value | 777 +----------------------+------------------------------------------+ 778 | Address Block | 2001:5::/32 | 779 | Name | EID Space for LISP (Managed by RIPE NCC) | 780 | RFC | [RFC7954] | 781 | Allocation Date | September 2016 | 782 | Termination Date | September 2019[3] | 783 | Source | True[4] | 784 | Destination | True | 785 | Forwardable | True | 786 | Globally Reachable | True | 787 | Reserved-by-Protocol | True[5] | 788 +----------------------+------------------------------------------+ 790 Table 34: EID Space - LISP 792 [3] According to the 3+3 Plan outlined in [RFC7954], the termination 793 date can be postponed to September 2022. 795 [4] Can be used as a multicast source as well. 797 [5] To be used as EID space by routers enabled by LISP [RFC6830]. 799 +----------------------+--------------------------------+ 800 | Attribute | Value | 801 +----------------------+--------------------------------+ 802 | Address Block | 2001:10::/28 | 803 | Name | Deprecated (previously ORCHID) | 804 | RFC | [RFC4843] | 805 | Allocation Date | March 2007 | 806 | Termination Date | March 2014 | 807 | Source | | 808 | Destination | | 809 | Forwardable | | 810 | Globally Reachable | | 811 | Reserved-by-Protocol | | 812 +----------------------+--------------------------------+ 814 Table 35: ORCHIDv1 - Deprecated 816 +----------------------+--------------+ 817 | Attribute | Value | 818 +----------------------+--------------+ 819 | Address Block | 2001:20::/28 | 820 | Name | ORCHIDv2 | 821 | RFC | [RFC7343] | 822 | Allocation Date | July 2014 | 823 | Termination Date | N/A | 824 | Source | True | 825 | Destination | True | 826 | Forwardable | True | 827 | Globally Reachable | True | 828 | Reserved-by-Protocol | False | 829 +----------------------+--------------+ 831 Table 36: ORCHIDv2 833 +----------------------+---------------+ 834 | Attribute | Value | 835 +----------------------+---------------+ 836 | Address Block | 2001:db8::/32 | 837 | Name | Documentation | 838 | RFC | [RFC3849] | 839 | Allocation Date | July 2004 | 840 | Termination Date | N/A | 841 | Source | False | 842 | Destination | False | 843 | Forwardable | False | 844 | Globally Reachable | False | 845 | Reserved-by-Protocol | False | 846 +----------------------+---------------+ 848 Table 37: Documentation 850 +----------------------+---------------+ 851 | Attribute | Value | 852 +----------------------+---------------+ 853 | Address Block | 2002::/16 [2] | 854 | Name | 6to4 | 855 | RFC | [RFC3056] | 856 | Allocation Date | February 2001 | 857 | Termination Date | N/A | 858 | Source | True | 859 | Destination | True | 860 | Forwardable | True | 861 | Globally Reachable | N/A [6] | 862 | Reserved-by-Protocol | False | 863 +----------------------+---------------+ 865 Table 38: 6to4 867 [6] See [RFC3056] for details. 869 +----------------------+---------------------------------+ 870 | Attribute | Value | 871 +----------------------+---------------------------------+ 872 | Address Block | 2620:4f:8000::/48 | 873 | Name | Direct Delegation AS112 Service | 874 | RFC | [RFC7534] | 875 | Allocation Date | May 2011 | 876 | Termination Date | N/A | 877 | Source | True | 878 | Destination | True | 879 | Forwardable | True | 880 | Globally Reachable | True | 881 | Reserved-by-Protocol | False | 882 +----------------------+---------------------------------+ 884 Table 39: Direct Delegation AS112 Service 886 +----------------------+--------------+ 887 | Attribute | Value | 888 +----------------------+--------------+ 889 | Address Block | fc00::/7 | 890 | Name | Unique-Local | 891 | RFC | [RFC4193] | 892 | Allocation Date | October 2005 | 893 | Termination Date | N/A | 894 | Source | True | 895 | Destination | True | 896 | Forwardable | True | 897 | Globally Reachable | False [7] | 898 | Reserved-by-Protocol | False | 899 +----------------------+--------------+ 901 Table 40: Unique-Local (Private) 903 [7] See [RFC4193] for more details on the routability of Unique-Local 904 addresses. The Unique-Local prefix is drawn from the IPv6 Global 905 Unicast Address range, but is specified as not globally routed. 907 +----------------------+-----------------------+ 908 | Attribute | Value | 909 +----------------------+-----------------------+ 910 | Address Block | fe80::/10 | 911 | Name | Linked-Scoped Unicast | 912 | RFC | [RFC4291] | 913 | Allocation Date | February 2006 | 914 | Termination Date | N/A | 915 | Source | True | 916 | Destination | True | 917 | Forwardable | False | 918 | Globally Reachable | False | 919 | Reserved-by-Protocol | True | 920 +----------------------+-----------------------+ 922 Table 41: Link-Scoped Unicast 924 4. Security Considerations 926 Security of the Internet's routing system relies on the ability to 927 authenticate an assertion of unique control of an address block. 928 Measures to authenticate such assertions rely on validation that the 929 address block forms part of an existing allocated address block and 930 that there is a trustable and unique reference in the IANA address 931 registries. 933 The proposed registry is intended to provide an authoritative source 934 of information regarding the currency and intended purpose of special 935 purpose address blocks that are designated from the IANA-administered 936 Special-Purpose registry. This is a small step towards the creation 937 of a comprehensive registry framework that can be used as a trust 938 point for commencing a chain of address validation. Consideration 939 should be given to IANA registry publication formats that are machine 940 parsable. Additionally, consideration should be given to the use of 941 file signatures and associated certificate mechanisms to allow 942 applications to confirm that the registry contents are current and 943 that they have been published by the IANA. 945 5. Acknowledgements 947 Brian Carpenter and C.M. Heard provided useful comments on initial 948 versions of this document. Daniel Migualt provided an in-depth 949 review that helped strengthen the text within the document. 951 6. References 953 6.1. Normative References 955 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 956 Requirement Levels", BCP 14, RFC 2119, 957 DOI 10.17487/RFC2119, March 1997, 958 . 960 6.2. Informative References 962 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 963 RFC 919, DOI 10.17487/RFC0919, October 1984, 964 . 966 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 967 RFC 1112, DOI 10.17487/RFC1112, August 1989, 968 . 970 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 971 Communication Layers", STD 3, RFC 1122, 972 DOI 10.17487/RFC1122, October 1989, 973 . 975 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 976 and E. Lear, "Address Allocation for Private Internets", 977 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 978 . 980 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 981 Network Interconnect Devices", RFC 2544, 982 DOI 10.17487/RFC2544, March 1999, 983 . 985 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 986 Understanding Concerning the Technical Work of the 987 Internet Assigned Numbers Authority", RFC 2860, 988 DOI 10.17487/RFC2860, June 2000, 989 . 991 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 992 IPv6 Sub-TLA ID Assignments", RFC 2928, 993 DOI 10.17487/RFC2928, September 2000, 994 . 996 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 997 via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February 998 2001, . 1000 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 1001 Reserved for Documentation", RFC 3849, 1002 DOI 10.17487/RFC3849, July 2004, 1003 . 1005 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 1006 Configuration of IPv4 Link-Local Addresses", RFC 3927, 1007 DOI 10.17487/RFC3927, May 2005, 1008 . 1010 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 1011 Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, 1012 . 1014 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 1015 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 1016 2006, . 1018 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 1019 Label Switched (MPLS) Data Plane Failures", RFC 4379, 1020 DOI 10.17487/RFC4379, February 2006, 1021 . 1023 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 1024 Network Address Translations (NATs)", RFC 4380, 1025 DOI 10.17487/RFC4380, February 2006, 1026 . 1028 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 1029 for Overlay Routable Cryptographic Hash Identifiers 1030 (ORCHID)", RFC 4843, DOI 10.17487/RFC4843, April 2007, 1031 . 1033 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 1034 Dugatkin, "IPv6 Benchmarking Methodology for Network 1035 Interconnect Devices", RFC 5180, DOI 10.17487/RFC5180, May 1036 2008, . 1038 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1039 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1040 DOI 10.17487/RFC5226, May 2008, 1041 . 1043 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 1044 Reserved for Documentation", RFC 5737, 1045 DOI 10.17487/RFC5737, January 2010, 1046 . 1048 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1049 "Bidirectional Forwarding Detection (BFD) for MPLS Label 1050 Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, 1051 June 2010, . 1053 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 1054 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 1055 DOI 10.17487/RFC6052, October 2010, 1056 . 1058 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 1059 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 1060 Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April 1061 2012, . 1063 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 1064 RFC 6666, DOI 10.17487/RFC6666, August 2012, 1065 . 1067 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 1068 Locator/ID Separation Protocol (LISP)", RFC 6830, 1069 DOI 10.17487/RFC6830, January 2013, 1070 . 1072 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 1073 "Special-Purpose IP Address Registries", BCP 153, 1074 RFC 6890, DOI 10.17487/RFC6890, April 2013, 1075 . 1077 [RFC7050] Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 1078 the IPv6 Prefix Used for IPv6 Address Synthesis", 1079 RFC 7050, DOI 10.17487/RFC7050, November 2013, 1080 . 1082 [RFC7335] Byrne, C., "IPv4 Service Continuity Prefix", RFC 7335, 1083 DOI 10.17487/RFC7335, August 2014, 1084 . 1086 [RFC7343] Laganier, J. and F. Dupont, "An IPv6 Prefix for Overlay 1087 Routable Cryptographic Hash Identifiers Version 2 1088 (ORCHIDv2)", RFC 7343, DOI 10.17487/RFC7343, September 1089 2014, . 1091 [RFC7450] Bumgardner, G., "Automatic Multicast Tunneling", RFC 7450, 1092 DOI 10.17487/RFC7450, February 2015, 1093 . 1095 [RFC7526] Troan, O. and B. Carpenter, Ed., "Deprecating the Anycast 1096 Prefix for 6to4 Relay Routers", BCP 196, RFC 7526, 1097 DOI 10.17487/RFC7526, May 2015, 1098 . 1100 [RFC7534] Abley, J. and W. Sotomayor, "AS112 Nameserver Operations", 1101 RFC 7534, DOI 10.17487/RFC7534, May 2015, 1102 . 1104 [RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson, 1105 "AS112 Redirection Using DNAME", RFC 7535, 1106 DOI 10.17487/RFC7535, May 2015, 1107 . 1109 [RFC7600] Despres, R., Jiang, S., Ed., Penno, R., Lee, Y., Chen, G., 1110 and M. Chen, "IPv4 Residual Deployment via IPv6 - A 1111 Stateless Solution (4rd)", RFC 7600, DOI 10.17487/RFC7600, 1112 July 2015, . 1114 [RFC7723] Kiesel, S. and R. Penno, "Port Control Protocol (PCP) 1115 Anycast Addresses", RFC 7723, DOI 10.17487/RFC7723, 1116 January 2016, . 1118 [RFC7954] Iannone, L., Lewis, D., Meyer, D., and V. Fuller, 1119 "Locator/ID Separation Protocol (LISP) Endpoint Identifier 1120 (EID) Block", RFC 7954, DOI 10.17487/RFC7954, September 1121 2016, . 1123 Authors' Addresses 1125 Ronald Bonica 1126 Juniper Networks 1128 Email: rbonica@juniper.net 1130 Michelle Cotton 1131 ICANN 1133 Email: michelle.cotton@icann.org 1135 Brian Haberman 1136 Johns Hopkins University 1138 Email: brian@innovationslab.net 1139 Leo Vegoda 1140 ICANN 1142 Email: leo.vegoda@icann.org