idnits 2.17.1 draft-asati-pignataro-mpls-ldp-iana-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 11, 2011) is 4785 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group C. Pignataro 3 Internet-Draft R. Asati 4 Intended status: Standards Track Cisco Systems 5 Expires: September 12, 2011 March 11, 2011 7 Label Distribution Protocol (LDP) Internet Assigned Numbers Authority 8 (IANA) Considerations Update 9 draft-asati-pignataro-mpls-ldp-iana-01 11 Abstract 13 This document augments the Internet Assigned Numbers Authority (IANA) 14 considerations for the Label Distribution Protocol (LDP), for 15 protocol fields that are Reserved in the LDP Specification but for 16 which there are no IANA allocation policies. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 12, 2011. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 54 2.1. ATM Label TLV . . . . . . . . . . . . . . . . . . . . . . . 3 55 2.2. Frame Relay Label TLV . . . . . . . . . . . . . . . . . . . 3 56 2.3. Common Hello Parameters TLV . . . . . . . . . . . . . . . . 4 57 2.4. Common Session Parameters TLV . . . . . . . . . . . . . . . 4 58 2.5. ATM Session Parameters TLV . . . . . . . . . . . . . . . . 4 59 2.6. Frame Relay Session Parameters TLV . . . . . . . . . . . . 4 60 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 61 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. Normative References . . . . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 LDP [RFC5036] specifies a number of Reserved fields in various 68 protocol elements, without establishing an allocation policy for 69 them. This document describes updates to the IANA Considerations for 70 LDP, for the following LDP TLVs: 72 o ATM Label TLV 74 o Frame Relay Label TLV 76 o Common Hello Parameters TLV 78 o Common Session Parameters TLV 80 o ATM Session Parameters TLV 82 o Frame Relay Session Parameters TLV 84 All Reserved bit-fields mentioned specifically in this document are 85 set to zero on transmission and ignored on receipt, therefore 86 protecting backwards compatibility. 88 2. IANA Considerations 90 IANA is requested to add the Registration Procedures for the LDP 91 fields as specified in the upcoming sections. All other LDP IANA 92 Registration Procedures are to remain unmodified. 94 2.1. ATM Label TLV 96 There are two Reserved bits in the ATM Label TLV (see Section 3.4.2.2 97 of [RFC5036]). Allocations from these bits are made via IETF Review 98 [RFC5226]. Previously, there was no rule for allocation of these 99 bits. 101 2.2. Frame Relay Label TLV 103 There are seven Reserved bits in the Frame Relay Label TLV (see 104 Section 3.4.2.3 of [RFC5036]). Allocations from these bits are made 105 via IETF Review [RFC5226]. Previously, there was no rule for 106 allocation of these bits. 108 Additionally, Section 3.4.2.3 of [RFC5036] also defines values 0 and 109 2 for the "Len" field. "Len" values 1 and 3 are available for 110 assignment via IETF Review [RFC5226]. Previously, there was no rule 111 for allocation of these values. 113 2.3. Common Hello Parameters TLV 115 There are fourteen Reserved bits in the Common Hello Parameters TLV 116 (see Section 3.5.2 of [RFC5036]). Allocations from these bits are 117 made via IETF Review [RFC5226]. Previously, there was no rule for 118 allocation of these bits. 120 2.4. Common Session Parameters TLV 122 There are six Reserved bits in the Common Session Parameters TLV (see 123 Section 3.5.3 of [RFC5036]). Allocations from these bits are made 124 via IETF Review [RFC5226]. Previously, there was no rule for 125 allocation of these bits. 127 2.5. ATM Session Parameters TLV 129 Within the ATM Session Parameters TLV, there are twenty five Reserved 130 bits in the header, and eight Reserved bits in the ATM Label Range 131 Component (see Section 3.5.3 of [RFC5036]). Allocations from these 132 bits are made via IETF Review [RFC5226]. Previously, there was no 133 rule for allocation of these bits. 135 2.6. Frame Relay Session Parameters TLV 137 Within the Frame Relay Session Parameters TLV, there are twenty five 138 Reserved bits in the header, and sixteen Reserved bits in the Frame 139 Relay Label Range Component (see Section 3.5.3 of [RFC5036]). 140 Allocations from these bits are made via IETF Review [RFC5226]. 141 Previously, there was no rule for allocation of these bits. 143 Additionally, Section 3.5.3 of [RFC5036] also defines values 0 and 2 144 for the "Len" field. "Len" values 1 and 3 are available for 145 assignment via IETF Review [RFC5226]. Previously, there was no rule 146 for allocation of these values. These values are common with those 147 of Section 2.2. 149 3. Security Considerations 151 This document does not modify the security properties for LDP. 153 4. Acknowledgments 155 The authors wish to thank Adrian Farrel and Loa Andersson for their 156 valuable comments. 158 5. Normative References 160 [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP 161 Specification", RFC 5036, October 2007. 163 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 164 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 165 May 2008. 167 Authors' Addresses 169 Carlos Pignataro 170 Cisco Systems 171 7200-12 Kit Creek Road 172 Research Triangle Park, NC 27709 173 US 175 Email: cpignata@cisco.com 177 Rajiv Asati 178 Cisco Systems 179 7025-6 Kit Creek Road 180 Research Triangle Park, NC 27709 181 US 183 Email: rajiva@cisco.com