idnits 2.17.00 (12 Aug 2021) /tmp/idnits8946/draft-ietf-sidr-iana-objects-02.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 8 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 5 instances 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 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 8, 2011) is 4060 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC0919' is defined on line 320, but no explicit reference was found in the text == Unused Reference: 'RFC0922' is defined on line 323, but no explicit reference was found in the text == Unused Reference: 'RFC1112' is defined on line 326, but no explicit reference was found in the text == Unused Reference: 'RFC1122' is defined on line 329, but no explicit reference was found in the text == Unused Reference: 'RFC2544' is defined on line 342, but no explicit reference was found in the text == Unused Reference: 'RFC3879' is defined on line 358, but no explicit reference was found in the text == Unused Reference: 'RFC3927' is defined on line 361, but no explicit reference was found in the text == Unused Reference: 'RFC4843' is defined on line 375, but no explicit reference was found in the text == Unused Reference: 'RFC5737' is defined on line 389, but no explicit reference was found in the text == Outdated reference: draft-ietf-sidr-arch has been published as RFC 6480 ** Downref: Normative reference to an Informational draft: draft-ietf-sidr-arch (ref. 'I-D.ietf-sidr-arch') == Outdated reference: draft-ietf-sidr-cp has been published as RFC 6484 == Outdated reference: draft-ietf-sidr-ghostbusters has been published as RFC 6493 == Outdated reference: draft-ietf-sidr-res-certs has been published as RFC 6487 == Outdated reference: draft-ietf-sidr-roa-format has been published as RFC 6482 == Outdated reference: draft-ietf-sidr-roa-validation has been published as RFC 6483 ** Downref: Normative reference to an Informational draft: draft-ietf-sidr-roa-validation (ref. 'I-D.ietf-sidr-roa-validation') == Outdated reference: draft-ietf-sidr-rpki-manifests has been published as RFC 6486 == Outdated reference: A later version (-08) exists of draft-ietf-sidr-ltamgmt-00 == Outdated reference: draft-ietf-sidr-usecases has been published as RFC 6907 -- Obsolete informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) -- Obsolete informational reference (is this intentional?): RFC 3068 (Obsoleted by RFC 7526) -- Obsolete informational reference (is this intentional?): RFC 4843 (Obsoleted by RFC 7343) -- 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: 2 errors (**), 0 flaws (~~), 23 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Manderson 3 Internet-Draft L. Vegoda 4 Intended status: Standards Track ICANN 5 Expires: October 10, 2011 S. Kent 6 BBN 7 April 8, 2011 9 RPKI Objects issued by IANA 10 draft-ietf-sidr-iana-objects-02.txt 12 Abstract 14 This document provides specific direction to IANA as to the Resource 15 Public Key Infrastructure (RPKI) objects it should issue. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on October 10, 2011. 34 Copyright Notice 36 Copyright (c) 2011 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 52 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 3. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 5 54 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 55 5. Reserved Resources . . . . . . . . . . . . . . . . . . . . . . 7 56 6. Unallocated Resources . . . . . . . . . . . . . . . . . . . . 8 57 7. Special Purpose Registry Resources . . . . . . . . . . . . . . 9 58 8. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . 10 59 9. Informational Objects . . . . . . . . . . . . . . . . . . . . 11 60 10. Certificates and CRLs . . . . . . . . . . . . . . . . . . . . 12 61 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 62 12. Security Considerations . . . . . . . . . . . . . . . . . . . 14 63 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 64 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 65 14.1. Normative References . . . . . . . . . . . . . . . . . . 16 66 14.2. Informative References . . . . . . . . . . . . . . . . . 16 67 Appendix A. IANA Reserved IPv4 Address Blocks . . . . . . . . . . 19 68 Appendix B. IANA Reserved IPv6 Address Blocks . . . . . . . . . . 20 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 71 1. Requirements Notation 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in [RFC2119]. 77 2. Introduction 79 An Infrastructure to Support Secure Internet Routing 80 [I-D.ietf-sidr-arch] directs IANA [RFC2860] to issue Resource Public 81 Key Infrastructure (RPKI) objects for which it is authoritative. 82 This document describes the objects IANA will issue. 84 The signed objects described here that IANA will issue are the 85 unallocated, reserved, special use IPv4 and IPv6 address blocks, and 86 reserved Autonomous System numbers. These number resources are 87 managed by IANA for the IETF, and thus IANA bears the responsibility 88 of issuing the corresponding RPKI objects. The reader is encouraged 89 to consider the technical effects on the public routing system of the 90 signed object issuance proposed for IANA in this document. 92 This document does not deal with localized BGP [RFC4271] routing 93 systems as those are under the policy controls of the organizations 94 that operate them. Readers are directed to Local Trust Anchor 95 Management for the Resource Public Key Infrastructure 96 [I-D.ietf-sidr-ltamgmt] for a description of how to locally override 97 IANA issued objects, e.g. to enable use of unallocated, reserved, and 98 special use IPv4 and IPv6 address blocks in a local context. 100 The direction to IANA contained herein follows the ideal that it 101 should represent the perfect technical behavior in registry, and 102 related registry, actions. 104 3. Suggested Reading 106 Readers should be familiar with the RPKI, the RPKI Repository 107 Structure, and the various RPKI objects, uses and interpretations 108 described in the following: [I-D.ietf-sidr-arch], 109 [I-D.ietf-sidr-res-certs], [I-D.ietf-sidr-roa-format], 110 [I-D.ietf-sidr-ghostbusters], [I-D.ietf-sidr-ltamgmt], 111 [I-D.ietf-sidr-roa-validation], [I-D.ietf-sidr-usecases], 112 [I-D.ietf-sidr-cp], and [I-D.ietf-sidr-rpki-manifests]. 114 NOTE: The addresses used in this document are not example addresses 115 therefore they are not compliant with [RFC3849], [RFC5735], and 116 [RFC5771]. This is intentional as the practices described in this 117 document affect real world addresses. 119 4. Definitions 121 Internet Number Resources (INR): The number identifiers for IPv4 122 [RFC0791] and IPv6 [RFC2460] addresses, and for Autonomous Systems. 124 IANA: Internet Assigned Numbers Authority (a traditional name, used 125 here to refer to the technical team making and publishing the 126 assignments of Internet protocol technical parameters). The 127 technical team of IANA is currently a part of ICANN [RFC2860]. 129 RPKI: Resource Public Key Infrastructure. A Public Key 130 Infrastructure designed to provide a secure basis for assertions 131 about holdings of Internet numeric resources. Certificates issued 132 under the RPKI contain additional attributes that identify IPv4, 133 IPv6, and Autonomous System Number (ASN) resources. 135 ROA: Route Origination Authorization. A ROA is an RPKI object that 136 enables the holder of the address prefix to specify an AS that is 137 permitted to originate (in BGP) routes for that prefix. 139 AS0 ROA: Validation of Route Origination using the Resource 140 Certificate PKI and ROAs [I-D.ietf-sidr-roa-validation] states "A ROA 141 with a subject of AS0 (AS0-ROA) is an attestation by the holder of a 142 prefix that the prefix described in the ROA, and any more specific 143 prefix, should not be used in a routing context." 145 "Not intended to be (publicly) routed": This phrase refers to 146 prefixes that are not meant to be represented in the global Internet 147 routing table (for example 192.168/16, [RFC1918]). 149 5. Reserved Resources 151 Reserved IPv4 and IPv6 resources are held back for various reasons by 152 IETF action. Generally such resources are not intended to be 153 globally routed. An example of such a reservation is 127.0.0.0/8 154 [RFC5735]. See Appendix A (Appendix A) and B (Appendix B) for IANA 155 reserved resources. 157 IANA SHOULD issue an AS0 ROA for all reserved IPv4 and IPv6 resources 158 not intended to be routed. 160 There are a small number of reserved resources which are intended to 161 be routed, for example 192.88.99.0/24 [RFC3068]. See Appendix A 162 (Appendix A) and B (Appendix B) for IANA reserved resources. 164 IANA MUST NOT issue any ROAs (AS0 or otherwise) for reserved 165 resources that are expected to be globally routed. 167 6. Unallocated Resources 169 Internet Number Resources that have not yet been allocated for 170 special purposes [RFC5736], to Regional Internet Registries (RIRs), 171 or to others are considered as not intended to be globally routed. 173 IANA MUST issue an AS0 ROA for all Unallocated Resources. 175 7. Special Purpose Registry Resources 177 Special Registry Resources [RFC5736] fall into one of two categories 178 in terms of routing. Either the resource is intended to be seen in 179 the global Internet routing table in some fashion, or it isn't. An 180 example of a special purpose registry INR that is intended for global 181 routing is 2001:0000::/32 [RFC4380]. An example of an INR not 182 intended to be seen would be 2001:002::/48 [RFC5180]. 184 IANA MUST NOT issue any ROAs (AS0 or otherwise) for Special Purpose 185 Registry Resources that are intended to be globally routed. 187 IANA MUST issue an AS0 ROA for Special Purpose Registry Resources 188 that are not intended to be globally routed. 190 8. Multicast 192 Within the IPv4 Multicast [RFC5771] and IPv6 Multicast [RFC4291] 193 registries there are a number of Multicast registrations that are not 194 intended to be globally routed. 196 IANA MUST issue an AS0 ROA covering the following IPv4 and IPv6 197 multicast INRs: 199 IPv4: 200 - Local Network Control Block 201 224.0.0.0 - 224.0.0.255 (224.0.0/24) 202 - IANA Reserved portions of RESERVED 203 224.1.0.0-224.1.255.255 (224.1/16) 204 - RESERVED 205 224.5.0.0-224.251.255.255 (251 /16s) 206 225.0.0.0-231.255.255.255 (7 /8s) 208 IPv6: 209 - Node-Local Scope Multicast Addresses 210 - Link-Local Scope Multicast Addresses 212 IANA MUST NOT issue any ROAs (AS0 or otherwise) for any other 213 multicast addresses unless directed by an IESG approved standards 214 track document with an appropriate IANA Considerations section. 216 9. Informational Objects 218 One informational object that can exist at a publication point of an 219 RPKI repository is the Ghostbusters Record 220 [I-D.ietf-sidr-ghostbusters]. 222 IANA MUST issue a ghostbusters object appropriate in content for the 223 resources IANA maintains. 225 10. Certificates and CRLs 227 Before IANA can issue a ROA it MUST first establish a RPKI 228 Certificate Authority (CA) that covers unallocated, reserved, and 229 special use INRs by containing RFC 3379 extensions [RFC3779] for 230 those corresponding number resources in the CA Certificate. This CA 231 MUST issue single use End Entity (EE) certificates for each ROA. The 232 EE certificate will conform to the Resource Certificate Profile 233 [I-D.ietf-sidr-res-certs] and the additional constraints specified in 234 [I-D.ietf-sidr-roa-format]. IANA MUST maintain a publication point 235 for this CA's use and publish manifests 236 [I-D.ietf-sidr-rpki-manifests] (with its corresponding EE 237 certificate). A Certificate Revocation List (CRL) will be issued 238 under this CA certificate. All objects issued by this CA will 239 conform to a published Certificate Policy [I-D.ietf-sidr-cp]. 241 11. IANA Considerations 243 This document directs IANA to issue, or refrain from issuing, the 244 specific objects described here for the current set of reserved, 245 unallocated, and special registry Internet Number Resources. Further 246 it MUST notify all other INR registries that RPKI objects have been 247 issued for specific Internet Number Resources to avoid duplicates 248 being issued thus reducing the burden on any relying party. 250 12. Security Considerations 252 This document does not alter the security profile of the RPKI from 253 that already discussed in SIDR-WG documents. 255 13. Acknowledgements 257 The authors acknowledge Dave Meyer for helpful direction with regard 258 to multicast assignments. 260 14. References 262 14.1. Normative References 264 [I-D.ietf-sidr-arch] 265 Lepinski, M. and S. Kent, "An Infrastructure to Support 266 Secure Internet Routing", draft-ietf-sidr-arch-12 (work in 267 progress), February 2011. 269 [I-D.ietf-sidr-cp] 270 Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 271 Policy (CP) for the Resource PKI (RPKI", 272 draft-ietf-sidr-cp-16 (work in progress), December 2010. 274 [I-D.ietf-sidr-ghostbusters] 275 Bush, R., "The RPKI Ghostbusters Record", 276 draft-ietf-sidr-ghostbusters-03 (work in progress), 277 March 2011. 279 [I-D.ietf-sidr-res-certs] 280 Huston, G., Michaelson, G., and R. Loomans, "A Profile for 281 X.509 PKIX Resource Certificates", 282 draft-ietf-sidr-res-certs-21 (work in progress), 283 December 2010. 285 [I-D.ietf-sidr-roa-format] 286 Lepinski, M., Kent, S., and D. Kong, "A Profile for Route 287 Origin Authorizations (ROAs)", 288 draft-ietf-sidr-roa-format-10 (work in progress), 289 February 2011. 291 [I-D.ietf-sidr-roa-validation] 292 Huston, G. and G. Michaelson, "Validation of Route 293 Origination using the Resource Certificate PKI and ROAs", 294 draft-ietf-sidr-roa-validation-10 (work in progress), 295 November 2010. 297 [I-D.ietf-sidr-rpki-manifests] 298 Austein, R., Huston, G., Kent, S., and M. Lepinski, 299 "Manifests for the Resource Public Key Infrastructure", 300 draft-ietf-sidr-rpki-manifests-09 (work in progress), 301 November 2010. 303 14.2. Informative References 305 [I-D.ietf-sidr-ltamgmt] 306 Kent, S. and M. Reynolds, "Local Trust Anchor Management 307 for the Resource Public Key Infrastructure", 308 draft-ietf-sidr-ltamgmt-00 (work in progress), 309 November 2010. 311 [I-D.ietf-sidr-usecases] 312 Manderson, T., Sriram, K., and R. White, "Use Cases and 313 interpretation of RPKI objects for issuers and relying 314 parties", draft-ietf-sidr-usecases-01 (work in progress), 315 December 2010. 317 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 318 September 1981. 320 [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, 321 RFC 919, October 1984. 323 [RFC0922] Mogul, J., "Broadcasting Internet datagrams in the 324 presence of subnets", STD 5, RFC 922, October 1984. 326 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 327 RFC 1112, August 1989. 329 [RFC1122] Braden, R., "Requirements for Internet Hosts - 330 Communication Layers", STD 3, RFC 1122, October 1989. 332 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 333 E. Lear, "Address Allocation for Private Internets", 334 BCP 5, RFC 1918, February 1996. 336 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 337 Requirement Levels", BCP 14, RFC 2119, March 1997. 339 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 340 (IPv6) Specification", RFC 2460, December 1998. 342 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 343 Network Interconnect Devices", RFC 2544, March 1999. 345 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 346 Understanding Concerning the Technical Work of the 347 Internet Assigned Numbers Authority", RFC 2860, June 2000. 349 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", 350 RFC 3068, June 2001. 352 [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP 353 Addresses and AS Identifiers", RFC 3779, June 2004. 355 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 356 Reserved for Documentation", RFC 3849, July 2004. 358 [RFC3879] Huitema, C. and B. Carpenter, "Deprecating Site Local 359 Addresses", RFC 3879, September 2004. 361 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 362 Configuration of IPv4 Link-Local Addresses", RFC 3927, 363 May 2005. 365 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 366 Protocol 4 (BGP-4)", RFC 4271, January 2006. 368 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 369 Architecture", RFC 4291, February 2006. 371 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 372 Network Address Translations (NATs)", RFC 4380, 373 February 2006. 375 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix 376 for Overlay Routable Cryptographic Hash Identifiers 377 (ORCHID)", RFC 4843, April 2007. 379 [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. 380 Dugatkin, "IPv6 Benchmarking Methodology for Network 381 Interconnect Devices", RFC 5180, May 2008. 383 [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", 384 BCP 153, RFC 5735, January 2010. 386 [RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special 387 Purpose Address Registry", RFC 5736, January 2010. 389 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 390 Reserved for Documentation", RFC 5737, January 2010. 392 [RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for 393 IPv4 Multicast Address Assignments", BCP 51, RFC 5771, 394 March 2010. 396 Appendix A. IANA Reserved IPv4 Address Blocks 398 This list of Address Space and RFCs was correct at the time of 399 writing 401 IPv4 Address Blocks and the RFCs which direct IANA to Reserve them 403 +--------------------+------------------------------------+---------+ 404 | Prefix | RFC | TBR | 405 +--------------------+------------------------------------+---------+ 406 | 0.0.0.0/8 | RFC1122, Section 3.2.1.3 | No | 407 | | | | 408 | 10.0.0.0/8 | RFC1918 | No | 409 | | | | 410 | 127.0.0.0/8 | RFC1122, Section 3.2.1.3 | No | 411 | | | | 412 | 169.254.0.0/16 | RFC3927 | No | 413 | | | | 414 | 172.16.0.0/12 | RFC1918 | No | 415 | | | | 416 | 192.0.0.0/24 | RFC5736 | Various | 417 | | | | 418 | 192.0.2.0/24 | RFC5737 | No | 419 | | | | 420 | 192.88.99.0/24 | RFC3068 | Yes | 421 | | | | 422 | 192.168.0.0/16 | RFC1918 | No | 423 | | | | 424 | 198.18.0.0/15 | RFC2544 | No | 425 | | | | 426 | 198.51.100.0/24 | RFC5737 | No | 427 | | | | 428 | 203.0.113.0/24 | RFC5737 | No | 429 | | | | 430 | 224.0.0.0/4 | RFC5771 | No | 431 | | | | 432 | 240.0.0.0/4 | RFC1112, Section 4 | No | 433 | | | | 434 | 255.255.255.255/32 | RFC919, Section 7 and RFC922, | No | 435 | | Section 7 | | 436 +--------------------+------------------------------------+---------+ 438 TBR: To Be Routed, the intention of the RFC pertaining to the address 439 block. 441 Table 1 443 Appendix B. IANA Reserved IPv6 Address Blocks 445 This list of Address Space and RFCs was correct at the time of 446 writing 448 IPv6 Address Blocks and the RFCs which direct IANA to Reserve them 450 +----------------+---------+-----+ 451 | Prefix | RFC | TBR | 452 +----------------+---------+-----+ 453 | 0000::/8 | RFC4291 | No | 454 | | | | 455 | 0100::/8 | RFC4291 | No | 456 | | | | 457 | 0200::/7 | RFC4291 | No | 458 | | | | 459 | 0400::/6 | RFC4291 | No | 460 | | | | 461 | 0800::/5 | RFC4291 | No | 462 | | | | 463 | 1000::/4 | RFC4291 | No | 464 | | | | 465 | 4000::/3 | RFC4291 | No | 466 | | | | 467 | 6000::/3 | RFC4291 | No | 468 | | | | 469 | 8000::/3 | RFC4291 | No | 470 | | | | 471 | A000::/3 | RFC4291 | No | 472 | | | | 473 | C000::/3 | RFC4291 | No | 474 | | | | 475 | E000::/4 | RFC4291 | No | 476 | | | | 477 | F000::/5 | RFC4291 | No | 478 | | | | 479 | F800::/6 | RFC4291 | No | 480 | | | | 481 | FC00::/7 | RFC4193 | No | 482 | | | | 483 | FE00::/9 | RFC4291 | No | 484 | | | | 485 | FE80::/10 | RFC4291 | No | 486 | | | | 487 | FEC0::/10 | RFC3879 | No | 488 | | | | 489 | FF00::/8 | RFC4291 | No | 490 | | | | 491 | 2001:0002::/48 | RFC5180 | No | 492 | | | | 493 | 2001:10::/28 | RFC4843 | No | 494 +----------------+---------+-----+ 496 TBR: To Be Routed, the intention of the RFC pertaining to the address 497 block. 499 Table 2 501 Authors' Addresses 503 Terry Manderson 504 ICANN 506 Email: terry.manderson@icann.org 508 Leo Vegoda 509 ICANN 511 Email: leo.vegoda@icann.org 513 Steve Kent 514 BBN 516 Email: kent@bbn.com