idnits 2.17.00 (12 Aug 2021) /tmp/idnits39830/draft-bonica-special-purpose-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 10 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 3 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. == There are 6 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- The draft header indicates that this document obsoletes 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 (October 15, 2012) is 3505 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 310 -- Looks like a reference, but probably isn't: '2' on line 541 -- Looks like a reference, but probably isn't: '3' on line 623 -- Looks like a reference, but probably isn't: '4' on line 618 == Unused Reference: 'RFC4007' is defined on line 717, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 3068 (Obsoleted by RFC 7526) -- Obsolete informational reference (is this intentional?): RFC 4773 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 4843 (Obsoleted by RFC 7343) -- Obsolete informational reference (is this intentional?): RFC 5156 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 5735 (Obsoleted by RFC 6890) -- Obsolete informational reference (is this intentional?): RFC 5736 (Obsoleted by RFC 6890) Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 13 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: April 18, 2013 B. Haberman 9 Johns Hopkins University Applied 10 Physics Lab 11 October 15, 2012 13 Special-Purpose Address Registries 14 draft-bonica-special-purpose-03 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 April 18, 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 . . . . . . . . . . . . . . . . . . . . . . . 16 70 5. Informative References . . . . . . . . . . . . . . . . . . . . 16 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 73 1. Introduction 75 In order to support new protocols and practices, the IETF 76 occasionally reserves an address block a for special purpose. For 77 example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to 78 represent the local (i.e., "this") network. Likewise, [RFC4291] 79 reserves an IPv6 address block (fe80::/10) to represent link-scoped 80 unicast addresses. 82 Periodically, the IETF publishes an RFC that catalogs special-purpose 83 address blocks. Currently, [RFC5735] catalogs all IPv4 special- 84 purpose address blocks and [RFC5156] catalogs all IPv6 special- 85 purpose address blocks. 87 [RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and 88 instructs IANA to allocate special-purpose address blocks from this 89 space. [RFC5736] also instructs IANA to create an IPv4 Special- 90 Purpose Address Registry that records allocations from this address 91 space. However, [RFC5736] does not instruct IANA to record special- 92 purpose address block reservations from outside of the aforementioned 93 space in the IPv4 Special-Purpose Address Registry. 95 Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to 96 IANA and instructs IANA to allocate special-purpose address blocks 97 from this space. [RFC4773] instructs IANA to create an IPv6 Special- 98 Purpose Address Registry that records allocations from this address 99 space. However, [RFC4773] does not instruct IANA to record special- 100 purpose address block reservations from outside of the aforementioned 101 space in the IPv6 Special-Purpose Address Registry. 103 This memo instructs IANA to restructure its IPv4 and IPv6 Special- 104 Purpose Address Registries. Therefore, this document updates 105 [RFC5736] and [RFC4773] which define the current structure of the 106 aforementioned registries. 108 Specifically, this memo instructs IANA to record all special-purpose 109 address blocks in the aforementioned registries. These include, but 110 are not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6 111 allocations from 2001:0000::/23. When the aforementioned registries 112 include all special-purpose address blocks, [RFC5735] and [RFC5156] 113 will become redundant with the registries. Therefore, this memo 114 obsoletes [RFC5735] and [RFC5156]. 116 Furthermore, this memo defines: 118 o a common set of information that the registries will maintain 119 regarding each special-purpose address block 121 o a common set of requirements for future entries 123 2. IANA Considerations 125 IANA will restructure the following registries: 127 o IPv4 Special-Purpose Address Registry 129 o IPv6 Special-Purpose Address Registry 131 The IPv4 Special-Purpose Address Registry will record all IPv4 132 special-purpose address blocks. These reservations will include, but 133 not be limited to, allocations from the 192.0.0.0/24 address block. 134 Likewise, the IPv6 Special-Purpose Address Registry will record all 135 IPv6 special-purpose address blocks. These reservations will 136 include, but not be limited to, allocations from the 2001:0000::/23 137 address block. 139 Section 2.1 of this document describes information that both 140 registries will maintain for each entry. Initially, IANA will 141 populate the IPv4 Special-Purpose Address Registry with information 142 taken from Section 2.2 of this document. Likewise, IANA will 143 populate the IPv6 Special-Purpose Address Registry with information 144 taken from Section 2.3 of this document. 146 IANA will update the aforementioned registries as requested in the 147 "IANA Considerations" section of an IESG-reviewed document. The " 148 IANA Considerations" section must include all of the information 149 specified in Section 2.1 of this document. 151 2.1. Information Requirements 153 The IPv4 and IPv6 Special-Purpose Address Registries will maintain 154 the following information regarding each entry: 156 o Prefix - An IPv4 or IPv6 prefix that identifies the special- 157 purpose address block 159 o Name - A descriptive name for the special-purpose address block 161 o RFC - The RFC though which the special-purpose address block was 162 requested 164 o Allocation Date - The date upon which the special purpose address 165 block was allocated 167 o Termination Date - The date upon which the allocation is to be 168 terminated. This field is applicable for limited-use allocations 169 only. 171 o Source - A boolean value indicated 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 o Destination - A boolean value indicated 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 o Routable - A boolean value indicating whether a IP datagram whose 181 destination address is drawn from the allocated special-purpose 182 address block is routable (i.e., may traverse more than a single 183 IP interface) 185 o Global - A boolean value indicating whether a IP datagram whose 186 destination address is drawn from the allocated special-purpose 187 address block is routable beyond a specified administrative 188 domain. 190 If the value of "Destination" is FALSE, the values of "Routable" and 191 "Global" must also be false. 193 2.2. IPv4 Special-Purpose Address Registry Entries 195 Table 1 though Table 16, below, represent entries with which the IANA 196 will initially populate the IPv4 Special-Purpose Address Registry. 198 +------------------+---------------------------+ 199 | Attribute | Value | 200 +------------------+---------------------------+ 201 | Prefix | 0.0.0.0/8 | 202 | Name | "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 | Routable | False | 209 | Global | False | 210 +------------------+---------------------------+ 212 Table 1: "This" Network 214 +------------------+---------------+ 215 | Attribute | Value | 216 +------------------+---------------+ 217 | Prefix | 10.0.0.0/8 | 218 | Name | Private-Use | 219 | RFC | [RFC1918] | 220 | Allocation Date | February 1996 | 221 | Termination Date | N/A | 222 | Source | True | 223 | Destination | True | 224 | Routable | True | 225 | Global | False | 226 +------------------+---------------+ 228 Table 2: Private-Use Networks 230 +------------------+----------------------+ 231 | Attribute | Value | 232 +------------------+----------------------+ 233 | Prefix | 100.64.0.0/10 | 234 | Name | Shared Address Space | 235 | RFC | [RFC6598] | 236 | Allocation Date | April 2012 | 237 | Termination Date | N/A | 238 | Source | True | 239 | Destination | True | 240 | Routable | True | 241 | Global | False | 242 +------------------+----------------------+ 244 Table 3: Shared Address Space 246 +------------------+---------------------------+ 247 | Attribute | Value | 248 +------------------+---------------------------+ 249 | Prefix | 127.0.0.0/8 | 250 | Name | Loopback | 251 | RFC | [RFC1122] Section 3.2.1.3 | 252 | Allocation Date | September 1981 | 253 | Termination Date | N/A | 254 | Source | False | 255 | Destination | False | 256 | Routable | False | 257 | Global | False | 258 +------------------+---------------------------+ 260 Table 4: Loopback 262 +------------------+----------------+ 263 | Attribute | Value | 264 +------------------+----------------+ 265 | Prefix | 169.254.0.0/16 | 266 | Name | Link Local | 267 | RFC | [RFC3927] | 268 | Allocation Date | May 2005 | 269 | Termination Date | N/A | 270 | Source | True | 271 | Destination | True | 272 | Routable | False | 273 | Global | False | 274 +------------------+----------------+ 276 Table 5: Link Local 278 +------------------+---------------+ 279 | Attribute | Value | 280 +------------------+---------------+ 281 | Prefix | 172.16.0.0/12 | 282 | Name | Private-Use | 283 | RFC | [RFC1122] | 284 | Allocation Date | February 1996 | 285 | Termination Date | N/A | 286 | Source | True | 287 | Destination | True | 288 | Routable | True | 289 | Global | False | 290 +------------------+---------------+ 292 Table 6: Private-Use Networks 294 +------------------+---------------------------+ 295 | Attribute | Value | 296 +------------------+---------------------------+ 297 | Prefix | 192.0.0.0/24 [1] | 298 | Name | IETF Protocol Assignments | 299 | RFC | [RFC5736] | 300 | Allocation Date | January 2010 | 301 | Termination Date | N/A | 302 | Source | False | 303 | Destination | False | 304 | Routable | False | 305 | Global | False | 306 +------------------+---------------------------+ 308 Table 7: IETF Protocol Assignments 310 [1] Not useable unless by virtue of a more specific reservation. 312 +------------------+--------------+ 313 | Attribute | Value | 314 +------------------+--------------+ 315 | Prefix | 192.0.0.0/29 | 316 | Name | DS-Lite | 317 | RFC | [RFC6333] | 318 | Allocation Date | June 2011 | 319 | Termination Date | N/A | 320 | Source | True | 321 | Destination | True | 322 | Routable | True | 323 | Global | False | 324 +------------------+--------------+ 326 Table 8: DS-Lite 328 +------------------+----------------------------+ 329 | Attribute | Value | 330 +------------------+----------------------------+ 331 | Prefix | 192.0.2.0/24 | 332 | Name | Documentation (TEST-NET-1) | 333 | RFC | [RFC5737] | 334 | Allocation Date | January 2010 | 335 | Termination Date | N/A | 336 | Source | False | 337 | Destination | False | 338 | Routable | False | 339 | Global | False | 340 +------------------+----------------------------+ 342 Table 9: TEST-NET-1 344 +------------------+--------------------+ 345 | Attribute | Value | 346 +------------------+--------------------+ 347 | Prefix | 192.88.99.0/24 | 348 | Name | 6to4 Relay Anycast | 349 | RFC | [RFC3068] | 350 | Allocation Date | June 2001 | 351 | Termination Date | N/A | 352 | Source | True | 353 | Destination | True | 354 | Routable | True | 355 | Global | True | 356 +------------------+--------------------+ 358 Table 10: 6to4 Relay Anycast 360 +------------------+----------------+ 361 | Attribute | Value | 362 +------------------+----------------+ 363 | Prefix | 192.168.0.0/16 | 364 | Name | Private-Use | 365 | RFC | [RFC1918] | 366 | Allocation Date | February 196 | 367 | Termination Date | N/A | 368 | Source | True | 369 | Destination | True | 370 | Routable | True | 371 | Global | Flase | 372 +------------------+----------------+ 374 Table 11: Private-Use Networks 376 +------------------+---------------+ 377 | Attribute | Value | 378 +------------------+---------------+ 379 | Prefix | 198.18.0.0/15 | 380 | Name | Benchmarking | 381 | RFC | [RFC2544] | 382 | Allocation Date | March 1999 | 383 | Termination Date | N/A | 384 | Source | True | 385 | Destination | True | 386 | Routable | True | 387 | Global | False | 388 +------------------+---------------+ 390 Table 12: Network Interconnect Device Benchmark Testing 391 +------------------+----------------------------+ 392 | Attribute | Value | 393 +------------------+----------------------------+ 394 | Prefix | 198.51.100.0/24 | 395 | Name | Documentation (TEST-NET-2) | 396 | RFC | [RFC5737] | 397 | Allocation Date | January 2010 | 398 | Termination Date | N/A | 399 | Source | False | 400 | Destination | False | 401 | Routable | False | 402 | Global | False | 403 +------------------+----------------------------+ 405 Table 13: TEST-NET-2 407 +------------------+----------------------------+ 408 | Attribute | Value | 409 +------------------+----------------------------+ 410 | Prefix | 203.0.113.0/24 | 411 | Name | Documentation (TEST-NET-3) | 412 | RFC | [RFC5737] | 413 | Allocation Date | January 2010 | 414 | Termination Date | N/A | 415 | Source | False | 416 | Destination | False | 417 | Routable | False | 418 | Global | False | 419 +------------------+----------------------------+ 421 Table 14: TEST-NET-3 423 +------------------+---------------------+ 424 | Attribute | Value | 425 +------------------+---------------------+ 426 | Prefix | 240.0.0.0/4 | 427 | Name | Reserved | 428 | RFC | [RFC1112] Section 4 | 429 | Allocation Date | August 1989 | 430 | Termination Date | N/A | 431 | Source | False | 432 | Destination | False | 433 | Routable | False | 434 | Global | False | 435 +------------------+---------------------+ 437 Table 15: Reserved for Future Use 439 +------------------+---------------------+ 440 | Attribute | Value | 441 +------------------+---------------------+ 442 | Prefix | 255.255.255.255/32 | 443 | Name | Limited Broadcast | 444 | RFC | [RFC0919] Section 7 | 445 | Allocation Date | October 1984 | 446 | Termination Date | N/A | 447 | Source | False | 448 | Destination | True | 449 | Routable | False | 450 | Global | False | 451 +------------------+---------------------+ 453 Table 16: Limited Broadcast 455 2.3. IPv6 Special-Purpose Address Registry Entries 457 Table 17 through Table 28, below, represent entries with which the 458 IANA will initially populate the IPv6 Special-Purpose Address 459 Registry. 461 +------------------+------------------+ 462 | Attribute | Value | 463 +------------------+------------------+ 464 | Prefix | ::1/128 | 465 | Name | Loopback Address | 466 | RFC | [RFC4291] | 467 | Allocation Date | February 2006 | 468 | Termination Date | N/A | 469 | Source | False | 470 | Destination | False | 471 | Routable | False | 472 | Global | False | 473 +------------------+------------------+ 475 Table 17: Loopback Address 477 +------------------+---------------------+ 478 | Attribute | Value | 479 +------------------+---------------------+ 480 | Prefix | ::/128 | 481 | Name | Unspecified Address | 482 | RFC | [RFC4291] | 483 | Allocation Date | February 2006 | 484 | Termination Date | N/A | 485 | Source | True | 486 | Destination | False | 487 | Routable | False | 488 | Global | False | 489 +------------------+---------------------+ 491 Table 18: Unspecified Address 493 +------------------+---------------------+ 494 | Attribute | Value | 495 +------------------+---------------------+ 496 | Prefix | ::FFFF:0:0/96 | 497 | Name | IPv4-mapped Address | 498 | RFC | [RFC4291] | 499 | Allocation Date | February 2006 | 500 | Termination Date | N/A | 501 | Source | False | 502 | Destination | False | 503 | Routable | False | 504 | Global | False | 505 +------------------+---------------------+ 507 Table 19: IPv4-mapped Address 509 +------------------+---------------------+ 510 | Attribute | Value | 511 +------------------+---------------------+ 512 | Prefix | 0100::/64 | 513 | Name | Discard-Only Prefix | 514 | RFC | [RFC6666] | 515 | Allocation Date | June 2012 | 516 | Termination Date | N/A | 517 | Source | True | 518 | Destination | True | 519 | Routable | True | 520 | Global | False | 521 +------------------+---------------------+ 523 Table 20: Discard-Only Prefix 525 +------------------+---------------------------+ 526 | Attribute | Value | 527 +------------------+---------------------------+ 528 | Prefix | 2001:0000::/23 | 529 | Name | IETF Protocol Assignments | 530 | RFC | [RFC2928] | 531 | Allocation Date | September 2000 | 532 | Termination Date | N/A | 533 | Source | False[2] | 534 | Destination | False[2] | 535 | Routable | False[2] | 536 | Global | False[2] | 537 +------------------+---------------------------+ 539 Table 21: IETF Protocol Assignments 541 [2] Unless allowed by a more specific allocation 543 +------------------+----------------+ 544 | Attribute | Value | 545 +------------------+----------------+ 546 | Prefix | 2001:0000::/32 | 547 | Name | TEREDO | 548 | RFC | [RFC4380] | 549 | Allocation Date | January 2006 | 550 | Termination Date | N/A | 551 | Source | True | 552 | Destination | True | 553 | Routable | True | 554 | Global | False | 555 +------------------+----------------+ 557 Table 22: TEREDO 559 +------------------+----------------+ 560 | Attribute | Value | 561 +------------------+----------------+ 562 | Prefix | 2001:0002::/48 | 563 | Name | Benchmarking | 564 | RFC | [RFC5180] | 565 | Allocation Date | April 2008 | 566 | Termination Date | N/A | 567 | Source | True | 568 | Destination | True | 569 | Routable | True | 570 | Global | False | 571 +------------------+----------------+ 573 Table 23: Benchmarking 575 +------------------+---------------+ 576 | Attribute | Value | 577 +------------------+---------------+ 578 | Prefix | 2001:db8::/32 | 579 | Name | Documentation | 580 | RFC | [RFC3849] | 581 | Allocation Date | July 2004 | 582 | Termination Date | N/A | 583 | Source | False | 584 | Destination | False | 585 | Routable | False | 586 | Global | False | 587 +------------------+---------------+ 589 Table 24: Documentation 591 +------------------+--------------+ 592 | Attribute | Value | 593 +------------------+--------------+ 594 | Prefix | 2001:10::/28 | 595 | Name | ORCHID | 596 | RFC | [RFC4843] | 597 | Allocation Date | March 2007 | 598 | Termination Date | March 2014 | 599 | Source | False | 600 | Destination | False | 601 | Routable | False | 602 | Global | False | 603 +------------------+--------------+ 605 Table 25: ORCHID 607 +------------------+---------------+ 608 | Attribute | Value | 609 +------------------+---------------+ 610 | Prefix | 2002::/16 [3] | 611 | Name | 6to4 | 612 | RFC | [RFC3056] | 613 | Allocation Date | February 2001 | 614 | Termination Date | N/A | 615 | Source | True | 616 | Destination | True | 617 | Routable | True | 618 | Global | N/A[4] | 619 +------------------+---------------+ 621 Table 26: 6to4 623 [3] See [RFC3056] for details. 625 +------------------+--------------+ 626 | Attribute | Value | 627 +------------------+--------------+ 628 | Prefix | FC00::/7 | 629 | Name | Unique-Local | 630 | RFC | [RFC4193] | 631 | Allocation Date | October 2005 | 632 | Termination Date | N/A | 633 | Source | True | 634 | Destination | True | 635 | Routable | True | 636 | Global | False | 637 +------------------+--------------+ 639 Table 27: Unique-Local 641 +------------------+-----------------------+ 642 | Attribute | Value | 643 +------------------+-----------------------+ 644 | Prefix | FE80::/10 | 645 | Name | Linked-Scoped Unicast | 646 | RFC | [RFC4291] | 647 | Allocation Date | February 2006 | 648 | Termination Date | N/A | 649 | Source | True | 650 | Destination | True | 651 | Routable | False | 652 | Global | False | 653 +------------------+-----------------------+ 655 Table 28: Linked-Scoped Unicast 657 3. Security Considerations 659 Security of the Internet's routing system relies on the ability to 660 authenticate an assertion of unique control of an address block. 661 Measures to authenticate such assertions rely on validation that the 662 address block forms part of an existing allocated address block, and 663 that there is a trustable and unique reference in the IANA address 664 registries. 666 The proposed registry is intended to provide an authoritative source 667 of information regarding the currency and intended purpose of special 668 purpose address blocks that are designated from the IANA-administered 669 Special Purpose registry. This is a small step towards the creation 670 of a comprehensive registry framework that can be used as a trust 671 point for commencing a chain of address validation. Consideration 672 should be given to IANA registry publication formats that are machine 673 parseable, and also the use of file signatures and associated 674 certificate mechanisms to allow applications to confirm that the 675 registry contents are current, and that they have been published by 676 the IANA. 678 4. Acknowledgements 680 The authors would like to acknowledge an anonymous donor, without 681 whom this document would not have been written. 683 5. Informative References 685 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 686 RFC 919, October 1984. 688 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 689 RFC 1112, August 1989. 691 [RFC1122] Braden, R., "Requirements for Internet Hosts - 692 Communication Layers", STD 3, RFC 1122, October 1989. 694 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 695 E. Lear, "Address Allocation for Private Internets", 696 BCP 5, RFC 1918, February 1996. 698 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 699 Network Interconnect Devices", RFC 2544, March 1999. 701 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 702 IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. 704 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 705 via IPv4 Clouds", RFC 3056, February 2001. 707 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", 708 RFC 3068, June 2001. 710 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 711 Reserved for Documentation", RFC 3849, July 2004. 713 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 714 Configuration of IPv4 Link-Local Addresses", RFC 3927, 715 May 2005. 717 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 718 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 719 March 2005. 721 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 722 Addresses", RFC 4193, October 2005. 724 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 725 Architecture", RFC 4291, February 2006. 727 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 728 Network Address Translations (NATs)", RFC 4380, 729 February 2006. 731 [RFC4773] Huston, G., "Administration of the IANA Special Purpose 732 IPv6 Address Block", RFC 4773, December 2006. 734 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 735 for Overlay Routable Cryptographic Hash Identifiers 736 (ORCHID)", RFC 4843, April 2007. 738 [RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, 739 April 2008. 741 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 742 Dugatkin, "IPv6 Benchmarking Methodology for Network 743 Interconnect Devices", RFC 5180, May 2008. 745 [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", 746 BCP 153, RFC 5735, January 2010. 748 [RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special 749 Purpose Address Registry", RFC 5736, January 2010. 751 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 752 Reserved for Documentation", RFC 5737, January 2010. 754 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 755 Stack Lite Broadband Deployments Following IPv4 756 Exhaustion", RFC 6333, August 2011. 758 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 759 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 760 Space", BCP 153, RFC 6598, April 2012. 762 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 763 RFC 6666, August 2012. 765 Authors' Addresses 767 Michelle Cotton 768 Internet Corporation for Assigned Names and Numbers 769 12025 Waterfront Drive, Suite 300 770 Los Angeles, CA 90094-2536 771 USA 773 Phone: +310-823-9358 774 Fax: 775 Email: michelle.cotton@icann.org 776 URI: http://www.icann.org/ 777 Leo Vegoda 778 Internet Corporation for Assigned Names and Numbers 779 12025 Waterfront Drive, Suite 300 780 LosAngeles, CA 90094-2536 781 USA 783 Phone: +310-823-9358 784 Fax: 785 Email: leo.vegoda@icann.org 786 URI: http://www.icann.org/ 788 Ronald P Bonica (editor) 789 Juniper Networks 790 2251 Corporate Park Drive 791 Herndon, Virginia 20171 792 USA 794 Email: rbonica@juniper.net 796 Brian Haberman 797 Johns Hopkins University Applied Physics Lab 798 11100 Johns Hopkins Road 799 Laurel, Maryland 20723-6099 800 USA 802 Email: brian@innovationslab.net