idnits 2.17.1 draft-ietf-teas-gmpls-scsi-04.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 (August 30, 2017) is 2431 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) -- Looks like a reference, but probably isn't: '1' on line 282 == Missing Reference: 'This ID' is mentioned on line 195, but not defined == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-ospf-availability-extension-10 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TEAS Working Group D. Ceccarelli 3 Internet-Draft Ericsson 4 Intended status: Standards Track L. Berger 5 Expires: March 3, 2018 LabN Consulting, L.L.C. 6 August 30, 2017 8 Generalized Interface Switching Capability Descriptor - Switching 9 Capability Specific Information 10 draft-ietf-teas-gmpls-scsi-04 12 Abstract 14 This document defines a generic information structure for information 15 carried in routing protocol Interface Switching Capability Descriptor 16 (ISCD) Switching Capability Specific Information (SCSI) fields. This 17 "Generalized SCSI" can be used with routing protocols that define 18 GMPLS ISCDs, and any specific technology. This document does not 19 modify any existing technology specific formats and is defined for 20 use in conjunction with new GMPLS Switching Capability types. The 21 context for this document is Generalized MPLS, and the reader is 22 expected to be familiar with the GMPLS architecture and associate 23 protocol standards. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on March 3, 2018. 42 Copyright Notice 44 Copyright (c) 2017 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Generalized SCSI Formats . . . . . . . . . . . . . . . . . . 3 62 4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 64 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 65 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 68 8.2. Informative References . . . . . . . . . . . . . . . . . 6 69 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 72 1. Introduction 74 The context for this document is Generalized MPLS, and the reader is 75 expected to be familiar with the GMPLS architecture, associate 76 terminology and protocol standards. Notably, but not limited to, 77 [RFC3945], [RFC4202], [RFC4203] and [RFC5307]. 79 The Interface Switching Capability Descriptor (ISCD) [RFC4202] allows 80 routing protocols such as OSPF and ISIS to carry technology specific 81 information in the the Switching Capability-specific information 82 (SCSI) field, see [RFC4203] and [RFC5307]. The format of an SCSI 83 field is dictated by the specific technology being represented as 84 indicated by the ISCD Switching Capability (SC) type field. Existing 85 Switching Capabilities are managed by IANA in the Switching Types 86 registry [1] and the related "IANA-GMPLS-TC-MIB" definitions. 88 [RFC7138] introduced a "sub-TLV" structure to its technology specific 89 SCSI field. The Sub-Type-Length-Value (TLV) based approach allows 90 for greater flexibility in the structure, ordering, and ability to 91 support extensions of the SC (technology) specific format. This Sub- 92 TLV approach is also used in [RFC7688]. 94 This document generalizes this approach and defines a new generalized 95 SCSI field format for use by future specific technologies and 96 Switching Capability types. The generalized SCSI carries SCSI-TLVs 97 that may be defined within the scope of a specific technology, or 98 shared across multiple technologies (e.g., 99 [I-D.ietf-ccamp-ospf-availability-extension]). This document also 100 establishes a registry for SCSI-TLV definitions that may be shared 101 across multiple technologies. 103 2. Terminology 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 107 "OPTIONAL" in this document are to be interpreted as described in 108 [RFC2119]. 110 The reader is expected to be familiar with GMPLS terminology, e.g. as 111 found in [RFC3945], as well as the terminology used in [RFC4202], 112 [RFC4203] and [RFC5307]. 114 3. Generalized SCSI Formats 116 The Generalized SCSI is composed of zero or more variable length 117 type-length-value fields which are each called a SCSI-TLV. There are 118 no specific size restrictions on these SCSI-TLV. Size and other 119 formatting restrictions may be imposed by the routing protocol ISCD 120 field, refer to [RFC4203] and [RFC5307]. Please also refer to 121 [RFC3630] for the treatment of malformed Link TLVs. 123 The SCSI-TLV format is: 125 0 1 2 3 126 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 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | Type | Length | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 ... Value ... 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 Figure 1: TLV format 135 Type (2 octets): 136 This field indicates the type and structure of the information 137 contained in the Value field. 139 Length (2 octets): 140 This field MUST be set to the size, in octets (bytes), of the 141 Value field. The value of the field MUST be zero or divisible by 142 4. Note that this implies that the Value field can be omitted or 143 contain padding. 145 Value (variable): 146 A variable length field, formatted according to the definition 147 indicated by value of the Type field. This field can be omitted 148 for certain types. 150 4. Procedures 152 The ISCD can include a Generalized SCSI when advertising technologies 153 whose Switching Capability definition references this document. The 154 corollary of this is that the Generalized SCSI MUST NOT be used for 155 ISCDs of technologies whose Switching Capability definition do not 156 reference this document. 158 The Generalized SCSI MAY contain a sequence of zero or more SCSI- 159 TLVs. Sub-TLV parsing (format) errors, such as an underrun or 160 overrun, MUST be treated as a malformed ISCD. SCSI-TLVs MUST be 161 processed in the order received and, if re-originated, ordering MUST 162 be preserved. Unknown SCSI-TLVs MUST be ignored and transparently 163 processed, i.e., re-originated when appropriate. Processing related 164 to multiple SCSI-TLVs of the same type may be further refined based 165 on the definition on the type. 167 5. Security Considerations 169 This document does not introduce any security issue beyond those 170 discussed in [RFC4203] and [RFC5307]. As discussed there, the 171 information carried in ISCDs are not used for SPF computation or 172 normal routing and the extensions here defined do not have direct 173 effect on IP routing. Tampering with GMPLS TE LSAs may have an 174 effect on the underlying transport network. Mechanisms such as 175 [RFC2154] and [RFC5304] to protect the transmission of this 176 information are suggested. 178 6. IANA Considerations 180 This document defines a new SCSI-TLV that is carried in the SCSI 181 field of the ISCDs defined in [RFC4203] and [RFC5307]. The SCSI-TLV 182 includes a 16-bit type identifier (the Type field). The same Type 183 field values are applicable to the new SCSI-TLV. 185 IANA is requested to create and maintain a new registry, the 186 "Generalized SCSI (Switching Capability Specific Information) TLVs 187 Types" registry under the the "Generalized Multi-Protocol Label 188 Switching (GMPLS) Signaling Parameters" registry. 190 The definition of the new registry is as follows: 192 Value SCSI-TLV Switching Type Reference 193 --------- ----------------------- -------------- --------- 194 0 Reserved [This ID] 195 1-65535 Unassigned (value list) [This ID] 197 New allocation requests to this registry must indicate the value or 198 values to be used in the Switching Type column. 200 The registry should be established with registration policies of 201 "Specification Required", see [RFC5226]. 203 REMOVE THIS AFTER PUBLICATION: The designated expert will be 204 appointed by the Routing AD. It is suggested to appoint any current 205 TEAS WG chair. 207 7. Acknowledgments 209 The authors would like to thank Adrian Farrel and Julien Meuric for 210 the careful review and suggestions. Thomas Heide Clausen provided 211 useful comments as part of the Routing Directorate review. 213 8. References 215 8.1. Normative References 217 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 218 Requirement Levels", BCP 14, RFC 2119, 219 DOI 10.17487/RFC2119, March 1997, . 222 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 223 (TE) Extensions to OSPF Version 2", RFC 3630, 224 DOI 10.17487/RFC3630, September 2003, . 227 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 228 in Support of Generalized Multi-Protocol Label Switching 229 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 230 . 232 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 233 Support of Generalized Multi-Protocol Label Switching 234 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 235 . 237 [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions 238 in Support of Generalized Multi-Protocol Label Switching 239 (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, 240 . 242 8.2. Informative References 244 [I-D.ietf-ccamp-ospf-availability-extension] 245 Long, H., Ye, M., Mirsky, G., D'Alessandro, A., and H. 246 Shah, "OSPF-TE Link Availability Extension for Links with 247 Variable Discrete Bandwidth", draft-ietf-ccamp-ospf- 248 availability-extension-10 (work in progress), August 2017. 250 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 251 Digital Signatures", RFC 2154, DOI 10.17487/RFC2154, June 252 1997, . 254 [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label 255 Switching (GMPLS) Architecture", RFC 3945, 256 DOI 10.17487/RFC3945, October 2004, . 259 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 260 IANA Considerations Section in RFCs", RFC 5226, 261 DOI 10.17487/RFC5226, May 2008, . 264 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 265 Authentication", RFC 5304, DOI 10.17487/RFC5304, October 266 2008, . 268 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 269 J. Drake, "Traffic Engineering Extensions to OSPF for 270 GMPLS Control of Evolving G.709 Optical Transport 271 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 272 . 274 [RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF 275 Enhancement for Signal and Network Element Compatibility 276 for Wavelength Switched Optical Networks", RFC 7688, 277 DOI 10.17487/RFC7688, November 2015, . 280 8.3. URIs 282 [1] http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig- 283 parameters.xml#gmpls-sig-parameters-3 285 Authors' Addresses 287 Daniele Ceccarelli 288 Ericsson 289 Torshamnsgatan 21 290 Kista - Stockholm 291 Sweden 293 Email: daniele.ceccarelli@ericsson.com 295 Lou Berger 296 LabN Consulting, L.L.C. 298 Email: lberger@labn.net