IPv6 Testing Address Allocation
RFC 2471

Document Type RFC - Historic (December 1998; No errata)
Obsoleted by RFC 3701
Obsoletes RFC 1897
Authors Robert Fink  , Bob Hinden  , Jon Postel 
Last updated 2013-03-02
Stream IETF
Formats plain text html pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2471 (Historic)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         R. Hinden
Request for Comments: 2471                                        Nokia
Obsoletes: 1897                                                 R. Fink
Category: Experimental                                             LBNL
                                                              J. Postel
                                                          December 1998

                    IPv6 Testing Address Allocation

Status of this Memo

   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 Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

1.0 Introduction

   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" [AGGR] and "TLA and
   NLA Assignment Rules" [TLAASN].

   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 [ARCH].  They may be assigned to nodes
   manually, with IPv6 Auto Address Allocation [AUTO], or with DHCP for
   IPv6 [DHCPv6].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in [RFC2119].

Hinden, et. al.               Experimental                      [Page 1]
RFC 2471            IPv6 Testing Address Allocation        December 1998

2.0 Address Format

   The Aggregatable Global Unicast Address Allocation format defined in
   [AGGR] 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 <rlfink@lbl.gov>).
           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.

Hinden, et. al.               Experimental                      [Page 2]
RFC 2471            IPv6 Testing Address Allocation        December 1998

      Interface ID

           This is the interface identifier of the interface on the link
           as defined in the appropriate IPv6 over <link> document, such
           as [ETHER], [FDDI], etc.

4.0 References

   [ARCH]    Hinden, R., "IP Version 6 Addressing Architecture",
             RFC 2373, July 1998.

   [AGGR]    Hinden, R., Deering, S., O'Dell, M., "An Aggregatable
             Global Unicast Address Format", RFC 2374, July 1998.

   [AUTO]    Thompson, S. and T. Narten, "IPv6 Stateless Address
             Autoconfiguration", RFC 1971, August 1996.

   [DHCP6]   Bound, J., "Host Configuration Protocol for IPv6", Work in

   [ETHER]   Crawford, M., "Transmission of IPv6 Packets over Ethernet
             Networks", RFC 2464, December 1998.
Show full document text