| TOC |
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
Copyright © The Internet Society (1998). All Rights Reserved.
| TOC |
2. Address Format
3. References (BOILERPLATE)
4. Security Considerations
5. Authors' Addresses (BOILERPLATE)
6. Full Copyright Statement (BOILERPLATE)
§ Authors' Addresses
§ Intellectual Property and Copyright Statements
This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. These addresses are temporary and will be reclaimed in the future. Any IPv6 system using these addresses will have to renumber at some time in the future. These addresses will not to be routable in the Internet other than for IPv6 testing.
The address format for the IPv6 test address is consistent with the "Aggregatable Global Unicast Address Allocation" [RFC2374] (Hinden, R. and S. Deering, “An IPv6 Aggregatable Global Unicast Address Format,” July 1998.) and "TLA and NLA Assignment Rules" [_XREF_TLAASN] (Hinden, R., “TLA and NLA Assignment Rules,” .).
This document is intended to replace RFC 1897 "IPv6 Testing Address Allocation", January 1996. RFC 1897 will become historic.
The addresses described in this document are consistent with the IPv6 Addressing Architecture [RFC2373] (Hinden, R. and S. Deering, “IP Version 6 Addressing Architecture,” July 1998.). They may be assigned to nodes manually, with IPv6 Auto Address Allocation [RFC1971] (Thomson, S. and T. Narten, “IPv6 Stateless Address Autoconfiguration,” August 1996.), or with DHCP for IPv6 [DHCPv6].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).
The Aggregatable Global Unicast Address Allocation format defined in [RFC2374] (Hinden, R. and S. Deering, “An IPv6 Aggregatable Global Unicast Address Format,” July 1998.) is as follows:
| 3 | 13 | 32 | 16 | 64 bits | +---+-----+-----------+--------+--------------------------------+ |FP | TLA | NLA ID | SLA ID | Interface ID | | | ID | | | | +---+-----+-----------+--------+--------------------------------+
FP = 001 = Format Prefix
This is the Format Prefix used to identify aggregatable global unicast addresses.
TLA = 0x1FFE = Top-Level Aggregation Identifier
This is a TLA ID assigned by the IANA for 6bone testing under the auspices of the IETF IPng Transition Working Group 6bone testbed activity. It is to be administered by the chair of the 6bone activity (currently Bob Fink <firstname.lastname@example.org>). The use of this TLA ID is temporary. All users of these addresses in this TLA ID will be required to renumber at some time in the future.
NLA ID = Next-Level Aggregation Identifier
The NLA ID space will be assigned, by the TLA ID administrator, in an addressing hierarchy sufficient to identify transit networks and end user sites consistent with the architecture and topology of the 6bone. This will provide a multi-level transit service consistent with the 6bone goals of fully testing IPv6 technology in real use environments.
SLA ID = Site-Level Aggregation Identifier
The SLA ID field is used by an individual organization to create its own local addressing hierarchy and to identify subnets. Assignment of the SLA ID field is the responsibility of each individual organization.
This is the interface identifier of the interface on the link as defined in the appropriate IPv6 over <link> document, such as [RFC2464] (Crawford, M., “Transmission of IPv6 Packets over Ethernet Networks,” December 1998.), [RFC2467] (Crawford, M., “Transmission of IPv6 Packets over FDDI Networks,” December 1998.), etc.
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "References."
This document defines a test approach for creating aggregatable address consistent with [RFC2374] (Hinden, R. and S. Deering, “An IPv6 Aggregatable Global Unicast Address Format,” July 1998.). It does not have any direct impact on Internet infrastructure security. Authentication of IPv6 packets is defined in [AUTH].
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Author's Address."
This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Full Copyright Statement."
|[RFC2373]||Hinden, R. and S. Deering, “IP Version 6 Addressing Architecture,” RFC 2373, July 1998 (TXT, HTML, XML).|
|[RFC2374]||Hinden, R. and S. Deering, “An IPv6 Aggregatable Global Unicast Address Format,” RFC 2374, July 1998 (TXT, HTML, XML).|
|[RFC1971]||Thomson, S. and T. Narten, “IPv6 Stateless Address Autoconfiguration,” RFC 1971, August 1996 (TXT).|
|[_XREF_DHCP6]||Bound, J., “Host Configuration Protocol for IPv6.”|
|[RFC2464]||Crawford, M., “Transmission of IPv6 Packets over Ethernet Networks,” RFC 2464, December 1998 (TXT, HTML, XML).|
|[RFC2467]||Crawford, M., “Transmission of IPv6 Packets over FDDI Networks,” RFC 2467, December 1998 (TXT, HTML, XML).|
|[RFC2119]||Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).|
|[_XREF_TLAASN]||Hinden, R., “TLA and NLA Assignment Rules.”|
|Robert M. Hinden|
|232 Java Drive|
|Sunnyvale, CA 94089|
|Phone:||+1 408 990-2004|
|Lawrence Berkeley National Laboratory|
|Berkeley, CA 94720|
|Phone:||+1 510 486-5692|
|Information Sciences Institute|
|4676 Admiralty Way|
|Marina del Rey, CA 90292-6695|
Copyright © The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP 11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.