IPV6 TOP LEVEL AGGREGATION IDENTIFIER ASSIGNMENTS

DEPRECATED BY [RFC4147]

THIS PAGE IS BEING PRESERVED FOR HISTORICAL RECORDS.  FOR THE CURRENT REGISTRY
PLEASE SEE: <http://www.iana.org/assignments/ipv6-unicast-address-assignments>

(last updated 24 February 2005)

TLA Identifier Assignments
--------------------------

TLA Identifiers are defined in [RFC2374] and are assigned from the Format
Prefix (FP) 001 (binary) in [RFC2373].

TLA ID assignments are listed below.

  IPv6 Prefix  FP   TLA Binary Value  TLA Hex  Assignment
  -----------  ---  ----------------  -------  ------------------
  2000::/16    001  0 0000 0000 0000  0x0000   Reserved
  2001::/16    001  0 0000 0000 0001  0x0001   Sub-TLA Assignments [RFC2450]
  2002::/16    001  0 0000 0000 0010  0x0002   "6to4" [RFC3056]
  2003::/16    001  0 0000 0000 0011  0x0003   Global Unicast [RFC3513]
  3FFE::/16    001  1 1111 1111 1110  0x1FFE   6bone Testing [RFC2471]
                                               To be phased out 6-Jun-2006 [RFC3701]  
  3FFF::/16    001  1 1111 1111 1111  0x1FFF   Reserved

  Note: Hex values are right justified. 

All TLA ID values not listed above are reserved.



Sub-TLA Identifier Assignments
------------------------------

Sub-TLA Identifiers are defined in [RFC2450] and are assigned out of
TLA ID 0x0001.  Note that use of the Reserved field to create the Sub-TLA
field is specific to TLA ID 0x0001.  It does not affect any other TLA ID.

| 3  |       13       |       13       |           19          |
+----+----------------+----------------+-----------------------+ . . .
| FP |      TLA       |    Sub-TLA     |           NLA         |
|    |      ID        |                |           ID          |
+----+----------------+----------------+-----------------------+ . . .
|001 |0 0000 0000 0001|xxxx xxxx xxxx x|xxx xxxx xxxx xxxx xxxx|


