idnits 2.17.00 (12 Aug 2021) /tmp/idnits36782/draft-bonica-special-purpose-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 10 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 == There are 3 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. == There are 6 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- The draft header indicates that this document obsoletes RFC5156, but the abstract doesn't seem to directly say this. It does mention RFC5156 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4773, updated by this document, for RFC5378 checks: 2005-11-14) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 27, 2012) is 3523 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 312 -- Looks like a reference, but probably isn't: '2' on line 441 -- Looks like a reference, but probably isn't: '3' on line 561 -- Looks like a reference, but probably isn't: '4' on line 642 -- Looks like a reference, but probably isn't: '5' on line 691 ** Obsolete normative reference: RFC 4773 (Obsoleted by RFC 6890) ** Obsolete normative reference: RFC 5156 (Obsoleted by RFC 6890) ** Obsolete normative reference: RFC 5735 (Obsoleted by RFC 6890) ** Obsolete normative reference: RFC 5736 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 3068 (Obsoleted by RFC 7526) -- Obsolete informational reference (is this intentional?): RFC 4843 (Obsoleted by RFC 7343) Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Cotton 3 Internet-Draft L. Vegoda 4 Obsoletes: 5156, 5735 Internet Corporation for 5 (if approved) Assigned Names and Numbers 6 Updates: 4773,5736 (if approved) R. Bonica, Ed. 7 Intended status: BCP Juniper Networks 8 Expires: March 31, 2013 B. Haberman 9 Johns Hopkins University Applied 10 Physics Lab 11 September 27, 2012 13 Special-Purpose Address Registries 14 draft-bonica-special-purpose-01 16 Abstract 18 This memo instructs IANA to restructure its IPv4 and IPv6 Special- 19 Purpose Address Registries. Upon restructuring, the aforementioned 20 registries will record all special-purpose address blocks, 21 maintaining a common set of information regarding each address block. 23 This memo updates RFC 5736 and RFC 4773, which define the current 24 structure of the IPv4 and IPv6 Special-Purpose Address Registries. 25 It also obsoletes RFC 5735 and RFC 5156 which document special- 26 purpose address blocks that are not currently, but will in the 27 future, be recorded in the IPv4 and IPv6 Special-Purpose Address 28 Registries. 30 Status of this Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on March 31, 2013. 47 Copyright Notice 48 Copyright (c) 2012 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 65 2.1. Information Requirements . . . . . . . . . . . . . . . . . 4 66 2.2. IPv4 Special-Purpose Address Registry Entries . . . . . . 5 67 2.3. IPv6 Special-Purpose Address Registry Entries . . . . . . 11 68 3. Security Considerations . . . . . . . . . . . . . . . . . . . 16 69 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 70 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 71 5.1. Normative References . . . . . . . . . . . . . . . . . . . 17 72 5.2. Informative References . . . . . . . . . . . . . . . . . . 17 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 75 1. Introduction 77 In order to support new protocols and practices, the IETF 78 occasionally reserves an address block a for special purpose. For 79 example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to 80 represent the local (i.e., "this") network. Likewise, [RFC4291] 81 reserves an IPv6 address block (fe80::/10) to represent link-scoped 82 unicast addresses. 84 Periodically, the IETF publishes an RFC that catalogs special-purpose 85 address blocks. Currently, [RFC5735] catalogs all IPv4 special- 86 purpose address blocks and [RFC5156] catalogs all IPv6 special- 87 purpose address blocks. 89 [RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and 90 instructs IANA to allocate special-purpose address blocks from this 91 space. [RFC5736] also instructs IANA to create an IPv4 Special- 92 Purpose Address Registry that records allocations from this address 93 space. However, [RFC5736] does not instruct IANA to record special- 94 purpose address block reservations from outside of the aforementioned 95 space in the IPv4 Special-Purpose Address Registry. 97 Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to 98 IANA and instructs IANA to allocate special-purpose address blocks 99 from this space. [RFC4773] instructs IANA to create an IPv6 Special- 100 Purpose Address Registry that records allocations from this address 101 space. However, [RFC4773] does not instruct IANA to record special- 102 purpose address block reservations from outside of the aforementioned 103 space in the IPv6 Special-Purpose Address Registry. 105 This memo instructs IANA to restructure its IPv4 and IPv6 Special- 106 Purpose Address Registries. Therefore, this document updates 107 [RFC5736] and [RFC4773] which define the current structure of the 108 aforementioned registries. 110 Specifically, this memo instructs IANA to record all special-purpose 111 address blocks in the aforementioned registries. These include, but 112 are not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6 113 allocations from 2001:0000::/23. When the aforementioned registries 114 include all special-purpose address blocks, [RFC5735] and [RFC5156] 115 will become redundant with the registries. Therefore, this memo 116 obsoletes [RFC5735] and [RFC5156]. 118 Furthermore, this memo defines: 120 o a common set of information that the registries will maintain 121 regarding each special-purpose address block 123 o a common set of requirements for future entries 125 2. IANA Considerations 127 IANA will restructure the following registries: 129 o IPv4 Special-Purpose Address Registry 131 o IPv6 Special-Purpose Address Registry 133 The IPv4 Special-Purpose Address Registry will record all IPv4 134 special-purpose address blocks. These reservations will include, but 135 not be limited to, allocations from the 192.0.0.0/24 address block. 136 Likewise, the IPv6 Special-Purpose Address Registry will record all 137 IPv6 special-purpose address blocks. These reservations will 138 include, but not be limited to, allocations from the 2001:0000::/23 139 address block. 141 Section 2.1 of this document describes information that both 142 registries will maintain for each entry. Initially, IANA will 143 populate the IPv4 Special-Purpose Address Registry with information 144 taken from Section 2.2 of this document. Likewise, IANA will 145 populate the IPv6 Special-Purpose Address Registry with information 146 taken from Section 2.3 of this document. 148 IANA will update the aforementioned registries as requested in the 149 "IANA Considerations" section of an IESG-reviewed document. The " 150 IANA Considerations" section must include all of the information 151 specified in Section 2.1 of this document. 153 2.1. Information Requirements 155 The IPv4 and IPv6 Special-Purpose Address Registries will maintain 156 the following information regarding each entry: 158 o Prefix - An IPv4 or IPv6 prefix that identifies the special- 159 purpose address block 161 o Name - A descriptive name for the special-purpose address block 163 o RFC - The RFC though which the special-purpose address block was 164 requested 166 o Allocation Date - The date upon which the special purpose address 167 block was allocated 169 o Termination Date - The date upon which the allocation is to be 170 terminated. This field is applicable for limited-use allocations 171 only. 173 o Source - A boolean value indicated whether an address from the 174 allocated special-purpose address block is valid when used as the 175 source address of an IP datagram that transits two devices 177 o Destination - A boolean value indicated whether an address from 178 the allocated special-purpose address block is valid when used as 179 the destination address of an IP datagram that transits two 180 devices 182 o Routable - A boolean value indicating whether a IP datagram whose 183 destination address is drawn from the allocated special-purpose 184 address block is routable (i.e., may traverse more than a single 185 IP interface) 187 o Global - A boolean value indicating whether a IP datagram whose 188 destination address is drawn from the allocated special-purpose 189 address block is routable beyond a specified administrative 190 domain. 192 If the value of "Destination" is FALSE, the values of "Routable" and 193 "Global" must also be false. 195 2.2. IPv4 Special-Purpose Address Registry Entries 197 Table 1 though Table 17, below, represent entries with which the IANA 198 will initially populate the IPv4 Special-Purpose Address Registry. 200 +------------------+---------------------------+ 201 | Attribute | Value | 202 +------------------+---------------------------+ 203 | Prefix | 0.0.0.0/8 | 204 | Name | "This" Network | 205 | RFC | [RFC1122] Section 3.2.1.3 | 206 | Allocation Date | September, 1981 | 207 | Termination Date | N/A | 208 | Source | True | 209 | Destination | False | 210 | Routable | False | 211 | Global | False | 212 +------------------+---------------------------+ 214 Table 1: "This" Network 216 +------------------+---------------+ 217 | Attribute | Value | 218 +------------------+---------------+ 219 | Prefix | 10.0.0.0/8 | 220 | Name | Private-Use | 221 | RFC | [RFC1918] | 222 | Allocation Date | February 1996 | 223 | Termination Date | N/A | 224 | Source | True | 225 | Destination | True | 226 | Routable | True | 227 | Global | False | 228 +------------------+---------------+ 230 Table 2: Private-Use Networks 232 +------------------+----------------------+ 233 | Attribute | Value | 234 +------------------+----------------------+ 235 | Prefix | 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 | Routable | True | 243 | Global | False | 244 +------------------+----------------------+ 246 Table 3: Shared Address Space 248 +------------------+---------------------------+ 249 | Attribute | Value | 250 +------------------+---------------------------+ 251 | Prefix | 127.0.0.0/8 | 252 | Name | Loopback | 253 | RFC | [RFC1122] Section 3.2.1.3 | 254 | Allocation Date | September 1981 | 255 | Termination Date | N/A | 256 | Source | False | 257 | Destination | False | 258 | Routable | False | 259 | Global | False | 260 +------------------+---------------------------+ 262 Table 4: Loopback 264 +------------------+----------------+ 265 | Attribute | Value | 266 +------------------+----------------+ 267 | Prefix | 169.254.0.0/16 | 268 | Name | Link Local | 269 | RFC | [RFC3927] | 270 | Allocation Date | May 2005 | 271 | Termination Date | N/A | 272 | Source | True | 273 | Destination | True | 274 | Routable | False | 275 | Global | False | 276 +------------------+----------------+ 278 Table 5: Link Local 280 +------------------+---------------+ 281 | Attribute | Value | 282 +------------------+---------------+ 283 | Prefix | 172.16.0.0/12 | 284 | Name | Private-Use | 285 | RFC | [RFC1122] | 286 | Allocation Date | February 1996 | 287 | Termination Date | N/A | 288 | Source | True | 289 | Destination | True | 290 | Routable | True | 291 | Global | False | 292 +------------------+---------------+ 294 Table 6: Private-Use Networks 296 +------------------+---------------------------+ 297 | Attribute | Value | 298 +------------------+---------------------------+ 299 | Prefix | 192.0.0.0/24 [1] | 300 | Name | IETF Protocol Assignments | 301 | RFC | [RFC5736] | 302 | Allocation Date | January 2010 | 303 | Termination Date | N/A | 304 | Source | False | 305 | Destination | False | 306 | Routable | False | 307 | Global | False | 308 +------------------+---------------------------+ 310 Table 7: IETF Protocol Assignments 312 [1] Not useable unless by virtue of a more specific reservation. 314 +------------------+--------------+ 315 | Attribute | Value | 316 +------------------+--------------+ 317 | Prefix | 192.0.0.0/29 | 318 | Name | DS-Lite | 319 | RFC | [RFC6333] | 320 | Allocation Date | June 2011 | 321 | Termination Date | N/A | 322 | Source | True | 323 | Destination | True | 324 | Routable | True | 325 | Global | False | 326 +------------------+--------------+ 328 Table 8: DS-Lite 330 +------------------+----------------------------+ 331 | Attribute | Value | 332 +------------------+----------------------------+ 333 | Prefix | 192.0.2.0/24 | 334 | Name | Documentation (TEST-NET-1) | 335 | RFC | [RFC5737] | 336 | Allocation Date | January 2010 | 337 | Termination Date | N/A | 338 | Source | False | 339 | Destination | False | 340 | Routable | False | 341 | Global | False | 342 +------------------+----------------------------+ 344 Table 9: TEST-NET-1 346 +------------------+--------------------+ 347 | Attribute | Value | 348 +------------------+--------------------+ 349 | Prefix | 192.88.99.0/24 | 350 | Name | 6to4 Relay Anycast | 351 | RFC | [RFC3068] | 352 | Allocation Date | June 2001 | 353 | Termination Date | N/A | 354 | Source | True | 355 | Destination | True | 356 | Routable | True | 357 | Global | True | 358 +------------------+--------------------+ 360 Table 10: 6to4 Relay Anycast 362 +------------------+----------------+ 363 | Attribute | Value | 364 +------------------+----------------+ 365 | Prefix | 192.168.0.0/16 | 366 | Name | Private-Use | 367 | RFC | [RFC1918] | 368 | Allocation Date | February 196 | 369 | Termination Date | N/A | 370 | Source | True | 371 | Destination | True | 372 | Routable | True | 373 | Global | Flase | 374 +------------------+----------------+ 376 Table 11: Private-Use Networks 378 +------------------+---------------+ 379 | Attribute | Value | 380 +------------------+---------------+ 381 | Prefix | 198.18.0.0/15 | 382 | Name | Benchmarking | 383 | RFC | [RFC2544] | 384 | Allocation Date | March 1999 | 385 | Termination Date | N/A | 386 | Source | True | 387 | Destination | True | 388 | Routable | True | 389 | Global | False | 390 +------------------+---------------+ 392 Table 12: Network Interconnect Device Benchmark Testing 393 +------------------+----------------------------+ 394 | Attribute | Value | 395 +------------------+----------------------------+ 396 | Prefix | 198.51.100.0/24 | 397 | Name | Documentation (TEST-NET-2) | 398 | RFC | [RFC5737] | 399 | Allocation Date | January 2010 | 400 | Termination Date | N/A | 401 | Source | False | 402 | Destination | False | 403 | Routable | False | 404 | Global | False | 405 +------------------+----------------------------+ 407 Table 13: TEST-NET-2 409 +------------------+----------------------------+ 410 | Attribute | Value | 411 +------------------+----------------------------+ 412 | Prefix | 203.0.113.0/24 | 413 | Name | Documentation (TEST-NET-3) | 414 | RFC | [RFC5737] | 415 | Allocation Date | January 2010 | 416 | Termination Date | N/A | 417 | Source | False | 418 | Destination | False | 419 | Routable | False | 420 | Global | False | 421 +------------------+----------------------------+ 423 Table 14: TEST-NET-3 425 +------------------+-------------+ 426 | Attribute | Value | 427 +------------------+-------------+ 428 | Prefix | 224.0.0.0/4 | 429 | Name | Multicast | 430 | RFC | [RFC5771] | 431 | Allocation Date | March 2010 | 432 | Termination Date | N/A | 433 | Source | False | 434 | Destination | True | 435 | Routable | True | 436 | Global | N/A [2] | 437 +------------------+-------------+ 439 Table 15: Multicast 441 [2] See [RFC5771] for details. 443 +------------------+---------------------+ 444 | Attribute | Value | 445 +------------------+---------------------+ 446 | Prefix | 240.0.0.0/4 | 447 | Name | Reserved | 448 | RFC | [RFC1112] Section 4 | 449 | Allocation Date | August 1989 | 450 | Termination Date | N/A | 451 | Source | False | 452 | Destination | False | 453 | Routable | False | 454 | Global | False | 455 +------------------+---------------------+ 457 Table 16: Reserved for Future Use 459 +------------------+---------------------+ 460 | Attribute | Value | 461 +------------------+---------------------+ 462 | Prefix | 255.255.255.255/32 | 463 | Name | Limited Broadcast | 464 | RFC | [RFC0919] Section 7 | 465 | Allocation Date | October 1984 | 466 | Termination Date | N/A | 467 | Source | False | 468 | Destination | True | 469 | Routable | False | 470 | Global | False | 471 +------------------+---------------------+ 473 Table 17: Limited Broadcast 475 2.3. IPv6 Special-Purpose Address Registry Entries 477 Table 18 through Table 30, below, represent entries with which the 478 IANA will initially populate the IPv6 Special-Purpose Address 479 Registry. 481 +------------------+------------------+ 482 | Attribute | Value | 483 +------------------+------------------+ 484 | Prefix | ::1/128 | 485 | Name | Loopback Address | 486 | RFC | [RFC4291] | 487 | Allocation Date | February 2006 | 488 | Termination Date | N/A | 489 | Source | False | 490 | Destination | False | 491 | Routable | False | 492 | Global | False | 493 +------------------+------------------+ 495 Table 18: Loopback Address 497 +------------------+---------------------+ 498 | Attribute | Value | 499 +------------------+---------------------+ 500 | Prefix | ::/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 | Routable | False | 508 | Global | False | 509 +------------------+---------------------+ 511 Table 19: Unspecified Address 513 +------------------+---------------------+ 514 | Attribute | Value | 515 +------------------+---------------------+ 516 | Prefix | ::FFFF:0:0/96 | 517 | Name | IPv4-mapped Address | 518 | RFC | [RFC4291] | 519 | Allocation Date | February 2006 | 520 | Termination Date | N/A | 521 | Source | False | 522 | Destination | False | 523 | Routable | False | 524 | Global | False | 525 +------------------+---------------------+ 527 Table 20: IPv4-mapped Address 529 +------------------+---------------------+ 530 | Attribute | Value | 531 +------------------+---------------------+ 532 | Prefix | 0100::/64 | 533 | Name | Discard-Only Prefix | 534 | RFC | [RFC6666] | 535 | Allocation Date | June 2012 | 536 | Termination Date | N/A | 537 | Source | True | 538 | Destination | True | 539 | Routable | True | 540 | Global | False | 541 +------------------+---------------------+ 543 Table 21: Discard-Only Prefix 545 +------------------+---------------------------+ 546 | Attribute | Value | 547 +------------------+---------------------------+ 548 | Prefix | 2001:0000::/23 | 549 | Name | IETF Protocol Assignments | 550 | RFC | [RFC2928] | 551 | Allocation Date | September 2000 | 552 | Termination Date | N/A | 553 | Source | False[3] | 554 | Destination | False[3] | 555 | Routable | False[3] | 556 | Global | False[3] | 557 +------------------+---------------------------+ 559 Table 22: IETF Protocol Assignments 561 [3] Unless allowed by a more specific allocation 563 +------------------+----------------+ 564 | Attribute | Value | 565 +------------------+----------------+ 566 | Prefix | 2001:0000::/32 | 567 | Name | TEREDO | 568 | RFC | [RFC4380] | 569 | Allocation Date | January 2006 | 570 | Termination Date | N/A | 571 | Source | True | 572 | Destination | True | 573 | Routable | True | 574 | Global | False | 575 +------------------+----------------+ 576 Table 23: TEREDO 578 +------------------+----------------+ 579 | Attribute | Value | 580 +------------------+----------------+ 581 | Prefix | 2001:0002::/48 | 582 | Name | Benchmarking | 583 | RFC | [RFC5180] | 584 | Allocation Date | April 2008 | 585 | Termination Date | N/A | 586 | Source | True | 587 | Destination | True | 588 | Routable | True | 589 | Global | False | 590 +------------------+----------------+ 592 Table 24: Benchmarking 594 +------------------+---------------+ 595 | Attribute | Value | 596 +------------------+---------------+ 597 | Prefix | 2001:db8::/32 | 598 | Name | Documentation | 599 | RFC | [RFC3849] | 600 | Allocation Date | July 2004 | 601 | Termination Date | N/A | 602 | Source | False | 603 | Destination | False | 604 | Routable | False | 605 | Global | False | 606 +------------------+---------------+ 608 Table 25: Documentation 610 +------------------+--------------+ 611 | Attribute | Value | 612 +------------------+--------------+ 613 | Prefix | 2001:10::/28 | 614 | Name | ORCHID | 615 | RFC | [RFC4843] | 616 | Allocation Date | March 2007 | 617 | Termination Date | March 2014 | 618 | Source | False | 619 | Destination | False | 620 | Routable | False | 621 | Global | False | 622 +------------------+--------------+ 624 Table 26: ORCHID 626 +------------------+---------------+ 627 | Attribute | Value | 628 +------------------+---------------+ 629 | Prefix | 2002::/16 [4] | 630 | Name | 6to4 | 631 | RFC | [RFC3056] | 632 | Allocation Date | February 2001 | 633 | Termination Date | N/A | 634 | Source | True | 635 | Destination | True | 636 | Routable | True | 637 | Global | N/A[4] | 638 +------------------+---------------+ 640 Table 27: 6to4 642 [4] See [RFC3056] for details. 644 +------------------+--------------+ 645 | Attribute | Value | 646 +------------------+--------------+ 647 | Prefix | FC00::/7 | 648 | Name | Unique-Local | 649 | RFC | [RFC4193] | 650 | Allocation Date | October 2005 | 651 | Termination Date | N/A | 652 | Source | True | 653 | Destination | True | 654 | Routable | True | 655 | Global | False | 656 +------------------+--------------+ 657 Table 28: Unique-Local 659 +------------------+-----------------------+ 660 | Attribute | Value | 661 +------------------+-----------------------+ 662 | Prefix | FE80::/10 | 663 | Name | Linked-Scoped Unicast | 664 | RFC | [RFC4291] | 665 | Allocation Date | February 2006 | 666 | Termination Date | N/A | 667 | Source | True | 668 | Destination | True | 669 | Routable | False | 670 | Global | False | 671 +------------------+-----------------------+ 673 Table 29: Linked-Scoped Unicast 675 +------------------+---------------+ 676 | Attribute | Value | 677 +------------------+---------------+ 678 | Prefix | FF00::/8 [5] | 679 | Name | Multicast | 680 | RFC | [RFC4291] | 681 | Allocation Date | February 2006 | 682 | Termination Date | N/A | 683 | Source | False | 684 | Destination | True | 685 | Routable | True | 686 | Global | N/A | 687 +------------------+---------------+ 689 Table 30: Multicast 691 [5] See [RFC4007] for global scoping for details 693 3. Security Considerations 695 Security of the Internet's routing system relies on the ability to 696 authenticate an assertion of unique control of an address block. 697 Measures to authenticate such assertions rely on validation that the 698 address block forms part of an existing allocated address block, and 699 that there is a trustable and unique reference in the IANA address 700 registries. 702 The proposed registry is intended to provide an authoritative source 703 of information regarding the currency and intended purpose of special 704 purpose address blocks that are designated from the IANA-administered 705 Special Purpose registry. This is a small step towards the creation 706 of a comprehensive registry framework that can be used as a trust 707 point for commencing a chain of address validation. Consideration 708 should be given to IANA registry publication formats that are machine 709 parseable, and also the use of file signatures and associated 710 certificate mechanisms to allow applications to confirm that the 711 registry contents are current, and that they have been published by 712 the IANA. 714 4. Acknowledgements 716 The authors would like to acknowledge an anonymous donor, without 717 whom this document would not have been written. 719 5. References 721 5.1. Normative References 723 [RFC4773] Huston, G., "Administration of the IANA Special Purpose 724 IPv6 Address Block", RFC 4773, December 2006. 726 [RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, 727 April 2008. 729 [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", 730 BCP 153, RFC 5735, January 2010. 732 [RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special 733 Purpose Address Registry", RFC 5736, January 2010. 735 5.2. Informative References 737 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 738 RFC 919, October 1984. 740 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 741 RFC 1112, August 1989. 743 [RFC1122] Braden, R., "Requirements for Internet Hosts - 744 Communication Layers", STD 3, RFC 1122, October 1989. 746 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 747 E. Lear, "Address Allocation for Private Internets", 748 BCP 5, RFC 1918, February 1996. 750 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 751 Network Interconnect Devices", RFC 2544, March 1999. 753 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 754 IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. 756 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 757 via IPv4 Clouds", RFC 3056, February 2001. 759 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", 760 RFC 3068, June 2001. 762 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 763 Reserved for Documentation", RFC 3849, July 2004. 765 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 766 Configuration of IPv4 Link-Local Addresses", RFC 3927, 767 May 2005. 769 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 770 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 771 March 2005. 773 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 774 Addresses", RFC 4193, October 2005. 776 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 777 Architecture", RFC 4291, February 2006. 779 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 780 Network Address Translations (NATs)", RFC 4380, 781 February 2006. 783 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 784 for Overlay Routable Cryptographic Hash Identifiers 785 (ORCHID)", RFC 4843, April 2007. 787 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 788 Dugatkin, "IPv6 Benchmarking Methodology for Network 789 Interconnect Devices", RFC 5180, May 2008. 791 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 792 Reserved for Documentation", RFC 5737, January 2010. 794 [RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for 795 IPv4 Multicast Address Assignments", BCP 51, RFC 5771, 796 March 2010. 798 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 799 Stack Lite Broadband Deployments Following IPv4 800 Exhaustion", RFC 6333, August 2011. 802 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 803 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 804 Space", BCP 153, RFC 6598, April 2012. 806 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 807 RFC 6666, August 2012. 809 Authors' Addresses 811 Michelle Cotton 812 Internet Corporation for Assigned Names and Numbers 813 12025 Waterfront Drive, Suite 300 814 Los Angeles, CA 90094-2536 815 USA 817 Phone: +310-823-9358 818 Fax: 819 Email: michelle.cotton@icann.org 820 URI: http://www.icann.org/ 822 Leo Vegoda 823 Internet Corporation for Assigned Names and Numbers 824 12025 Waterfront Drive, Suite 300 825 LosAngeles, CA 90094-2536 826 USA 828 Phone: +310-823-9358 829 Fax: 830 Email: leo.vegoda@icann.org 831 URI: http://www.icann.org/ 833 Ronald P Bonica (editor) 834 Juniper Networks 835 2251 Corporate Park Drive 836 Herndon, Virginia 20171 837 USA 839 Email: rbonica@juniper.net 840 Brian Haberman 841 Johns Hopkins University Applied Physics Lab 842 11100 Johns Hopkins Road 843 Laurel, Maryland 20723-6099 844 USA 846 Email: brian@innovationslab.net