As per Relevance of the word assigned, we have this rfc below:
Network Working Group R.
Request for Comments: 2928
Category: Informational S.
R.
T.
September 2000
Initial IPv6 Sub-TLA ID
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document defines initial assignments of IPv6 Sub-Top-
Aggregation Identifiers (Sub-TLA ID) to the Address Registries.
is intended as technical input to the Internet Assigned
Authority (IANA) from the Internet Engineering Task Force (IETF
Internet Protocol Next Generation (IPNG) and Next
Transition (NGTRANS) working groups, as an input to the process
developing guidelines for the allocation of IPv6 addresses
This document was originally developed to provide advice to IANA
the fall of 1998 and is being published at this time for
historical record. The Internet Architecture Board (IAB
subsequently requested that the IANA delegate these assignments
the Address Registries. The IANA did this and the Address
are now using them to assign IPv6 addresses
1.
This document was originally developed to provide advice to IANA
the fall of 1998 and is being published at this time for
historical record. The IAB subsequently requested that the
delegate these assignments to the Address Registries. The IANA
this and the Address Registries are now using them to assign IPv
addresses
Hinden, et al. Informational [Page 1]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
This document defines initial assignments of IPv6 Sub-TLA
Identifiers (Sub-TLA ID) to the Address Registries. It is
as technical input to the IANA from the IETF IP Next
(IPNG) and Next Generation Transition (NGTRANS) working groups, as
input to the process of developing guidelines for the allocation
IPv6 addresses
The IAB and IESG have authorized the Internet Assigned
Authority (IANA) as the appropriate entity to have the
for the management of the IPv6 address space as defined in [ALLOC].
The proposed initial assignment described in the document
consistent with
- RFC 2373,"IP Version 6 Addressing Architecture" [ARCH
- RFC 2374 "An Aggregatable Global Unicast Address Format" [AGGR
- RFC 2450 "Proposed TLA and NLA Assignment Rules" [TLA-RULES
2.
[TLA-RULES] specifies that TLA assignments will be done in
stages. The first stage is to allocate a Sub-TLA ID. This
specifies the initial assignments of Sub-TLA ID's to the Registries
As defined in [TLA-RULES] Section 5.1:
"Sub-TLA ID's are assigned out of TLA ID 0x0001 as follows.
that use of the Reserved field to create the Sub-TLA field
specific to TLA ID 0x0001. It does not affect any other TLA
| 3 | 13 | 13 | 19 |
+----+----------+---------+---------------+
| FP | TLA | Sub-TLA | NLA |
| | ID | | ID |
+----+----------+---------+---------------+
where
FP = 001 = Format
This is the Format Prefix used to identify aggregatable
unicast addresses
TLA ID = 0x0001 = Top-Level Aggregation
This is the TLA ID assigned by the IANA for Sub-
allocation
Hinden, et al. Informational [Page 2]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
Sub-TLA ID = Sub-TLA Aggregation
The Sub-TLA ID field is used by the registries for
allocations to organizations meeting the requirements
Section 5.2 of this document. The IANA will assign
blocks (e.g., few hundred) of Sub-TLA ID's to registries.
registries will assign the Sub-TLA ID's to
meeting the requirements specified in Section 5.2. When
registries have assigned all of their Sub-TLA ID's they
request that the IANA give them another block. The blocks
not have to be contiguous. The IANA may also assign Sub-
ID's to organizations directly. This includes the
TLA assignment for testing and experimental usage
activities such as the 6bone or new approaches like exchanges
NLA ID = Next-Level Aggregation
Next-Level Aggregation ID's are used by organizations
a TLA ID to create an addressing hierarchy and to
sites. The organization can assign the top part of the NLA
in a manner to create an addressing hierarchy appropriate
its network."
Note: In the above quote from [TLA-RULES] the references to "
5.2" refer to section 5.2 in [TLA-RULES].
Hinden, et al. Informational [Page 3]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
3. Initial
As specified in [TLA-RULES], Sub-TLA ID assignments are made
blocks. The initial Sub-TLA ID assignments to IP address
are in blocks of 64 Sub-TLA IDs. These assignments are listed below
Binary Value IPv6 Prefix Range
---------------- ------------------------------- -------------------
0000 000X XXXX X 2001:0000::/29 - 2001:01F8::/29
0000 001X XXXX X 2001:0200::/29 - 2001:03F8::/29
0000 010X XXXX X 2001:0400::/29 - 2001:05F8::/29
0000 011X XXXX X 2001:0600::/29 - 2001:07F8::/29 RIPE
0000 100X XXXX X 2001:0800::/29 - 2001:09F8::/29 (future assignment
0000 101X XXXX X 2001:0A00::/29 - 2001:0BF8::/29 (future assignment
0000 110X XXXX X 2001:0C00::/29 - 2001:0DF8::/29 (future assignment
0000 111X XXXX X 2001:0E00::/29 - 2001:0FF8::/29 (future assignment
0001 000X XXXX X 2001:1000::/29 - 2001:11F8::/29 (future assignment
. . .
. . .
. . .
1111 111X XXXX X 2001:FE00::/29 - 2001:FFF8::/29 (future assignment
Where "X" indicates "0" or "1".
All other Sub-TLA ID values not listed above are reserved
When a registry has assigned all of the Sub-TLA IDs in their
they can request that the IANA provide another block. The
assigned to a registry do not have to be contiguous
The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:0000::/29 -
2001:01F8::/29) is for assignment for testing and experimental
to support activities such as the 6bone, and for new approaches
exchanges
4.
The authors would like to express their thanks to Joyce K. Reynolds
Thomas Narten, Kim Hubbard, Mirjam Kuehne, and Brian Carpenter
their help with this document
5. Security
IPv6 addressing documents do not have any direct impact on
infrastructure security. Authentication of IPv6 packets is
in [AUTH]. Authentication of the ownership of prefixes to
"prefix stealing" is a related security issue but is beyond the
of this document
Hinden, et al. Informational [Page 4]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
6.
[AGGR] Hinden, R., Deering, S. and M. O'Dell, "An
Global Unicast Address Format", RFC 2374, July 1998.
[ALLOC] IAB and IESG, "IPv6 Address Allocation Management",
1881, December 1995.
[ARCH] Hinden, R., "IP Version 6 Addressing Architecture",
2373, July 1998.
[AUTH] Kent, S. and R. Atkinson, "IP Authentication Header",
2402, November 1998.
[IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC2026] Bradner, S., "The Internet Standards Process --
3", BCP 9, RFC 2026, October 1996.
[TLA-RULES] Hinden, R., "Proposed TLA and NLA Assignment Rules",
2450, December 1998.
[TST-ALLOC] Hinden, R., Fink R. and J. Postel, "IPv6 Testing
Allocation", RFC 2471, December 1998.
Hinden, et al. Informational [Page 5]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
7. Authors'
Robert M.
313 Fairchild
Mountain View, CA 94043
Phone: +1 650 625-2004
EMail: hinden@iprg.nokia.
Stephen E.
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134-1706
Phone: +1 408 527-8213
EMail: deering@cisco.
Robert L.
Lawrence Berkeley National
1 Cyclotron Rd
Bldg 50A, Room 3111
Berkeley, CA 94720
Phone: +1 510 486-5692
EMail: rlfink@lbl.
Tony
Phone: +1 425 703-6619
EMail: tonyhain@microsoft.
Hinden, et al. Informational [Page 6]
RFC 2928 Initial IPv6 Sub-TLA ID Assignments September 2000
8. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Hinden, et al. Informational [Page 7]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
