1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
IPV6 TOP LEVEL AGGREGATION IDENTIFIER ASSIGNMENTS
(last updated 2003-04-05)
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]
3FFE::/16 001 1 1111 1111 1110 0x1FFE 6bone Testing [RFC2471]
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 (future assignment)
2001:1800::/23 0001 100X XXXX X ARIN Apr 03
. . .
. . .
. . .
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.
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.
[]
|
