idnits 2.17.1 draft-ietf-ipngwg-iana-tla-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 7 instances of too long lines in the document, the longest one being 4 characters in excess of 72. == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2119' is mentioned on line 56, but not defined == Unused Reference: 'IPV6' is defined on line 177, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 180, but no explicit reference was found in the text == Unused Reference: 'TST-ALLOC' is defined on line 189, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2374 (ref. 'AGGR') (Obsoleted by RFC 3587) ** Downref: Normative reference to an Informational RFC: RFC 1881 (ref. 'ALLOC') ** Obsolete normative reference: RFC 2373 (ref. 'ARCH') (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 2402 (ref. 'AUTH') (Obsoleted by RFC 4302, RFC 4305) ** Obsolete normative reference: RFC 2460 (ref. 'IPV6') (Obsoleted by RFC 8200) ** Downref: Normative reference to an Informational RFC: RFC 2450 (ref. 'TLA-RULES') ** Obsolete normative reference: RFC 2471 (ref. 'TST-ALLOC') (Obsoleted by RFC 3701) Summary: 12 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT R. Hinden, Nokia 2 January 13, 2000 S. Deering, Cisco 3 R. Fink, LBNL 4 T. Hain, Microsoft 6 Initial IPv6 Sub-TLA ID Assignments 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of [RFC2026]. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This internet draft expires on July 13, 2000. 33 1.0 Introduction 35 This document defines initial assignments of IPv6 Sub-TLA Aggregation 36 Identifiers (Sub-TLA ID) to the Address Registries. It is intended 37 as technical input to the IANA from the IETF IP Next Generation 38 (IPNG) and Next Generation Transition (NGTRANS) working groups, as an 39 input to the process of developing guidelines for the allocation of 40 IPv6 addresses. 42 The IAB and IESG have authorized the Internet Assigned Numbers 43 Authority (IANA) as the appropriate entity to have the responsibility 44 for the management of the IPv6 address space as defined in [ALLOC]. 46 The proposed initial assignment described in the document is 47 consistent with: 49 - RFC 2373,"IP Version 6 Addressing Architecture" [ARCH] 50 - RFC 2374 "An Aggregatable Global Unicast Address Format" [AGGR] 51 - RFC 2450 "Proposed TLA and NLA Assignment Rules" [TLA-RULES] 53 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 54 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 55 document are to be interpreted as described in [RFC 2119]. 57 2.0 Background 59 [TLA-RULES] specifies that TLA assignments will be done in two 60 stages. The first stage is to allocate a Sub-TLA ID. This document 61 specifies the initial assignments of Sub-TLA ID's to the Registries. 63 As defined in [TLA-RULES] Section 5.1: 65 "Sub-TLA ID's are assigned out of TLA ID 0x0001 as follows. Note 66 that use of the Reserved field to create the Sub-TLA field is 67 specific to TLA ID 0x0001. It does not affect any other TLA. 69 | 3 | 13 | 13 | 19 | 70 +----+----------+---------+---------------+ 71 | FP | TLA | Sub-TLA | NLA | 72 | | ID | | ID | 73 +----+----------+---------+---------------+ 75 where: 77 FP = 001 = Format Prefix 79 This is the Format Prefix used to identify aggregatable global 80 unicast addresses. 82 TLA ID = 0x0001 = Top-Level Aggregation Identifier 84 This is the TLA ID assigned by the IANA for Sub-TLA 85 allocation. 87 Sub-TLA ID = Sub-TLA Aggregation Identifier 89 The Sub-TLA ID field is used by the registries for initial 90 allocations to organizations meeting the requirements in 91 Section 5.2 of this document. The IANA will assign small 92 blocks (e.g., few hundred) of Sub-TLA ID's to registries. The 93 registries will assign the Sub-TLA ID's to organizations 94 meeting the requirements specified in Section 5.2. When the 95 registries have assigned all of their Sub-TLA ID's they can 96 request that the IANA give them another block. The blocks do 97 not have to be contiguous. The IANA may also assign Sub-TLA 98 ID's to organizations directly. This includes the temporary 99 TLA assignment for testing and experimental usage for 100 activities such as the 6bone or new approaches like exchanges. 102 NLA ID = Next-Level Aggregation Identifier 104 Next-Level Aggregation ID's are used by organizations assigned 105 a TLA ID to create an addressing hierarchy and to identify 106 sites. The organization can assign the top part of the NLA ID 107 in a manner to create an addressing hierarchy appropriate to 108 its network." 110 Note: In the above quote from [TLA-RULES] the references to "Section 111 5.2" refer to section 5.2 in [TLA-RULES]. 113 3.0 Initial Assignments 115 As specified in [TLA-RULES], Sub-TLA ID assignments are made in 116 blocks. The initial Sub-TLA ID assignments to IP address registries 117 are in blocks of 64 Sub-TLA IDs. These assignments are listed below. 119 Binary Value IPv6 Prefix Range Assignment 120 ---------------- ------------------------------- ------------------- 122 0000 000X XXXX X 2001:0000::/29 - 2001:01F8::/29 IANA 123 0000 001X XXXX X 2001:0200::/29 - 2001:03F8::/29 APNIC 124 0000 010X XXXX X 2001:0400::/29 - 2001:05F8::/29 ARIN 125 0000 011X XXXX X 2001:0600::/29 - 2001:07F8::/29 RIPE NCC 126 0000 100X XXXX X 2001:0800::/29 - 2001:09F8::/29 (future assignment) 127 0000 101X XXXX X 2001:0A00::/29 - 2001:0BF8::/29 (future assignment) 128 0000 110X XXXX X 2001:0C00::/29 - 2001:0DF8::/29 (future assignment) 129 0000 111X XXXX X 2001:0E00::/29 - 2001:0FF8::/29 (future assignment) 130 0001 000X XXXX X 2001:1000::/29 - 2001:11F8::/29 (future assignment) 131 . . . 132 . . . 133 . . . 134 1111 111X XXXX X 2001:FE00::/29 - 2001:FFF8::/29 (future assignment) 136 Where "X" indicates "0" or "1". 138 All other Sub-TLA ID values not listed above are reserved. 140 When a registry has assigned all of the Sub-TLA IDs in their block 141 they can request that the IANA provide another block. The blocks 142 assigned to a registry do not have to be contiguous. 144 The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:0000::/29 - 145 2001:01F8::/29) is for assignment for testing and experimental usage 146 to support activities such as the 6bone, and for new approaches like 147 exchanges. 149 4.0 Acknowledgments 151 The authors would like to express their thanks to Joyce Reynolds, 152 Thomas Narten, Kim Hubbard, Mirjam Kuehne, and Brian Carpenter for 153 their help with this document. 155 5.0 Security Considerations 157 IPv6 addressing documents do not have any direct impact on Internet 158 infrastructure security. Authentication of IPv6 packets is defined 159 in [AUTH]. Authentication of the ownership of prefixes to avoid 160 "prefix stealing" is a related security issue but is beyond the scope 161 of this document. 163 6.0 References 165 [AGGR] Hinden, R., Deering, S., O'Dell, M., "An Aggregatable 166 Global Unicast Address Format", RFC2374, July 1998. 168 [ALLOC] IAB and IESG, "IPv6 Address Allocation Management", 169 RFC1881, December 1995. 171 [ARCH] Hinden, R., "IP Version 6 Addressing Architecture", 172 RFC2373, July 1998. 174 [AUTH] Kent, S., R. Atkinson, "IP Authentication Header", 175 RFC2402, November 1998. 177 [IPV6] Deering, S., R. Hinden, "Internet Protocol, Version 6 178 (IPv6) Specification", RFC2460, December 1998. 180 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 181 Requirement Levels", RFC2119, BCP14, March 1997. 183 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 184 3", RFC2026, BCP00009, October 1996. 186 [TLA-RULES] Hinden, R., "Proposed TLA and NLA Assignment Rules", 187 RFC2450, December 1998. 189 [TST-ALLOC] Hinden, R., R. Fink, J. Postel, "IPv6 Testing Address 190 Allocation", RFC2471, December 1998. 192 7.0 Authors' Addresses 194 Robert M. Hinden phone: +1 650 625-2004 195 Nokia email: hinden@iprg.nokia.com 196 313 Fairchild Drive 197 Mountain View, CA 94043 198 USA 200 Stephen E. Deering phone: +1 408 527-8213 201 Cisco Systems, Inc. email: deering@cisco.com 202 170 West Tasman Drive 203 San Jose, CA 95134-1706 204 USA 206 Robert L. Fink phone: +1 510 486-5692 207 Lawrence Berkeley National Lab email: rlfink@lbl.gov 208 1 Cyclotron Rd. 209 Bldg 50A, Room 3111 210 Berkeley, CA 94720 211 USA 213 Tony Hain phone: +1 425 703-6619 214 Microsoft email: tonyhain@microsoft.com