Skip to main content

IPv6 Testing Address Allocation
draft-ietf-ipngwg-testv2-addralloc-00

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 2471.
Authors Robert L. Fink , Bob Hinden , Dr. Jon Postel
Last updated 2013-03-02 (Latest revision 1997-05-27)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Experimental
Formats
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 2471 (Historic)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-ipngwg-testv2-addralloc-00
INTERNET-DRAFT                              R. Hinden, Ipsilon Networks
May 27, 1997                                              R. Fink, LBNL
                                                         J. Postel, ISI

                    IPv6 Testing Address Allocation

               <draft-ietf-ipngwg-testv2-addralloc-00.txt>

Status of this Memo

   This document is an Internet Draft.  Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its Areas,
   and its Working Groups.  Note that other groups may also distribute
   working documents as Internet Drafts.

   Internet Drafts are draft documents valid for a maximum of six
   months.  Internet Drafts may be updated, replaced, or obsoleted by
   other documents at any time.  It is not appropriate to use Internet
   Drafts as reference material or to cite them other than as a
   ``working draft'' or ``work in progress.''

   Please check the 1id-abstracts.txt listing contained in the internet-
   drafts Shadow Directories on nic.ddn.mil, nnsc.nsf.net,
   nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au to learn the
   current status of any Internet Draft.

   This draft expires in November 27, 1997.

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.

   This document is intended to replace RFC1897 "IPv6 Testing Address
   Allocation", January 1996.  RFC1897 will become historic.

   The addresses described in this document are consistent with the IPv6

draft-ietf-ipngwg-testv2-addralloc-00.txt                        [Page 1]
INTERNET-DRAFT       IPv6 Testing Address Allocation        May 27, 1997

   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",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

2.0 Address Format

   The address format for the IPv6 test address is consistent with the
   aggregatable global unicast address allocation [AGGR] which is as
   follows:

      | 3 |  13 |    32     |   16   |          64 bits               |
      +---+-----+-----------+--------+--------------------------------+
      |FP | TLA |   NLA*    |  SLA*  |         Interface ID           |
      +---+-----+-----------+--------+--------------------------------+

   where:

      FP = 001 = Format Prefix

           This is the Format Prefix used to identify aggregatable
           global unicast addresses.

      TLA = 0x1FFE = Top Level Aggregator

           This is a TLA 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 (Bob Fink at the present time).  The use
           of this TLA is temporary.  All users of these addresses in
           this TLA will be required to renumber at some time in the
           future.

      NLA* = Next-Level Aggregator(s)

           The NLA* space will be assigned, by the TLA 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* = Site-Level Aggregator(s)

draft-ietf-ipngwg-testv2-addralloc-00.txt                        [Page 2]
INTERNET-DRAFT       IPv6 Testing Address Allocation        May 27, 1997

           The SLA* field is used by an individual organization to
           create its own local addressing hierarchy and to identify
           subnets.  Assignment of the SLA* field is the responsibility
           of each individual organization.

      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",
             Internet Draft, <draft-ietf-ipngwg-addr-arch-00.txt>, May
             1997.

   [AGGR]    Hinden, R., Deering, S., O'Dell, M., "An Aggregatable
             Global Unicast Address Format", internet draft, <draft-
             ietf-ipngwg-unicast-aggr-00.txt>, May 1997.

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

   [DHCP6]   Bound, J., "Host Configuration Protocol for IPv6", Internet
             Draft, <draft-ietf-dhc-dhcpv6-02.txt>, July 1995.

   [ETHER]   Crawford, M., "Transmission of IPv6 Packets over Ethernet
             Networks", Internet Draft, <draft-ietf-ipngwg-trans-
             ethernet-00.txt>, March 1997.

   [FDDI]    Crawford, M., "Transmission of IPv6 Packets over FDDI
             Networks", Internet Draft, <draft-ietf-ipngwg-trans-fddi-
             net-00.txt>, March 1997.

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
             Requirement Levels", RFC2119, BCP14, March 1997.

5.0 Security Considerations

   Documents of this type do not directly impact the security of the
   Internet infrastructure or its applications.

draft-ietf-ipngwg-testv2-addralloc-00.txt                        [Page 3]
INTERNET-DRAFT       IPv6 Testing Address Allocation        May 27, 1997

6.0  Authors Address

   Robert M. Hinden                          phone: +1 408 990-2004
   Ipsilon Networks, Inc.                    email: hinden@ipsilon.com
   232 Java Drive
   Sunnyvale, CA 94089
   USA

   Robert Fink                               phone: +1 510 486-5692
   Lawrence Berkeley National Laboratory     email: rlfink@lbl.gov
   MS 50A-3111
   Berkeley, CA 94720
   USA

   Jon Postel                                phone: +1 310 822 1511
   Information Sciences Institute            email: postel@isi.edu
   4676 Admiralty Way
   Marina del Rey, CA 90292-6695
   USA

draft-ietf-ipngwg-testv2-addralloc-00.txt                        [Page 4]