As specified in [RFC2450], Sub-TLA ID assignments are done in blocks.
The initial Sub-TLA ID assignments to IP address registries are in blocks
of 64 Sub-TLA IDs.  These assignments are listed below.

  IPv6 Prefix       sub-TLA Binary Values  Allocated to          Date 
  ---------------   ---------------------  -------------------   ------
  2001:0000::/23    0000 000X XXXX X       IANA                  Jul 99
  2001:0200::/23    0000 001X XXXX X       APNIC                 Jul 99
  2001:0400::/23    0000 010X XXXX X       ARIN                  Jul 99
  2001:0600::/23    0000 011X XXXX X       RIPE NCC              Jul 99
  2001:0800::/23    0000 100X XXXX X       RIPE NCC              May 02
  2001:0A00::/23    0000 101X XXXX X       RIPE NCC              Nov 02
  2001:0C00::/23    0000 110X XXXX X       APNIC **              May 02
  2001:0E00::/23    0000 111X XXXX X       APNIC                 Jan 03 
  2001:1000::/23    0001 000X XXXX X       (future assignment)
  2001:1200::/23    0001 001X XXXX X       LACNIC                Nov 02
  2001:1400::/23    0001 010X XXXX X       RIPE NCC              Feb 03
  2001:1600::/23    0001 011X XXXX X       RIPE NCC              Jul 03
  2001:1800::/23    0001 100X XXXX X       ARIN                  Apr 03
  2001:1A00::/23    0001 101X XXXX X       RIPE NCC              Jan 04
  2001:1C00::/23    0001 110X XXXX X       RIPE NCC              May 04
  2001:1E00::/23    0001 111X XXXX X       RIPE NCC              May 04
  2001:2000::/23    0010 000X XXXX X       RIPE NCC              May 04
  2001:2200::/23    0010 001X XXXX X       RIPE NCC              May 04
  2001:2400::/23    0010 010X XXXX X       RIPE NCC              May 04
  2001:2600::/23    0010 011X XXXX X       RIPE NCC              May 04
  2001:2800::/23    0010 100X XXXX X       RIPE NCC              May 04
  2001:2A00::/23    0010 101X XXXX X       RIPE NCC              May 04
  2001:2C00::/23    0010 110X XXXX X       RIPE NCC              May 04
  2001:2E00::/23    0010 111X XXXX X       RIPE NCC              May 04
  2001:3000::/23    0011 000X XXXX X       RIPE NCC              May 04
  2001:3200::/23    0011 001X XXXX X       RIPE NCC              May 04
  2001:3400::/23    0011 010X XXXX X       RIPE NCC              May 04
  2001:3600::/23    0011 011X XXXX X       RIPE NCC              May 04
  2001:3800::/23    0011 100X XXXX X       RIPE NCC              May 04
  2001:3A00::/23    0011 101X XXXX X       RIPE NCC              May 04
  2001:3C00::/23    0011 110X XXXX X       (reserved *)          Jun 04  
  2001:3E00::/23    0011 111X XXXX X       (reserved *)          Jun 04
  2001:4000::/23    0100 000X XXXX X       RIPE NCC              Jun 04
  2001:4200::/23    0100 001X XXXX X       ARIN                  Jun 04
  2001:4400::/23    0100 010X XXXX X       APNIC                 Jun 04
  2001:4600::/23    0100 011X XXXX X       RIPE NCC              Aug 04
  2001:4800::/23    0100 100X XXXX X       ARIN                  Aug 04
  2001:4A00::/23    0100 101X XXXX X       RIPE NCC              Oct 04
  2001:4C00::/23    0100 110X XXXX X       RIPE NCC              Dec 04
      .   .    . 
  2001:5000::/23    0101 000X XXXX X       RIPE NCC              Sep 04
  2001:5200::/23    0101 001X XXXX X       RIPE NCC              Sep 04
  2001:5400::/23    0101 010X XXXX X       RIPE NCC              Sep 04
  2001:5600::/23    0101 011X XXXX X       RIPE NCC              Sep 04
  2001:5800::/23    0101 100X XXXX X       RIPE NCC              Sep 04
  2001:5A00::/23    0101 101X XXXX X       RIPE NCC              Sep 04
  2001:5C00::/23    0101 110X XXXX X       RIPE NCC              Sep 04
  2001:5E00::/23    0101 111X XXXX X       RIPE NCC              Sep 04
      .   .    .
  2001:8000::/23    1000 000X XXXX X       APNIC                 Nov 04
  2001:8200::/23    1000 001X XXXX X       APNIC                 Nov 04
  2001:8400::/23    1000 010X XXXX X       APNIC                 Nov 04
  2001:8600::/23    1000 011X XXXX X       APNIC                 Nov 04
  2001:8800::/23    1000 100X XXXX X       APNIC                 Nov 04
  2001:8A00::/23    1000 101X XXXX X       APNIC                 Nov 04
  2001:8C00::/23    1000 110X XXXX X       APNIC                 Nov 04
  2001:8E00::/23    1000 111X XXXX X       APNIC                 Nov 04
  2001:9000::/23    1001 000X XXXX X       APNIC                 Nov 04
  2001:9200::/23    1001 001X XXXX X       APNIC                 Nov 04
  2001:9400::/23    1001 010X XXXX X       APNIC                 Nov 04
  2001:9600::/23    1001 011X XXXX X       APNIC                 Nov 04
  2001:9800::/23    1001 100X XXXX X       APNIC                 Nov 04
  2001:9A00::/23    1001 101X XXXX X       APNIC                 Nov 04
  2001:9C00::/23    1001 110X XXXX X       APNIC                 Nov 04
  2001:9E00::/23    1001 111X XXXX X       APNIC                 Nov 04
  2001:A000::/23    1010 000X XXXX X       APNIC                 Nov 04
  2001:A200::/23    1010 001X XXXX X       APNIC                 Nov 04
  2001:A400::/23    1010 010X XXXX X       APNIC                 Nov 04
  2001:A600::/23    1010 011X XXXX X       APNIC                 Nov 04
  2001:A800::/23    1010 100X XXXX X       APNIC                 Nov 04
  2001:AA00::/23    1010 101X XXXX X       APNIC                 Nov 04
  2001:AC00::/23    1010 110X XXXX X       APNIC                 Nov 04
  2001:AE00::/23    1010 111X XXXX X       APNIC                 Nov 04
      .   .    .
      .   .    .
      .   .    .
  2001:FE00::/23    1111 111X XXXX X       (future assignment)

   Where "X" indicates "0" or "1".


All other Sub-TLA ID values not listed above are reserved.

When an RIR is nearing complete allocation of all of the Sub-TLA IDs in its 
block(s), it can request that the IANA provide another block.  

The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:0000::/23
is for assignment for testing and experimental usage to support activities 
such as the 6bone, and for new approaches like exchanges.

*  For possible future allocation to RIPE NCC.

** Per [RFC3849], the 2001:DB8::/32 prefix has been assigned as 
   a NON-ROUTABLE range to be used for documentation purposes.  
   Please see the following for additional information:
   http://www.apnic.net/info/faq/ipv6-documentation-prefix-faq.html



Global Unicast Prefix  Assignment     Date        Note
---------------------  ----------     ---------   ----
2003:0000::/18         RIPE NCC       12 Jan 05   

  
 
References
----------

[RFC2471]   Hinden, R., R. Fink, J. Postel, "IPv6 Testing Address
            Allocation", RFC2471, December 1998.

[RFC2373]   Hinden, R., "IP Version 6 Addressing Architecture",
            RFC2373, July 1998.

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

[RFC2450]   Hinden, R., "Proposed TLA and NLA Assignment Rules",
            RFC2450, December 1998.

[RFC3056]   Carpenter, B., K. Moore, "Connection of IPv6 Domains via IPv4
            Clouds without Explicit Tunnels", RFC 3056, February 2001.

[RFC3513]   R. Hinden and S. Deering, "Internet Protocol Version 6 (IPv6) 
            Addressing Architecture", RFC 3513,  April 2003.

[RFC3701]   Fink, R., "6Bone (IPv6 Testing Address Allocation) Phaseout",
            RFC 3701, March 2004.

[RFC3849]   G. Huston, A. Lord, and P. Smith, "IPv6 Address Prefix 
            Reserved for Documentation", RFC 3849, July 2004.

[RFC4147]   G. Huston, "Proposed changes to the format of the IANA IPv6 Registry",
            RFC 4147, August 2005.

[]