idnits 2.17.1 draft-bchv-rfc6890bis-05.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 (March 10, 2017) is 2575 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 695 -- Looks like a reference, but probably isn't: '2' on line 714 -- Looks like a reference, but probably isn't: '3' on line 800 -- Looks like a reference, but probably isn't: '4' on line 803 -- Looks like a reference, but probably isn't: '5' on line 805 -- Looks like a reference, but probably isn't: '6' on line 875 -- Looks like a reference, but probably isn't: '7' on line 911 -- 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) -- Obsolete informational reference (is this intentional?): RFC 6830 (Obsoleted by RFC 9300, RFC 9301) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 12 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: September 11, 2017 B. Haberman 7 Johns Hopkins University 8 L. Vegoda 9 ICANN 10 March 10, 2017 12 Special-Purpose IP Address Registries 13 draft-bchv-rfc6890bis-05 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 to the IANA 20 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 September 11, 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 in [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 124 (https://www.iana.org/assignments/iana-ipv4-special-registry/iana- 125 ipv4-special-registry.xhtml) 127 IPv6 Special-Purpose Address Registry 128 (https://www,iana.org/assignments/iana-ipv6-special-registry/iana- 129 ipv6-special-registry.xhtml) 131 The IPv4 Special-Purpose Address Registry records all IPv4 special- 132 purpose address blocks. These reservations include, but are not 133 limited to, allocations from the 192.0.0.0/24 address block. 134 Likewise, the IPv6 Special-Purpose Address Registry records all IPv6 135 special-purpose address blocks. These reservations include, but are 136 not limited to, allocations from the 2001:0000::/23 address block, 137 which is a globally scoped address block. 139 Section 3.2.1 of this document describes information that both 140 registries will maintain for each entry. IANA has populated the IPv4 141 Special-Purpose Address Registry with information taken from 142 Section 3.2.2 of this document. Likewise, IANA has populated the 143 IPv6 Special-Purpose Address Registry with information taken from 144 Section 3.2.3 of this document. 146 IANA will update the aforementioned registries as requested in the 147 "IANA Considerations" section of a document that has passed IETF 148 Review [RFC5226]. The "IANA Considerations" section MUST include all 149 of the information specified in Section 3.2.1 of this document. 151 3.2.1. Information Requirements 153 The IPv4 and IPv6 Special-Purpose Address Registries maintain the 154 following information regarding each entry: 156 Address Block - A block of IPv4 or IPv6 addresses that has been 157 registered for a special purpose. 159 Name - A descriptive name for the special-purpose address block. 161 RFC - The RFC through which the special-purpose address block was 162 requested. 164 Allocation Date - The date upon which the special-purpose address 165 block was allocated. 167 Termination Date - The date upon which the allocation is to be 168 terminated. This field is applicable for limited-use allocations 169 only. 171 Source - A boolean value indicating whether an address from the 172 allocated special-purpose address block is valid when used as the 173 source address of an IP datagram that transits two devices. 175 Destination - A boolean value indicating whether an address from 176 the allocated special-purpose address block is valid when used as 177 the destination address of an IP datagram that transits two 178 devices. 180 Forwardable - A boolean value indicating whether a router may 181 forward an IP datagram whose destination address is drawn from the 182 allocated special-purpose address block between external 183 interfaces (i.e., different administrative domains). 185 Globally Reachable - A boolean value indicating whether an IP 186 datagram whose destination address is drawn from the allocated 187 special-purpose address block is forwardable beyond a specified 188 administrative domain. 190 Reserved-by-Protocol - A boolean value indicating whether the 191 special-purpose address block is reserved by IP, itself. This 192 value is "TRUE" if the RFC that created the special-purpose 193 address block requires all compliant IP implementations to behave 194 in a special way when processing packets either to or from 195 addresses contained by the address block. 197 If the value of "Destination" is FALSE, the values of "Forwardable" 198 and "Globally Reachable" must also be FALSE. 200 3.2.2. IPv4 Special-Purpose Address Registry Entries 202 Table 1 through Table 22, below, represent entries with which IANA 203 has initially populated the IPv4 Special-Purpose Address Registry. 205 +----------------------+-----------------------------+ 206 | Attribute | Value | 207 +----------------------+-----------------------------+ 208 | Address Block | 0.0.0.0/8 | 209 | Name | "This host on this network" | 210 | RFC | [RFC1122], Section 3.2.1.3 | 211 | Allocation Date | September 1981 | 212 | Termination Date | N/A | 213 | Source | True | 214 | Destination | False | 215 | Forwardable | False | 216 | Globally Reachable | False | 217 | Reserved-by-Protocol | True | 218 +----------------------+-----------------------------+ 220 Table 1: This host on this network 222 +----------------------+---------------+ 223 | Attribute | Value | 224 +----------------------+---------------+ 225 | Address Block | 10.0.0.0/8 | 226 | Name | Private-Use | 227 | RFC | [RFC1918] | 228 | Allocation Date | February 1996 | 229 | Termination Date | N/A | 230 | Source | True | 231 | Destination | True | 232 | Forwardable | True | 233 | Globally Reachable | False | 234 | Reserved-by-Protocol | False | 235 +----------------------+---------------+ 237 Table 2: Private-Use Networks 239 +----------------------+----------------------+ 240 | Attribute | Value | 241 +----------------------+----------------------+ 242 | Address Block | 100.64.0.0/10 | 243 | Name | Shared Address Space | 244 | RFC | [RFC6598] | 245 | Allocation Date | April 2012 | 246 | Termination Date | N/A | 247 | Source | True | 248 | Destination | True | 249 | Forwardable | True | 250 | Globally Reachable | False | 251 | Reserved-by-Protocol | False | 252 +----------------------+----------------------+ 254 Table 3: Shared Address Space 256 +----------------------+----------------------------+ 257 | Attribute | Value | 258 +----------------------+----------------------------+ 259 | Address Block | 127.0.0.0/8 | 260 | Name | Loopback | 261 | RFC | [RFC1122], Section 3.2.1.3 | 262 | Allocation Date | September 1981 | 263 | Termination Date | N/A | 264 | Source | False [1] | 265 | Destination | False [1] | 266 | Forwardable | False [1] | 267 | Globally Reachable | False [1] | 268 | Reserved-by-Protocol | True | 269 +----------------------+----------------------------+ 271 Table 4: Loopback 273 [1] Several protocols have been granted exceptions to this rule. For 274 examples, see [RFC4379] and [RFC5884]. 276 +----------------------+----------------+ 277 | Attribute | Value | 278 +----------------------+----------------+ 279 | Address Block | 169.254.0.0/16 | 280 | Name | Link Local | 281 | RFC | [RFC3927] | 282 | Allocation Date | May 2005 | 283 | Termination Date | N/A | 284 | Source | True | 285 | Destination | True | 286 | Forwardable | False | 287 | Globally Reachable | False | 288 | Reserved-by-Protocol | True | 289 +----------------------+----------------+ 291 Table 5: Link Local 293 +----------------------+---------------+ 294 | Attribute | Value | 295 +----------------------+---------------+ 296 | Address Block | 172.16.0.0/12 | 297 | Name | Private-Use | 298 | RFC | [RFC1918] | 299 | Allocation Date | February 1996 | 300 | Termination Date | N/A | 301 | Source | True | 302 | Destination | True | 303 | Forwardable | True | 304 | Globally Reachable | False | 305 | Reserved-by-Protocol | False | 306 +----------------------+---------------+ 308 Table 6: Private-Use Networks 310 +----------------------+---------------------------+ 311 | Attribute | Value | 312 +----------------------+---------------------------+ 313 | Address Block | 192.0.0.0/24 [2] | 314 | Name | IETF Protocol Assignments | 315 | RFC | Section 2.1 of RFC XXXX | 316 | Allocation Date | January 2010 | 317 | Termination Date | N/A | 318 | Source | False | 319 | Destination | False | 320 | Forwardable | False | 321 | Globally Reachable | False | 322 | Reserved-by-Protocol | False | 323 +----------------------+---------------------------+ 325 Table 7: IETF Protocol Assignments 327 [2] Not usable unless by virtue of a more specific reservation. 329 RFC Editor NOTE : Please update XXXX in the above table with the RFC 330 number assigned to this document. This note can be removed prior to 331 publication. 333 +----------------------+--------------------------------+ 334 | Attribute | Value | 335 +----------------------+--------------------------------+ 336 | Address Block | 192.0.0.0/29 | 337 | Name | IPv4 Service Continuity Prefix | 338 | RFC | [RFC7335] | 339 | Allocation Date | June 2011 | 340 | Termination Date | N/A | 341 | Source | True | 342 | Destination | True | 343 | Forwardable | True | 344 | Globally Reachable | False | 345 | Reserved-by-Protocol | False | 346 +----------------------+--------------------------------+ 348 Table 8: IPv4 Service Continuity 350 +----------------------+--------------------+ 351 | Attribute | Value | 352 +----------------------+--------------------+ 353 | Address Block | 192.0.0.8/32 | 354 | Name | IPv4 dummy address | 355 | RFC | [RFC7600] | 356 | Allocation Date | March 2015 | 357 | Termination Date | N/A | 358 | Source | True | 359 | Destination | False | 360 | Forwardable | False | 361 | Globally Reachable | False | 362 | Reserved-by-Protocol | False | 363 +----------------------+--------------------+ 365 Table 9: IPv4 Dummy Address 367 +----------------------+-------------------------------+ 368 | Attribute | Value | 369 +----------------------+-------------------------------+ 370 | Address Block | 192.0.0.9/32 | 371 | Name | Port Control Protocol Anycast | 372 | RFC | [RFC7723] | 373 | Allocation Date | October 2015 | 374 | Termination Date | N/A | 375 | Source | True | 376 | Destination | True | 377 | Forwardable | True | 378 | Globally Reachable | True | 379 | Reserved-by-Protocol | False | 380 +----------------------+-------------------------------+ 382 Table 10: PCP Anycast 384 +----------------------+--------------------------------+ 385 | Attribute | Value | 386 +----------------------+--------------------------------+ 387 | Address Block | 192.0.0.170/32, 192.0.0.171/32 | 388 | Name | NAT64/DNS64 Discovery | 389 | RFC | [RFC7050] | 390 | Allocation Date | February 2013 | 391 | Termination Date | N/A | 392 | Source | False | 393 | Destination | False | 394 | Forwardable | False | 395 | Globally Reachable | False | 396 | Reserved-by-Protocol | True | 397 +----------------------+--------------------------------+ 399 Table 11: NAT64/DNS64 Discovery 401 +----------------------+----------------------------+ 402 | Attribute | Value | 403 +----------------------+----------------------------+ 404 | Address Block | 192.0.2.0/24 | 405 | Name | Documentation (TEST-NET-1) | 406 | RFC | [RFC5737] | 407 | Allocation Date | January 2010 | 408 | Termination Date | N/A | 409 | Source | False | 410 | Destination | False | 411 | Forwardable | False | 412 | Globally Reachable | False | 413 | Reserved-by-Protocol | False | 414 +----------------------+----------------------------+ 416 Table 12: TEST-NET-1 418 +----------------------+-----------------+ 419 | Attribute | Value | 420 +----------------------+-----------------+ 421 | Address Block | 192.31.196.0/24 | 422 | Name | AS112-v4 | 423 | RFC | [RFC7535] | 424 | Allocation Date | December 2014 | 425 | Termination Date | N/A | 426 | Source | True | 427 | Destination | True | 428 | Forwardable | True | 429 | Globally Reachable | True | 430 | Reserved-by-Protocol | False | 431 +----------------------+-----------------+ 433 Table 13: AS112 - IPv4 435 +----------------------+-----------------+ 436 | Attribute | Value | 437 +----------------------+-----------------+ 438 | Address Block | 192.52.193.0/24 | 439 | Name | AMT | 440 | RFC | [RFC7450] | 441 | Allocation Date | December 2014 | 442 | Termination Date | N/A | 443 | Source | True | 444 | Destination | True | 445 | Forwardable | True | 446 | Globally Reachable | True | 447 | Reserved-by-Protocol | False | 448 +----------------------+-----------------+ 450 Table 14: Automatic Multicast Tunneling 452 +----------------------+-------------------------------+ 453 | Attribute | Value | 454 +----------------------+-------------------------------+ 455 | Address Block | 192.88.99.0/24 | 456 | Name | Deprecated 6to4 Relay Anycast | 457 | RFC | [RFC7526] | 458 | Allocation Date | June 2001 | 459 | Termination Date | March 2015 | 460 | Source | N/A | 461 | Destination | N/A | 462 | Forwardable | N/A | 463 | Globally Reachable | N/A | 464 | Reserved-by-Protocol | N/A | 465 +----------------------+-------------------------------+ 467 Table 15: 6to4 Relay Anycast - Deprecated 469 +----------------------+----------------+ 470 | Attribute | Value | 471 +----------------------+----------------+ 472 | Address Block | 192.168.0.0/16 | 473 | Name | Private-Use | 474 | RFC | [RFC1918] | 475 | Allocation Date | February 1996 | 476 | Termination Date | N/A | 477 | Source | True | 478 | Destination | True | 479 | Forwardable | True | 480 | Globally Reachable | False | 481 | Reserved-by-Protocol | False | 482 +----------------------+----------------+ 484 Table 16: Private-Use Networks 486 +----------------------+---------------------------------+ 487 | Attribute | Value | 488 +----------------------+---------------------------------+ 489 | Address Block | 192.175.48.0/24 | 490 | Name | Direct Delegation AS112 Service | 491 | RFC | [RFC7534] | 492 | Allocation Date | January 1996 | 493 | Termination Date | N/A | 494 | Source | True | 495 | Destination | True | 496 | Forwardable | True | 497 | Globally Reachable | True | 498 | Reserved-by-Protocol | False | 499 +----------------------+---------------------------------+ 501 Table 17: Direct Delegation AS112 Service 503 +----------------------+---------------+ 504 | Attribute | Value | 505 +----------------------+---------------+ 506 | Address Block | 198.18.0.0/15 | 507 | Name | Benchmarking | 508 | RFC | [RFC2544] | 509 | Allocation Date | March 1999 | 510 | Termination Date | N/A | 511 | Source | True | 512 | Destination | True | 513 | Forwardable | True | 514 | Globally Reachable | False | 515 | Reserved-by-Protocol | False | 516 +----------------------+---------------+ 518 Table 18: Network Interconnect Device Benchmark Testing 519 +----------------------+----------------------------+ 520 | Attribute | Value | 521 +----------------------+----------------------------+ 522 | Address Block | 198.51.100.0/24 | 523 | Name | Documentation (TEST-NET-2) | 524 | RFC | [RFC5737] | 525 | Allocation Date | January 2010 | 526 | Termination Date | N/A | 527 | Source | False | 528 | Destination | False | 529 | Forwardable | False | 530 | Globally Reachable | False | 531 | Reserved-by-Protocol | False | 532 +----------------------+----------------------------+ 534 Table 19: TEST-NET-2 536 +----------------------+----------------------------+ 537 | Attribute | Value | 538 +----------------------+----------------------------+ 539 | Address Block | 203.0.113.0/24 | 540 | Name | Documentation (TEST-NET-3) | 541 | RFC | [RFC5737] | 542 | Allocation Date | January 2010 | 543 | Termination Date | N/A | 544 | Source | False | 545 | Destination | False | 546 | Forwardable | False | 547 | Globally Reachable | False | 548 | Reserved-by-Protocol | False | 549 +----------------------+----------------------------+ 551 Table 20: TEST-NET-3 553 +----------------------+----------------------+ 554 | Attribute | Value | 555 +----------------------+----------------------+ 556 | Address Block | 240.0.0.0/4 | 557 | Name | Reserved | 558 | RFC | [RFC1112], Section 4 | 559 | Allocation Date | August 1989 | 560 | Termination Date | N/A | 561 | Source | False | 562 | Destination | False | 563 | Forwardable | False | 564 | Globally Reachable | False | 565 | Reserved-by-Protocol | True | 566 +----------------------+----------------------+ 568 Table 21: Reserved for Future Use 570 +----------------------+----------------------+ 571 | Attribute | Value | 572 +----------------------+----------------------+ 573 | Address Block | 255.255.255.255/32 | 574 | Name | Limited Broadcast | 575 | RFC | [RFC0919], Section 7 | 576 | Allocation Date | October 1984 | 577 | Termination Date | N/A | 578 | Source | False | 579 | Destination | True | 580 | Forwardable | False | 581 | Globally Reachable | False | 582 | Reserved-by-Protocol | True | 583 +----------------------+----------------------+ 585 Table 22: Limited Broadcast 587 3.2.3. IPv6 Special-Purpose Address Registry Entries 589 Table 23 through Table 41, below, represent entries with which the 590 IANA has initially populated the IPv6 Special-Purpose Address 591 Registry. 593 +----------------------+------------------+ 594 | Attribute | Value | 595 +----------------------+------------------+ 596 | Address Block | ::1/128 | 597 | Name | Loopback Address | 598 | RFC | [RFC4291] | 599 | Allocation Date | February 2006 | 600 | Termination Date | N/A | 601 | Source | False | 602 | Destination | False | 603 | Forwardable | False | 604 | Globally Reachable | False | 605 | Reserved-by-Protocol | True | 606 +----------------------+------------------+ 608 Table 23: Loopback Address 610 +----------------------+---------------------+ 611 | Attribute | Value | 612 +----------------------+---------------------+ 613 | Address Block | ::/128 | 614 | Name | Unspecified Address | 615 | RFC | [RFC4291] | 616 | Allocation Date | February 2006 | 617 | Termination Date | N/A | 618 | Source | True | 619 | Destination | False | 620 | Forwardable | False | 621 | Globally Reachable | False | 622 | Reserved-by-Protocol | True | 623 +----------------------+---------------------+ 625 Table 24: Unspecified Address 627 +----------------------+---------------------+ 628 | Attribute | Value | 629 +----------------------+---------------------+ 630 | Address Block | ::ffff:0:0/96 | 631 | Name | IPv4-mapped Address | 632 | RFC | [RFC4291] | 633 | Allocation Date | February 2006 | 634 | Termination Date | N/A | 635 | Source | False | 636 | Destination | False | 637 | Forwardable | False | 638 | Globally Reachable | False | 639 | Reserved-by-Protocol | True | 640 +----------------------+---------------------+ 642 Table 25: IPv4-Mapped Address 644 +----------------------+---------------------+ 645 | Attribute | Value | 646 +----------------------+---------------------+ 647 | Address Block | 64:ff9b::/96 | 648 | Name | IPv4-IPv6 Translat. | 649 | RFC | [RFC6052] | 650 | Allocation Date | October 2010 | 651 | Termination Date | N/A | 652 | Source | True | 653 | Destination | True | 654 | Forwardable | True | 655 | Globally Reachable | True | 656 | Reserved-by-Protocol | False | 657 +----------------------+---------------------+ 659 Table 26: IPv4-IPv6 Translation Address 661 +----------------------+----------------------------+ 662 | Attribute | Value | 663 +----------------------+----------------------------+ 664 | Address Block | 100::/64 | 665 | Name | Discard-Only Address Block | 666 | RFC | [RFC6666] | 667 | Allocation Date | June 2012 | 668 | Termination Date | N/A | 669 | Source | True | 670 | Destination | True | 671 | Forwardable | True | 672 | Globally Reachable | False | 673 | Reserved-by-Protocol | False | 674 +----------------------+----------------------------+ 676 Table 27: Discard-Only Prefix 678 +----------------------+---------------------------+ 679 | Attribute | Value | 680 +----------------------+---------------------------+ 681 | Address Block | 2001::/23 | 682 | Name | IETF Protocol Assignments | 683 | RFC | [RFC2928] | 684 | Allocation Date | September 2000 | 685 | Termination Date | N/A | 686 | Source | False[1] | 687 | Destination | False[1] | 688 | Forwardable | False[1] | 689 | Globally Reachable | False[1] | 690 | Reserved-by-Protocol | False | 691 +----------------------+---------------------------+ 693 Table 28: IETF Protocol Assignments 695 [1] Unless allowed by a more specific allocation. 697 +----------------------+--------------+ 698 | Attribute | Value | 699 +----------------------+--------------+ 700 | Address Block | 2001::/32 | 701 | Name | TEREDO | 702 | RFC | [RFC4380] | 703 | Allocation Date | January 2006 | 704 | Termination Date | N/A | 705 | Source | True | 706 | Destination | True | 707 | Forwardable | True | 708 | Globally Reachable | N/A [2] | 709 | Reserved-by-Protocol | False | 710 +----------------------+--------------+ 712 Table 29: TEREDO 714 [2] See [RFC4380] for details. 716 +----------------------+-------------------------------+ 717 | Attribute | Value | 718 +----------------------+-------------------------------+ 719 | Address Block | 2001:1::1/128 | 720 | Name | Port Control Protocol Anycast | 721 | RFC | [RFC7723] | 722 | Allocation Date | November 2015 | 723 | Termination Date | N/A | 724 | Source | True | 725 | Destination | True | 726 | Forwardable | True | 727 | Globally Reachable | True | 728 | Reserved-by-Protocol | False | 729 +----------------------+-------------------------------+ 731 Table 30: Port Control Protocol Anycast 732 +----------------------+--------------+ 733 | Attribute | Value | 734 +----------------------+--------------+ 735 | Address Block | 2001:2::/48 | 736 | Name | Benchmarking | 737 | RFC | [RFC5180] | 738 | Allocation Date | April 2008 | 739 | Termination Date | N/A | 740 | Source | True | 741 | Destination | True | 742 | Forwardable | True | 743 | Globally Reachable | False | 744 | Reserved-by-Protocol | False | 745 +----------------------+--------------+ 747 Table 31: Benchmarking 749 +----------------------+---------------+ 750 | Attribute | Value | 751 +----------------------+---------------+ 752 | Address Block | 2001:3::/32 | 753 | Name | AMT | 754 | RFC | [RFC7450] | 755 | Allocation Date | December 2014 | 756 | Termination Date | N/A | 757 | Source | True | 758 | Destination | True | 759 | Forwardable | True | 760 | Globally Reachable | True | 761 | Reserved-by-Protocol | False | 762 +----------------------+---------------+ 764 Table 32: Automatic Multicast Tunneling 766 +----------------------+-----------------+ 767 | Attribute | Value | 768 +----------------------+-----------------+ 769 | Address Block | 2001:4:112::/48 | 770 | Name | AS112-v6 | 771 | RFC | [RFC7535] | 772 | Allocation Date | December 2014 | 773 | Termination Date | N/A | 774 | Source | True | 775 | Destination | True | 776 | Forwardable | True | 777 | Globally Reachable | True | 778 | Reserved-by-Protocol | False | 779 +----------------------+-----------------+ 781 Table 33: AS112 - IPv6 783 +----------------------+------------------------------------------+ 784 | Attribute | Value | 785 +----------------------+------------------------------------------+ 786 | Address Block | 2001:5::/32 | 787 | Name | EID Space for LISP (Managed by RIPE NCC) | 788 | RFC | [RFC7954] | 789 | Allocation Date | September 2016 | 790 | Termination Date | September 2019[3] | 791 | Source | True[4] | 792 | Destination | True | 793 | Forwardable | True | 794 | Globally Reachable | True | 795 | Reserved-by-Protocol | True[5] | 796 +----------------------+------------------------------------------+ 798 Table 34: EID Space - LISP 800 [3] According to the 3+3 Plan outlined in [RFC7954], the termination 801 date can be postponed to September 2022. 803 [4] Can be used as a multicast source as well. 805 [5] To be used as EID space by routers enabled by LISP [RFC6830]. 807 +----------------------+--------------------------------+ 808 | Attribute | Value | 809 +----------------------+--------------------------------+ 810 | Address Block | 2001:10::/28 | 811 | Name | Deprecated (previously ORCHID) | 812 | RFC | [RFC4843] | 813 | Allocation Date | March 2007 | 814 | Termination Date | March 2014 | 815 | Source | | 816 | Destination | | 817 | Forwardable | | 818 | Globally Reachable | | 819 | Reserved-by-Protocol | | 820 +----------------------+--------------------------------+ 822 Table 35: ORCHIDv1 - Deprecated 824 +----------------------+--------------+ 825 | Attribute | Value | 826 +----------------------+--------------+ 827 | Address Block | 2001:20::/28 | 828 | Name | ORCHIDv2 | 829 | RFC | [RFC7343] | 830 | Allocation Date | July 2014 | 831 | Termination Date | N/A | 832 | Source | True | 833 | Destination | True | 834 | Forwardable | True | 835 | Globally Reachable | True | 836 | Reserved-by-Protocol | False | 837 +----------------------+--------------+ 839 Table 36: ORCHIDv2 841 +----------------------+---------------+ 842 | Attribute | Value | 843 +----------------------+---------------+ 844 | Address Block | 2001:db8::/32 | 845 | Name | Documentation | 846 | RFC | [RFC3849] | 847 | Allocation Date | July 2004 | 848 | Termination Date | N/A | 849 | Source | False | 850 | Destination | False | 851 | Forwardable | False | 852 | Globally Reachable | False | 853 | Reserved-by-Protocol | False | 854 +----------------------+---------------+ 856 Table 37: Documentation 858 +----------------------+---------------+ 859 | Attribute | Value | 860 +----------------------+---------------+ 861 | Address Block | 2002::/16 [6] | 862 | Name | 6to4 | 863 | RFC | [RFC3056] | 864 | Allocation Date | February 2001 | 865 | Termination Date | N/A | 866 | Source | True | 867 | Destination | True | 868 | Forwardable | True | 869 | Globally Reachable | N/A [6] | 870 | Reserved-by-Protocol | False | 871 +----------------------+---------------+ 873 Table 38: 6to4 875 [6] See [RFC3056] for details. 877 +----------------------+---------------------------------+ 878 | Attribute | Value | 879 +----------------------+---------------------------------+ 880 | Address Block | 2620:4f:8000::/48 | 881 | Name | Direct Delegation AS112 Service | 882 | RFC | [RFC7534] | 883 | Allocation Date | May 2011 | 884 | Termination Date | N/A | 885 | Source | True | 886 | Destination | True | 887 | Forwardable | True | 888 | Globally Reachable | True | 889 | Reserved-by-Protocol | False | 890 +----------------------+---------------------------------+ 892 Table 39: Direct Delegation AS112 Service 894 +----------------------+--------------+ 895 | Attribute | Value | 896 +----------------------+--------------+ 897 | Address Block | fc00::/7 | 898 | Name | Unique-Local | 899 | RFC | [RFC4193] | 900 | Allocation Date | October 2005 | 901 | Termination Date | N/A | 902 | Source | True | 903 | Destination | True | 904 | Forwardable | True | 905 | Globally Reachable | False [7] | 906 | Reserved-by-Protocol | False | 907 +----------------------+--------------+ 909 Table 40: Unique-Local (Private) 911 [7] See [RFC4193] for more details on the routability of Unique-Local 912 addresses. The Unique-Local prefix is drawn from the IPv6 Global 913 Unicast Address range, but is specified as not globally routed. 915 +----------------------+-----------------------+ 916 | Attribute | Value | 917 +----------------------+-----------------------+ 918 | Address Block | fe80::/10 | 919 | Name | Linked-Scoped Unicast | 920 | RFC | [RFC4291] | 921 | Allocation Date | February 2006 | 922 | Termination Date | N/A | 923 | Source | True | 924 | Destination | True | 925 | Forwardable | False | 926 | Globally Reachable | False | 927 | Reserved-by-Protocol | True | 928 +----------------------+-----------------------+ 930 Table 41: Link-Scoped Unicast 932 4. Security Considerations 934 Security of the Internet's routing system relies on the ability to 935 authenticate an assertion of unique control of an address block. 936 Measures to authenticate such assertions rely on validation that the 937 address block forms part of an existing allocated address block and 938 that there is a trustable and unique reference in the IANA address 939 registries. 941 The proposed registry is intended to provide an authoritative source 942 of information regarding the currency and intended purpose of special 943 purpose address blocks that are designated from the IANA-administered 944 Special-Purpose registry. This is a small step towards the creation 945 of a comprehensive registry framework that can be used as a trust 946 point for commencing a chain of address validation. Consideration 947 should be given to IANA registry publication formats that are machine 948 parsable. Additionally, consideration should be given to the use of 949 file signatures and associated certificate mechanisms to allow 950 applications to confirm that the registry contents are current and 951 that they have been published by the IANA. 953 5. Acknowledgements 955 Brian Carpenter and C.M. Heard provided useful comments on initial 956 versions of this document. Daniel Migualt provided an in-depth 957 review that helped strengthen the text within the document. 959 6. References 961 6.1. Normative References 963 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 964 Requirement Levels", BCP 14, RFC 2119, 965 DOI 10.17487/RFC2119, March 1997, 966 . 968 6.2. Informative References 970 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 971 RFC 919, DOI 10.17487/RFC0919, October 1984, 972 . 974 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 975 RFC 1112, DOI 10.17487/RFC1112, August 1989, 976 . 978 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 979 Communication Layers", STD 3, RFC 1122, 980 DOI 10.17487/RFC1122, October 1989, 981 . 983 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 984 and E. Lear, "Address Allocation for Private Internets", 985 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 986 . 988 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 989 Network Interconnect Devices", RFC 2544, 990 DOI 10.17487/RFC2544, March 1999, 991 . 993 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 994 Understanding Concerning the Technical Work of the 995 Internet Assigned Numbers Authority", RFC 2860, 996 DOI 10.17487/RFC2860, June 2000, 997 . 999 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 1000 IPv6 Sub-TLA ID Assignments", RFC 2928, 1001 DOI 10.17487/RFC2928, September 2000, 1002 . 1004 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 1005 via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February 1006 2001, . 1008 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 1009 Reserved for Documentation", RFC 3849, 1010 DOI 10.17487/RFC3849, July 2004, 1011 . 1013 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 1014 Configuration of IPv4 Link-Local Addresses", RFC 3927, 1015 DOI 10.17487/RFC3927, May 2005, 1016 . 1018 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 1019 Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, 1020 . 1022 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 1023 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 1024 2006, . 1026 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 1027 Label Switched (MPLS) Data Plane Failures", RFC 4379, 1028 DOI 10.17487/RFC4379, February 2006, 1029 . 1031 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 1032 Network Address Translations (NATs)", RFC 4380, 1033 DOI 10.17487/RFC4380, February 2006, 1034 . 1036 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 1037 for Overlay Routable Cryptographic Hash Identifiers 1038 (ORCHID)", RFC 4843, DOI 10.17487/RFC4843, April 2007, 1039 . 1041 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 1042 Dugatkin, "IPv6 Benchmarking Methodology for Network 1043 Interconnect Devices", RFC 5180, DOI 10.17487/RFC5180, May 1044 2008, . 1046 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1047 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1048 DOI 10.17487/RFC5226, May 2008, 1049 . 1051 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 1052 Reserved for Documentation", RFC 5737, 1053 DOI 10.17487/RFC5737, January 2010, 1054 . 1056 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1057 "Bidirectional Forwarding Detection (BFD) for MPLS Label 1058 Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, 1059 June 2010, . 1061 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 1062 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 1063 DOI 10.17487/RFC6052, October 2010, 1064 . 1066 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 1067 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 1068 Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April 1069 2012, . 1071 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 1072 RFC 6666, DOI 10.17487/RFC6666, August 2012, 1073 . 1075 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 1076 Locator/ID Separation Protocol (LISP)", RFC 6830, 1077 DOI 10.17487/RFC6830, January 2013, 1078 . 1080 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 1081 "Special-Purpose IP Address Registries", BCP 153, 1082 RFC 6890, DOI 10.17487/RFC6890, April 2013, 1083 . 1085 [RFC7050] Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 1086 the IPv6 Prefix Used for IPv6 Address Synthesis", 1087 RFC 7050, DOI 10.17487/RFC7050, November 2013, 1088 . 1090 [RFC7335] Byrne, C., "IPv4 Service Continuity Prefix", RFC 7335, 1091 DOI 10.17487/RFC7335, August 2014, 1092 . 1094 [RFC7343] Laganier, J. and F. Dupont, "An IPv6 Prefix for Overlay 1095 Routable Cryptographic Hash Identifiers Version 2 1096 (ORCHIDv2)", RFC 7343, DOI 10.17487/RFC7343, September 1097 2014, . 1099 [RFC7450] Bumgardner, G., "Automatic Multicast Tunneling", RFC 7450, 1100 DOI 10.17487/RFC7450, February 2015, 1101 . 1103 [RFC7526] Troan, O. and B. Carpenter, Ed., "Deprecating the Anycast 1104 Prefix for 6to4 Relay Routers", BCP 196, RFC 7526, 1105 DOI 10.17487/RFC7526, May 2015, 1106 . 1108 [RFC7534] Abley, J. and W. Sotomayor, "AS112 Nameserver Operations", 1109 RFC 7534, DOI 10.17487/RFC7534, May 2015, 1110 . 1112 [RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson, 1113 "AS112 Redirection Using DNAME", RFC 7535, 1114 DOI 10.17487/RFC7535, May 2015, 1115 . 1117 [RFC7600] Despres, R., Jiang, S., Ed., Penno, R., Lee, Y., Chen, G., 1118 and M. Chen, "IPv4 Residual Deployment via IPv6 - A 1119 Stateless Solution (4rd)", RFC 7600, DOI 10.17487/RFC7600, 1120 July 2015, . 1122 [RFC7723] Kiesel, S. and R. Penno, "Port Control Protocol (PCP) 1123 Anycast Addresses", RFC 7723, DOI 10.17487/RFC7723, 1124 January 2016, . 1126 [RFC7954] Iannone, L., Lewis, D., Meyer, D., and V. Fuller, 1127 "Locator/ID Separation Protocol (LISP) Endpoint Identifier 1128 (EID) Block", RFC 7954, DOI 10.17487/RFC7954, September 1129 2016, . 1131 Authors' Addresses 1133 Ronald Bonica 1134 Juniper Networks 1136 Email: rbonica@juniper.net 1138 Michelle Cotton 1139 ICANN 1141 Email: michelle.cotton@icann.org 1143 Brian Haberman 1144 Johns Hopkins University 1146 Email: brian@innovationslab.net 1147 Leo Vegoda 1148 ICANN 1150 Email: leo.vegoda@icann.org