idnits 2.17.1 draft-bchv-rfc6890bis-01.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 9 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 4 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 141: '... Review [RFC5226]. The "IANA Considerations" section MUST include all...' == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 22, 2016) is 2802 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 582 -- Looks like a reference, but probably isn't: '2' on line 657 -- Looks like a reference, but probably isn't: '3' on line 671 -- Looks like a reference, but probably isn't: '4' on line 690 -- 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: 1 error (**), 0 flaws (~~), 5 warnings (==), 8 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: RFC 6890 (if approved) M. Cotton 5 Intended status: Best Current Practice ICANN 6 Expires: February 23, 2017 B. Haberman 7 Johns Hopkins University 8 L. Vegoda 9 ICANN 10 August 22, 2016 12 Special-Purpose IP Address Registries 13 draft-bchv-rfc6890bis-01 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 February 23, 2017. 41 Copyright Notice 43 Copyright (c) 2016 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Assignment of an IPv4 Address Block to IANA . . . . . . . 3 61 2.2. Restructuring of the IPv4 and IPv6 Special-Purpose 62 Address Registries . . . . . . . . . . . . . . . . . . . 3 63 2.2.1. Information Requirements . . . . . . . . . . . . . . 4 64 2.2.2. IPv4 Special-Purpose Address Registry Entries . . . . 5 65 2.2.3. IPv6 Special-Purpose Address Registry Entries . . . . 12 66 3. Security Considerations . . . . . . . . . . . . . . . . . . . 19 67 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 68 5. Informative References . . . . . . . . . . . . . . . . . . . 19 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 71 1. Introduction 73 In order to support new protocols and practices, the IETF 74 occasionally reserves an address block for a special purpose. For 75 example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to 76 represent the local (i.e., "this") network. Likewise, [RFC4291] 77 reserves an IPv6 address block (fe80::/10) to represent link-scoped 78 unicast addresses. 80 The current list of all special-purpose address blocks are described 81 in [RFC6890]. However, several issues have been raised with how 82 "global" is defined in that document. Specifically, the definition 83 of global provided in [RFC6890] focuses on the prefix's ability to be 84 routed globally within the Internet and does not indicate if the 85 prefix is globally scoped (i.e., may be routed beyond the local link; 86 described as "global unicast" in the IPv6 addressing architecture 87 [RFC4291]). 89 This memo reiterates the assignments made to the IPv4 and IPv6 90 Special-Purpose Address Registries and augments the fields contained 91 within the registires in order to address the confusion raised by the 92 definition of "global". Furthermore, this memo defines: 94 o a common set of information that the registries will maintain 95 regarding each special-purpose address block 97 o a common set of requirements for future entries 99 This memo obsoletes [RFC6890]. 101 2. IANA Considerations 103 2.1. Assignment of an IPv4 Address Block to IANA 105 Table 7 of this document records the assignment of an IPv4 address 106 block (192.0.0.0/24) to IANA for IETF protocol assignments. This 107 address allocation to IANA is intended to support IETF protocol 108 assignments. A more general view of the roles of IANA with respect 109 to address allocation functions is documented in Sections 4.1 and 4.3 110 [RFC2860]. 112 IANA has designated special-purpose address blocks in compliance with 113 [RFC2860]. 115 2.2. Restructuring of the IPv4 and IPv6 Special-Purpose Address 116 Registries 118 IANA has restructured the following registries: 120 IPv4 Special-Purpose Address Registry 122 IPv6 Special-Purpose Address Registry 124 The IPv4 Special-Purpose Address Registry records all IPv4 special- 125 purpose address blocks. These reservations include, but are not 126 limited to, allocations from the 192.0.0.0/24 address block. 127 Likewise, the IPv6 Special-Purpose Address Registry records all IPv6 128 special-purpose address blocks. These reservations include, but are 129 not limited to, allocations from the 2001:0000::/23 address block, 130 which is a globally scoped address block. 132 Section 2.2.1 of this document describes information that both 133 registries will maintain for each entry. IANA has populated the IPv4 134 Special-Purpose Address Registry with information taken from 135 Section 2.2.2 of this document. Likewise, IANA has populated the 136 IPv6 Special-Purpose Address Registry with information taken from 137 Section 2.2.3 of this document. 139 IANA will update the aforementioned registries as requested in the 140 "IANA Considerations" section of a document that has passed IETF 141 Review [RFC5226]. The "IANA Considerations" section MUST include all 142 of the information specified in Section 2.2.1 of this document. 144 2.2.1. Information Requirements 146 The IPv4 and IPv6 Special-Purpose Address Registries maintain the 147 following information regarding each entry: 149 Address Block - A block of IPv4 or IPv6 addresses that has been 150 registered for a special purpose. 152 Name - A descriptive name for the special-purpose address block. 154 RFC - The RFC through which the special-purpose address block was 155 requested. 157 Allocation Date - The date upon which the special-purpose address 158 block was allocated. 160 Termination Date - The date upon which the allocation is to be 161 terminated. This field is applicable for limited-use allocations 162 only. 164 Source - A boolean value indicating whether an address from the 165 allocated special-purpose address block is valid when used as the 166 source address of an IP datagram that transits two devices. 168 Destination - A boolean value indicating whether an address from 169 the allocated special-purpose address block is valid when used as 170 the destination address of an IP datagram that transits two 171 devices. 173 Forwardable - A boolean value indicating whether a router may 174 forward an IP datagram whose destination address is drawn from the 175 allocated special-purpose address block between external 176 interfaces. 178 Globally Reachable - A boolean value indicating whether an IP 179 datagram whose destination address is drawn from the allocated 180 special-purpose address block is forwardable beyond a specified 181 administrative domain. 183 Reserved-by-Protocol - A boolean value indicating whether the 184 special-purpose address block is reserved by IP, itself. This 185 value is "TRUE" if the RFC that created the special-purpose 186 address block requires all compliant IP implementations to behave 187 in a special way when processing packets either to or from 188 addresses contained by the address block. 190 If the value of "Destination" is FALSE, the values of "Forwardable" 191 and "Globally Reachable" must also be false. 193 2.2.2. IPv4 Special-Purpose Address Registry Entries 195 Table 1 though Table 16, below, represent entries with which IANA has 196 initially populated the IPv4 Special-Purpose Address Registry. 198 +----------------------+-----------------------------+ 199 | Attribute | Value | 200 +----------------------+-----------------------------+ 201 | Address Block | 0.0.0.0/8 | 202 | Name | "This host on this network" | 203 | RFC | [RFC1122], Section 3.2.1.3 | 204 | Allocation Date | September 1981 | 205 | Termination Date | N/A | 206 | Source | True | 207 | Destination | False | 208 | Forwardable | False | 209 | Globally Reachable | False | 210 | Reserved-by-Protocol | True | 211 +----------------------+-----------------------------+ 213 Table 1: This host on this network 215 +----------------------+---------------+ 216 | Attribute | Value | 217 +----------------------+---------------+ 218 | Address Block | 10.0.0.0/8 | 219 | Name | Private-Use | 220 | RFC | [RFC1918] | 221 | Allocation Date | February 1996 | 222 | Termination Date | N/A | 223 | Source | True | 224 | Destination | True | 225 | Forwardable | True | 226 | Globally Reachable | False | 227 | Reserved-by-Protocol | False | 228 +----------------------+---------------+ 230 Table 2: Private-Use Networks 232 +----------------------+----------------------+ 233 | Attribute | Value | 234 +----------------------+----------------------+ 235 | Address Block | 100.64.0.0/10 | 236 | Name | Shared Address Space | 237 | RFC | [RFC6598] | 238 | Allocation Date | April 2012 | 239 | Termination Date | N/A | 240 | Source | True | 241 | Destination | True | 242 | Forwardable | True | 243 | Globally Reachable | False | 244 | Reserved-by-Protocol | False | 245 +----------------------+----------------------+ 247 Table 3: Shared Address Space 249 +----------------------+----------------------------+ 250 | Attribute | Value | 251 +----------------------+----------------------------+ 252 | Address Block | 127.0.0.0/8 | 253 | Name | Loopback | 254 | RFC | [RFC1122], Section 3.2.1.3 | 255 | Allocation Date | September 1981 | 256 | Termination Date | N/A | 257 | Source | False [1] | 258 | Destination | False [1] | 259 | Forwardable | False [1] | 260 | Globally Reachable | False [1] | 261 | Reserved-by-Protocol | True | 262 +----------------------+----------------------------+ 264 Table 4: Loopback 266 [1] Several protocols have been granted exceptions to this rule. For 267 examples, see [RFC4379] and [RFC5884]. 269 +----------------------+----------------+ 270 | Attribute | Value | 271 +----------------------+----------------+ 272 | Address Block | 169.254.0.0/16 | 273 | Name | Link Local | 274 | RFC | [RFC3927] | 275 | Allocation Date | May 2005 | 276 | Termination Date | N/A | 277 | Source | True | 278 | Destination | True | 279 | Forwardable | False | 280 | Globally Reachable | False | 281 | Reserved-by-Protocol | True | 282 +----------------------+----------------+ 284 Table 5: Link Local 286 +----------------------+---------------+ 287 | Attribute | Value | 288 +----------------------+---------------+ 289 | Address Block | 172.16.0.0/12 | 290 | Name | Private-Use | 291 | RFC | [RFC1918] | 292 | Allocation Date | February 1996 | 293 | Termination Date | N/A | 294 | Source | True | 295 | Destination | True | 296 | Forwardable | True | 297 | Globally Reachable | False | 298 | Reserved-by-Protocol | False | 299 +----------------------+---------------+ 301 Table 6: Private-Use Networks 303 +----------------------+------------------------------+ 304 | Attribute | Value | 305 +----------------------+------------------------------+ 306 | Address Block | 192.0.0.0/24 [2] | 307 | Name | IETF Protocol Assignments | 308 | RFC | Section 2.1 of this document | 309 | Allocation Date | January 2010 | 310 | Termination Date | N/A | 311 | Source | False | 312 | Destination | False | 313 | Forwardable | False | 314 | Globally Reachable | False | 315 | Reserved-by-Protocol | False | 316 +----------------------+------------------------------+ 318 Table 7: IETF Protocol Assignments 320 [2] Not usable unless by virtue of a more specific reservation. 322 +----------------------+--------------+ 323 | Attribute | Value | 324 +----------------------+--------------+ 325 | Address Block | 192.0.0.0/29 | 326 | Name | DS-Lite | 327 | RFC | [RFC6333] | 328 | Allocation Date | June 2011 | 329 | Termination Date | N/A | 330 | Source | True | 331 | Destination | True | 332 | Forwardable | True | 333 | Globally Reachable | False | 334 | Reserved-by-Protocol | False | 335 +----------------------+--------------+ 337 Table 8: DS-Lite 339 +----------------------+----------------------------+ 340 | Attribute | Value | 341 +----------------------+----------------------------+ 342 | Address Block | 192.0.2.0/24 | 343 | Name | Documentation (TEST-NET-1) | 344 | RFC | [RFC5737] | 345 | Allocation Date | January 2010 | 346 | Termination Date | N/A | 347 | Source | False | 348 | Destination | False | 349 | Forwardable | False | 350 | Globally Reachable | False | 351 | Reserved-by-Protocol | False | 352 +----------------------+----------------------------+ 354 Table 9: TEST-NET-1 356 +----------------------+-------------------------------+ 357 | Attribute | Value | 358 +----------------------+-------------------------------+ 359 | Address Block | 192.88.99.0/24 | 360 | Name | Deprecated 6to4 Relay Anycast | 361 | RFC | [RFC7526] | 362 | Allocation Date | June 2001 | 363 | Termination Date | March 2015 | 364 | Source | N/A | 365 | Destination | N/A | 366 | Forwardable | N/A | 367 | Globally Reachable | N/A | 368 | Reserved-by-Protocol | N/A | 369 +----------------------+-------------------------------+ 371 Table 10: 6to4 Relay Anycast 373 +----------------------+----------------+ 374 | Attribute | Value | 375 +----------------------+----------------+ 376 | Address Block | 192.168.0.0/16 | 377 | Name | Private-Use | 378 | RFC | [RFC1918] | 379 | Allocation Date | February 1996 | 380 | Termination Date | N/A | 381 | Source | True | 382 | Destination | True | 383 | Forwardable | True | 384 | Globally Reachable | False | 385 | Reserved-by-Protocol | False | 386 +----------------------+----------------+ 388 Table 11: Private-Use Networks 390 +----------------------+---------------+ 391 | Attribute | Value | 392 +----------------------+---------------+ 393 | Address Block | 198.18.0.0/15 | 394 | Name | Benchmarking | 395 | RFC | [RFC2544] | 396 | Allocation Date | March 1999 | 397 | Termination Date | N/A | 398 | Source | True | 399 | Destination | True | 400 | Forwardable | True | 401 | Globally Reachable | False | 402 | Reserved-by-Protocol | False | 403 +----------------------+---------------+ 405 Table 12: Network Interconnect Device Benchmark Testing 406 +----------------------+----------------------------+ 407 | Attribute | Value | 408 +----------------------+----------------------------+ 409 | Address Block | 198.51.100.0/24 | 410 | Name | Documentation (TEST-NET-2) | 411 | RFC | [RFC5737] | 412 | Allocation Date | January 2010 | 413 | Termination Date | N/A | 414 | Source | False | 415 | Destination | False | 416 | Forwardable | False | 417 | Globally Reachable | False | 418 | Reserved-by-Protocol | False | 419 +----------------------+----------------------------+ 421 Table 13: TEST-NET-2 423 +----------------------+----------------------------+ 424 | Attribute | Value | 425 +----------------------+----------------------------+ 426 | Address Block | 203.0.113.0/24 | 427 | Name | Documentation (TEST-NET-3) | 428 | RFC | [RFC5737] | 429 | Allocation Date | January 2010 | 430 | Termination Date | N/A | 431 | Source | False | 432 | Destination | False | 433 | Forwardable | False | 434 | Globally Reachable | False | 435 | Reserved-by-Protocol | False | 436 +----------------------+----------------------------+ 438 Table 14: TEST-NET-3 440 +----------------------+----------------------+ 441 | Attribute | Value | 442 +----------------------+----------------------+ 443 | Address Block | 240.0.0.0/4 | 444 | Name | Reserved | 445 | RFC | [RFC1112], Section 4 | 446 | Allocation Date | August 1989 | 447 | Termination Date | N/A | 448 | Source | False | 449 | Destination | False | 450 | Forwardable | False | 451 | Globally Reachable | False | 452 | Reserved-by-Protocol | True | 453 +----------------------+----------------------+ 455 Table 15: Reserved for Future Use 457 +----------------------+----------------------+ 458 | Attribute | Value | 459 +----------------------+----------------------+ 460 | Address Block | 255.255.255.255/32 | 461 | Name | Limited Broadcast | 462 | RFC | [RFC0919], Section 7 | 463 | Allocation Date | October 1984 | 464 | Termination Date | N/A | 465 | Source | False | 466 | Destination | True | 467 | Forwardable | False | 468 | Globally Reachable | False | 469 | Reserved-by-Protocol | False | 470 +----------------------+----------------------+ 472 Table 16: Limited Broadcast 474 2.2.3. IPv6 Special-Purpose Address Registry Entries 476 Table 17 through Table 29, below, represent entries with which the 477 IANA has initially populated the IPv6 Special-Purpose Address 478 Registry. 480 +----------------------+------------------+ 481 | Attribute | Value | 482 +----------------------+------------------+ 483 | Address Block | ::1/128 | 484 | Name | Loopback Address | 485 | RFC | [RFC4291] | 486 | Allocation Date | February 2006 | 487 | Termination Date | N/A | 488 | Source | False | 489 | Destination | False | 490 | Forwardable | False | 491 | Globally Reachable | False | 492 | Reserved-by-Protocol | True | 493 +----------------------+------------------+ 495 Table 17: Loopback Address 497 +----------------------+---------------------+ 498 | Attribute | Value | 499 +----------------------+---------------------+ 500 | Address Block | ::/128 | 501 | Name | Unspecified Address | 502 | RFC | [RFC4291] | 503 | Allocation Date | February 2006 | 504 | Termination Date | N/A | 505 | Source | True | 506 | Destination | False | 507 | Forwardable | False | 508 | Globally Reachable | False | 509 | Reserved-by-Protocol | True | 510 +----------------------+---------------------+ 512 Table 18: Unspecified Address 514 +----------------------+---------------------+ 515 | Attribute | Value | 516 +----------------------+---------------------+ 517 | Address Block | 64:ff9b::/96 | 518 | Name | IPv4-IPv6 Translat. | 519 | RFC | [RFC6052] | 520 | Allocation Date | October 2010 | 521 | Termination Date | N/A | 522 | Source | True | 523 | Destination | True | 524 | Forwardable | True | 525 | Globally Reachable | True | 526 | Reserved-by-Protocol | False | 527 +----------------------+---------------------+ 529 Table 19: IPv4-IPv6 Translation Address 531 +----------------------+---------------------+ 532 | Attribute | Value | 533 +----------------------+---------------------+ 534 | Address Block | ::ffff:0:0/96 | 535 | Name | IPv4-mapped Address | 536 | RFC | [RFC4291] | 537 | Allocation Date | February 2006 | 538 | Termination Date | N/A | 539 | Source | False | 540 | Destination | False | 541 | Forwardable | False | 542 | Globally Reachable | False | 543 | Reserved-by-Protocol | True | 544 +----------------------+---------------------+ 546 Table 20: IPv4-Mapped Address 548 +----------------------+----------------------------+ 549 | Attribute | Value | 550 +----------------------+----------------------------+ 551 | Address Block | 100::/64 | 552 | Name | Discard-Only Address Block | 553 | RFC | [RFC6666] | 554 | Allocation Date | June 2012 | 555 | Termination Date | N/A | 556 | Source | True | 557 | Destination | True | 558 | Forwardable | True | 559 | Globally Reachable | False | 560 | Reserved-by-Protocol | False | 561 +----------------------+----------------------------+ 563 Table 21: Discard-Only Prefix 565 +----------------------+---------------------------+ 566 | Attribute | Value | 567 +----------------------+---------------------------+ 568 | Address Block | 2001::/23 | 569 | Name | IETF Protocol Assignments | 570 | RFC | [RFC2928] | 571 | Allocation Date | September 2000 | 572 | Termination Date | N/A | 573 | Source | False[1] | 574 | Destination | False[1] | 575 | Forwardable | False[1] | 576 | Globally Reachable | False[1] | 577 | Reserved-by-Protocol | False | 578 +----------------------+---------------------------+ 580 Table 22: IETF Protocol Assignments 582 [1] Unless allowed by a more specific allocation. 584 +----------------------+--------------+ 585 | Attribute | Value | 586 +----------------------+--------------+ 587 | Address Block | 2001::/32 | 588 | Name | TEREDO | 589 | RFC | [RFC4380] | 590 | Allocation Date | January 2006 | 591 | Termination Date | N/A | 592 | Source | True | 593 | Destination | True | 594 | Forwardable | True | 595 | Globally Reachable | N/A [2] | 596 | Reserved-by-Protocol | False | 597 +----------------------+--------------+ 599 Table 23: TEREDO 601 [2] See [RFC4380] for details. 603 +----------------------+--------------+ 604 | Attribute | Value | 605 +----------------------+--------------+ 606 | Address Block | 2001:2::/48 | 607 | Name | Benchmarking | 608 | RFC | [RFC5180] | 609 | Allocation Date | April 2008 | 610 | Termination Date | N/A | 611 | Source | True | 612 | Destination | True | 613 | Forwardable | True | 614 | Globally Reachable | False | 615 | Reserved-by-Protocol | False | 616 +----------------------+--------------+ 618 Table 24: Benchmarking 620 +----------------------+---------------+ 621 | Attribute | Value | 622 +----------------------+---------------+ 623 | Address Block | 2001:db8::/32 | 624 | Name | Documentation | 625 | RFC | [RFC3849] | 626 | Allocation Date | July 2004 | 627 | Termination Date | N/A | 628 | Source | False | 629 | Destination | False | 630 | Forwardable | False | 631 | Globally Reachable | False | 632 | Reserved-by-Protocol | False | 633 +----------------------+---------------+ 635 Table 25: Documentation 637 +----------------------+--------------+ 638 | Attribute | Value | 639 +----------------------+--------------+ 640 | Address Block | 2001:10::/28 | 641 | Name | ORCHID | 642 | RFC | [RFC4843] | 643 | Allocation Date | March 2007 | 644 | Termination Date | March 2014 | 645 | Source | False | 646 | Destination | False | 647 | Forwardable | False | 648 | Globally Reachable | False | 649 | Reserved-by-Protocol | False | 650 +----------------------+--------------+ 652 Table 26: ORCHID 654 +----------------------+---------------+ 655 | Attribute | Value | 656 +----------------------+---------------+ 657 | Address Block | 2002::/16 [2] | 658 | Name | 6to4 | 659 | RFC | [RFC3056] | 660 | Allocation Date | February 2001 | 661 | Termination Date | N/A | 662 | Source | True | 663 | Destination | True | 664 | Forwardable | True | 665 | Globally Reachable | N/A [3] | 666 | Reserved-by-Protocol | False | 667 +----------------------+---------------+ 669 Table 27: 6to4 671 [3] See [RFC3056] for details. 673 +----------------------+--------------+ 674 | Attribute | Value | 675 +----------------------+--------------+ 676 | Address Block | fc00::/7 | 677 | Name | Unique-Local | 678 | RFC | [RFC4193] | 679 | Allocation Date | October 2005 | 680 | Termination Date | N/A | 681 | Source | True | 682 | Destination | True | 683 | Forwardable | True | 684 | Globally Reachable | False [4] | 685 | Reserved-by-Protocol | False | 686 +----------------------+--------------+ 688 Table 28: Unique-Local (Private) 690 [4] See [RFC4193] for more details on the routability of Unique-Local 691 addresses. The Unique-Local prefix is drawn from the IPv6 Global 692 Unicast Address range, but is specified as not globally routed. 694 +----------------------+-----------------------+ 695 | Attribute | Value | 696 +----------------------+-----------------------+ 697 | Address Block | fe80::/10 | 698 | Name | Linked-Scoped Unicast | 699 | RFC | [RFC4291] | 700 | Allocation Date | February 2006 | 701 | Termination Date | N/A | 702 | Source | True | 703 | Destination | True | 704 | Forwardable | False | 705 | Globally Reachable | False | 706 | Reserved-by-Protocol | True | 707 +----------------------+-----------------------+ 709 Table 29: Link-Scoped Unicast 711 3. Security Considerations 713 Security of the Internet's routing system relies on the ability to 714 authenticate an assertion of unique control of an address block. 715 Measures to authenticate such assertions rely on validation that the 716 address block forms part of an existing allocated address block and 717 that there is a trustable and unique reference in the IANA address 718 registries. 720 The proposed registry is intended to provide an authoritative source 721 of information regarding the currency and intended purpose of special 722 purpose address blocks that are designated from the IANA-administered 723 Special-Purpose registry. This is a small step towards the creation 724 of a comprehensive registry framework that can be used as a trust 725 point for commencing a chain of address validation. Consideration 726 should be given to IANA registry publication formats that are machine 727 parsable. Additionally, consideration should be given to the use of 728 file signatures and associated certificate mechanisms to allow 729 applications to confirm that the registry contents are current and 730 that they have been published by the IANA. 732 4. Acknowledgements 734 Brian Carpenter provided useful comments on the initial version of 735 this document. 737 5. Informative References 739 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 740 RFC 919, DOI 10.17487/RFC0919, October 1984, 741 . 743 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 744 RFC 1112, DOI 10.17487/RFC1112, August 1989, 745 . 747 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 748 Communication Layers", STD 3, RFC 1122, 749 DOI 10.17487/RFC1122, October 1989, 750 . 752 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 753 and E. Lear, "Address Allocation for Private Internets", 754 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 755 . 757 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 758 Network Interconnect Devices", RFC 2544, 759 DOI 10.17487/RFC2544, March 1999, 760 . 762 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 763 Understanding Concerning the Technical Work of the 764 Internet Assigned Numbers Authority", RFC 2860, 765 DOI 10.17487/RFC2860, June 2000, 766 . 768 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 769 IPv6 Sub-TLA ID Assignments", RFC 2928, 770 DOI 10.17487/RFC2928, September 2000, 771 . 773 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 774 via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February 775 2001, . 777 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 778 Reserved for Documentation", RFC 3849, 779 DOI 10.17487/RFC3849, July 2004, 780 . 782 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 783 Configuration of IPv4 Link-Local Addresses", RFC 3927, 784 DOI 10.17487/RFC3927, May 2005, 785 . 787 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 788 Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, 789 . 791 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 792 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 793 2006, . 795 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 796 Label Switched (MPLS) Data Plane Failures", RFC 4379, 797 DOI 10.17487/RFC4379, February 2006, 798 . 800 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 801 Network Address Translations (NATs)", RFC 4380, 802 DOI 10.17487/RFC4380, February 2006, 803 . 805 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 806 for Overlay Routable Cryptographic Hash Identifiers 807 (ORCHID)", RFC 4843, DOI 10.17487/RFC4843, April 2007, 808 . 810 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 811 Dugatkin, "IPv6 Benchmarking Methodology for Network 812 Interconnect Devices", RFC 5180, DOI 10.17487/RFC5180, May 813 2008, . 815 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 816 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 817 DOI 10.17487/RFC5226, May 2008, 818 . 820 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 821 Reserved for Documentation", RFC 5737, 822 DOI 10.17487/RFC5737, January 2010, 823 . 825 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 826 "Bidirectional Forwarding Detection (BFD) for MPLS Label 827 Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, 828 June 2010, . 830 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 831 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 832 DOI 10.17487/RFC6052, October 2010, 833 . 835 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 836 Stack Lite Broadband Deployments Following IPv4 837 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, 838 . 840 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 841 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 842 Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April 843 2012, . 845 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 846 RFC 6666, DOI 10.17487/RFC6666, August 2012, 847 . 849 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 850 "Special-Purpose IP Address Registries", BCP 153, 851 RFC 6890, DOI 10.17487/RFC6890, April 2013, 852 . 854 [RFC7526] Troan, O. and B. Carpenter, Ed., "Deprecating the Anycast 855 Prefix for 6to4 Relay Routers", BCP 196, RFC 7526, 856 DOI 10.17487/RFC7526, May 2015, 857 . 859 Authors' Addresses 861 Ronald Bonica 862 Juniper Networks 864 Email: rbonica@juniper.net 866 Michelle Cotton 867 ICANN 869 Email: michelle.cotton@icann.org 871 Brian Haberman 872 Johns Hopkins University 874 Email: brian@innovationslab.net 876 Leo Vegoda 877 ICANN 879 Email: leo.vegoda@icann.org