idnits 2.17.1 draft-ietf-mpls-tp-ach-tlv-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 5, 2010) is 5164 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 2460 (ref. '3') (Obsoleted by RFC 8200) -- Possible downref: Non-RFC (?) normative reference: ref. '4' == Outdated reference: A later version (-07) exists of draft-ietf-mpls-tp-identifiers-00 == Outdated reference: A later version (-12) exists of draft-ietf-mpls-tp-framework-10 Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS S. Boutros 3 Internet-Draft S. Bryant, Ed. 4 Intended status: Standards Track S. Sivabalan 5 Expires: September 6, 2010 G . Swallow 6 Cisco Systems 7 D. Ward 8 Juniper Networks 9 V. Manral 10 IP Infusion Inc. 11 March 5, 2010 13 Definition of ACH TLV Structure 14 draft-ietf-mpls-tp-ach-tlv-02 16 Abstract 18 In some application of the associated channel header (ACH), it is 19 necessary to have the ability to include a set of TLVs to provide 20 additional context information for the ACH payload. This document 21 defines a number of TLV types. 23 This document is a product of a joint Internet Engineering Task Force 24 (IETF) / International Telecommunications Union Telecommunications 25 Standardization Sector (ITU-T) effort to include an MPLS Transport 26 Profile within the IETF MPLS and PWE3 architectures to support the 27 capabilities and functionalities of a packet transport network as 28 defined by the ITU-T. 30 Requirements Language 32 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 33 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 34 document are to be interpreted as described in RFC2119 [1]. 36 Status of this Memo 38 This Internet-Draft is submitted to IETF in full conformance with the 39 provisions of BCP 78 and BCP 79. 41 Internet-Drafts are working documents of the Internet Engineering 42 Task Force (IETF), its areas, and its working groups. Note that 43 other groups may also distribute working documents as Internet- 44 Drafts. 46 Internet-Drafts are draft documents valid for a maximum of six months 47 and may be updated, replaced, or obsoleted by other documents at any 48 time. It is inappropriate to use Internet-Drafts as reference 49 material or to cite them other than as "work in progress." 51 The list of current Internet-Drafts can be accessed at 52 http://www.ietf.org/ietf/1id-abstracts.txt. 54 The list of Internet-Draft Shadow Directories can be accessed at 55 http://www.ietf.org/shadow.html. 57 This Internet-Draft will expire on September 6, 2010. 59 Copyright Notice 61 Copyright (c) 2010 IETF Trust and the persons identified as the 62 document authors. All rights reserved. 64 This document is subject to BCP 78 and the IETF Trust's Legal 65 Provisions Relating to IETF Documents 66 (http://trustee.ietf.org/license-info) in effect on the date of 67 publication of this document. Please review these documents 68 carefully, as they describe your rights and restrictions with respect 69 to this document. Code Components extracted from this document must 70 include Simplified BSD License text as described in Section 4.e of 71 the Trust Legal Provisions and are provided without warranty as 72 described in the BSD License. 74 Table of Contents 76 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 2. ACH TLV Object Definitions . . . . . . . . . . . . . . . . . . 4 78 2.1. The Null TLV Object . . . . . . . . . . . . . . . . . . . . 4 79 2.2. IPv4 Source Address . . . . . . . . . . . . . . . . . . . . 4 80 2.3. IPv6 Source Address . . . . . . . . . . . . . . . . . . . . 5 81 2.4. ITU-T Carrier Code . . . . . . . . . . . . . . . . . . . . 5 82 2.5. Global Identifier . . . . . . . . . . . . . . . . . . . . . 6 83 2.6. Network Interface Identifier . . . . . . . . . . . . . . . 6 84 2.7. Authentication . . . . . . . . . . . . . . . . . . . . . . 7 85 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 86 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 87 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 88 5.1. Normative References . . . . . . . . . . . . . . . . . . . 8 89 5.2. Informative References . . . . . . . . . . . . . . . . . . 8 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 92 1. Introduction 94 The MPLS generic associated channel header specification [6] (GACH) 95 describes a TLV structure that is used to provide additional context 96 information for the ACH payload. This document defines a number of 97 TLVs that are required by the MPLS-TP design [7], [8]. 99 2. ACH TLV Object Definitions 101 This section provides the definition for a number of ACH TLV objects. 102 In each case the length in the TLV header is the length of only the 103 value component. 105 2.1. The Null TLV Object 107 The Null TLV provides an OPTIONAL mechanism of restoring 32bit 108 alignment of the following element in the packet and also provides an 109 OPTIONAL mechanism to reserve space in the packet to be used by TLV 110 objects that will be written by LSR that perform some operation on 111 the packet at a later time. For security reasons the value must be 112 zero. 114 0 1 2 3 115 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | AchTlvType = 0 | Length | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 ~ Value = 0 ~ 120 | | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 Figure 1: Null TLV Object 125 2.2. IPv4 Source Address 127 This TLV specifies the IPv4 [2] source address (SAv4) of an ACH 128 packet. 130 Where the packet is associated with a maintenance request/response 131 operation it refers to the requester of the operation, i.e. It is 132 the address of the Maintenance End Point that initiated the operation 133 being either requested, or is being responded to. 135 0 1 2 3 136 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | AchTlvType = 1 | Length = 4 | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | IPv4 Address | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 Figure 2: IPv4 Source Address 145 2.3. IPv6 Source Address 147 This TLV specifies the IPv6 [3] source address (SAv6) of an ACH 148 packet. 150 Where the packet is associated with a maintenance request/response 151 operation it refers to the requester of the operation, i.e. It is 152 the address of the Maintenance End Point that initiated the operation 153 being either requested, or is being responded to. 155 0 1 2 3 156 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | AchTlvType = 2 | Length = 16 | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 ~ IPv6 Address | 161 | | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 Figure 3: IPv4 Source Address 166 2.4. ITU-T Carrier Code 168 This TLV is used to carry an ITU-T Carrier Code Identifier (ICC) as 169 defined in M.1400 [4]. 171 0 1 2 3 172 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 | AchTlvType = 3 | Length = 16 | 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 | ICC | 177 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 Figure 4: ITU-T Carrier Code 183 The ICC is encoded in ASCII in a fixed format 6 byte field, with 184 unused trailing bytes set to NULL (0). 186 2.5. Global Identifier 188 This TLV is used to carry a Global Identifier (Global_ID) [5] . 190 0 1 2 3 191 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | AchTlvType = 4 | Length = 4 | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Global ID | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Figure 5: Global_ID TLV 200 2.6. Network Interface Identifier 202 This TLV is used to carry Network Interface ID (IF_ID) [5] . As 203 defined in [5], an IF_ID consists of a node identifier (Node_ID) and 204 a Logical Interface Handle (LIH), both or which are 32 bit 205 identifiers. 207 0 1 2 3 208 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | AchTlvType = 5 | Length = 8 | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | Node_ID | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | LIH | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 Figure 6: IF_ID TLV 219 2.7. Authentication 221 The structure of the ACH authentication (auth) TLV is as follows: 222 0 1 2 3 223 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 | AchTlvType = 6 | Length | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 | Auth Type | Auth Len | Authentication Data... | 228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 The authentication proceedures and data format used is the same as 231 that defined in Sections 4.1, 4.2, 4.3 and 4.4 of [9] . 233 Each document which defines a channel type needs to define whether an 234 authentication TLV is required, permitted, or disallowed, and the 235 actions to be taken in normal and error situations. 237 An application not supporting data origin authentication MAY use this 238 mechanism instead of defining its own proprietery mechanism. 240 3. Security Considerations 242 This specification defines a mechanism to identify a set of protocol 243 parameters. The necessary security considerations will be described 244 in the definition of the protocols that uses these parameters. 246 4. IANA Considerations 248 IANA is requested to create a new registry in the pseudowire name 249 spaces: the ACH TLV Registry. 251 The ACH TLV Registry should be initialized with the following 252 entries. The allocation policy for this registry is IETF consensus. 254 Name Type Length Description Reference 255 (octets) 256 Null 0 3 Null TLV This Draft 257 SAv4 1 4 IPv4 Source Address This Draft 258 SAv6 2 16 IPv6 Source Address This Draft 259 ICC 3 6 ITU-T Carrier Code This Draft 260 Global_ID 4 4 Global Identifier This Draft 261 IF_ID 5 8 Network Interface ID This Draft 262 Auth 6 var Authentication This Draft 264 5. References 266 5.1. Normative References 268 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 269 Levels", BCP 14, RFC 2119, March 1997. 271 [2] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981. 273 [3] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) 274 Specification", RFC 2460, December 1998. 276 [4] "ITU-T Recommendation M.1400, "Designations for interconnections 277 among operators' networks"", 2006. 279 [5] Bocci, M. and G. Swallow, "MPLS-TP Identifiers", 280 draft-ietf-mpls-tp-identifiers-00 (work in progress), 281 November 2009. 283 5.2. Informative References 285 [6] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic 286 Associated Channel", RFC 5586, June 2009. 288 [7] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and S. 289 Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, 290 September 2009. 292 [8] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, "A 293 Framework for MPLS in Transport Networks", 294 draft-ietf-mpls-tp-framework-10 (work in progress), 295 February 2010. 297 [9] Katz, D. and D. Ward, "Bidirectional Forwarding Detection", 298 draft-ietf-bfd-base-11 (work in progress), January 2010. 300 Authors' Addresses 302 Sami Boutros 303 Cisco Systems 305 Email: sboutros@cisco.com 307 Stewart Bryant (editor) 308 Cisco Systems 310 Email: stbryant@cisco.com 312 Siva Sivabalan 313 Cisco Systems 315 Email: msiva@cisco.com 317 George Swallow 318 Cisco Systems 320 Email: swallow@cisco.com 322 David Ward 323 Juniper Networks 325 Email: dward@Juniper.net 327 Vishwas Manral 328 IP Infusion Inc. 329 Bamankhola, 330 Bansgali,, Almora, Uttaranchal 263601 331 India 333 Email: vishwas.ietf@gmail.com