idnits 2.17.1 draft-ietf-teas-gmpls-scsi-02.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 27, 2017) is 2588 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) == Missing Reference: 'This ID' is mentioned on line 185, but not defined == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-ospf-availability-extension-09 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 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: September 28, 2017 LabN Consulting, L.L.C. 6 March 27, 2017 8 Generalized Interface Switching Capability Descriptor - Switching 9 Capability Specific Information 10 draft-ietf-teas-gmpls-scsi-02 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 an existing technology specific formats and is defined for use 20 in conjunction with new GMPLS Switching Capability types. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on September 28, 2017. 39 Copyright Notice 41 Copyright (c) 2017 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Generalized SCSI Formats . . . . . . . . . . . . . . . . . . . 3 59 4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 62 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 64 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 65 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 68 1. Introduction 70 The Interface Switching Capability Descriptor (ISCD) [RFC4202] allows 71 routing protocols such as OSPF and ISIS to carry technology specific 72 information in the the Switching Capability-specific information 73 (SCSI) field, see [RFC4203] and [RFC5307]. The format of an SCSI 74 field is dictated by the specific technology being represented as 75 indicated by the ISCD Switching Capability (SC) type field. Existing 76 Switching Capabilities are managed by IANA in the Switching Types 77 registry and the related "IANA-GMPLS-TC-MIB" definitions. 79 [RFC7138] introduced a "sub-TLV" structure to its technology specific 80 SCSI field. The Sub-Type-Length-Value (TLV) based approach allows 81 for greater flexibility in the structure, ordering, and ability to 82 support extensions of the SC (technology) specific format. This Sub- 83 TLV approach is also used in [RFC7688]. 85 This document generalizes this approach and defines a new generalized 86 SCSI field format for use by future specific technologies and 87 Switching Capability types. The generalized SCSI carries SCSI-TLVs 88 that may be defined within the scope of a specific technology, or 89 shared across multiple technologies (e.g., 90 [I-D.ietf-ccamp-ospf-availability-extension]). This document also 91 establishes a registry for SCSI-TLV definitions that may be shared 92 across multiple technologies. 94 2. Terminology 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in [RFC2119]. 100 3. Generalized SCSI Formats 102 The Generalized SCSI is composed of zero or more variable length 103 type-length-value fields which are each called a SCSI-TLV. There are 104 no specific size restrictions on these SCSI-TLV. Size and other 105 formatting restrictions may be imposed by the routing protocol ISCD 106 field, refer to [RFC4203] and [RFC5307]. 108 The SCSI-TLV format is: 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Type | Length | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 ... Value ... 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 Figure 1: TLV format 120 Type (2 octets): 121 This field indicates the type and structure of the information 122 contained in the Value field. Note that the value range of this 123 field has been split in two. The lower range is used to indicated 124 technology specific formats, while the higher range is reserved 125 for formats that can be used with more than one technology. See 126 Section 6 128 Length (2 octets): 129 This field MUST be set to the size, in octets (bytes), of the 130 Value field. The value of the field MUST be zero or divisible by 131 4. Note that this implies that the Value field can be omitted or 132 contain padding. 134 Value (variable): 135 A variable length field, formatted according to the value of the 136 Type field. This field can be omitted for certain types. 138 4. Procedures 140 The ISCD can include a Generalized SCSI when advertising technologies 141 whose Switching Capability definition references this document. The 142 corollary of this is that the Generalized SCSI MUST NOT be used for 143 ISCDs of technologies whose Switching Capability definition do not 144 reference this document. 146 The Generalized SCSI MAY contain a sequence of zero or more SCSI- 147 TLVs. Sub-TLV parsing (format) errors, such as an underrun or 148 overrun, MUST be treated as a malformed ISCD. SCSI-TLVs MUST be 149 processed in the order received and, if re-originated, ordering MUST 150 be preserved. Unknown SCSI-TLVs MUST be ignored and transparently 151 processed, i.e., re-originated when appropriate. Processing related 152 to multiple SCSI-TLVs of the same type may be further refined based 153 on the definition on the type. 155 5. Security Considerations 157 This document does not introduce any security issue beyond those 158 discussed in [RFC4203] and [RFC5307]. As discussed there, the 159 information carried in ISCDs are not used for SPF computation or 160 normal routing and the extensions here defined do not have direct 161 effect on IP routing. Tampering with GMPLS TE LSAs may have an 162 effect on the underlying transport network. Mechanisms such as 163 [RFC2154] and [RFC5304] to protect the transmission of this 164 information are suggested. 166 6. IANA Considerations 168 This document defines a new SCSI-TLV that is carried in the SCSI 169 field of the ISCDs defined in [RFC4203] and [RFC5307]. The SCSI-TLV 170 includes a 16-bit type identifier (the Type field). The same Type 171 field values are applicable to the new SCSI-TLV. 173 IANA is requested to create and maintain a new registry, the 174 "Generalized SCSI (Switching Capability Specific Information) TLVs 175 Types" registry under either the the "Generalized Multi-Protocol 176 Label Switching (GMPLS) Signaling Parameters" registry or a new 177 "Generalized Multi-Protocol Label Switching (GMPLS) Routing 178 Parameters" registry. 180 The definition of the new registry is as follows: 182 Value SCSI-TLV Switching Type Reference 183 --------- ----------------------- -------------- --------- 184 0 Reserved [This ID] 185 1-65535 Unassigned (Any, or [This ID] 186 value list) 188 New allocation requests to this registry must indicate the value or 189 values to be used in the Switching Type column. 191 The registry should be established with registration policies of 192 "Specification Required", see [RFC5226]. 194 REMOVE THIS AFTER PUBLICATION: The designated expert will be 195 appointed by the Routing AD. It is suggested to appoint any current 196 TEAS WG chair. 198 7. Acknowledgements 200 The authors would like to thank Adrian Farrel and Julien Meuric for 201 the careful review and suggestions. 203 8. References 205 8.1. Normative References 207 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 208 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 209 RFC2119, March 1997, 210 . 212 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 213 in Support of Generalized Multi-Protocol Label Switching 214 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 215 . 217 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 218 Support of Generalized Multi-Protocol Label Switching 219 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 220 . 222 [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions 223 in Support of Generalized Multi-Protocol Label Switching 224 (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, 225 . 227 8.2. Informative References 229 [I-D.ietf-ccamp-ospf-availability-extension] 230 Long, H., Ye, M., Mirsky, G., D'Alessandro, A., and H. 231 Shah, "OSPF-TE Link Availability Extension for Links with 232 Variable Discrete Bandwidth", 233 draft-ietf-ccamp-ospf-availability-extension-09 (work in 234 progress), February 2017. 236 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 237 Digital Signatures", RFC 2154, DOI 10.17487/RFC2154, 238 June 1997, . 240 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 241 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 242 DOI 10.17487/RFC5226, May 2008, 243 . 245 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 246 Authentication", RFC 5304, DOI 10.17487/RFC5304, 247 October 2008, . 249 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 250 J. Drake, "Traffic Engineering Extensions to OSPF for 251 GMPLS Control of Evolving G.709 Optical Transport 252 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 253 . 255 [RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF 256 Enhancement for Signal and Network Element Compatibility 257 for Wavelength Switched Optical Networks", RFC 7688, 258 DOI 10.17487/RFC7688, November 2015, 259 . 261 Authors' Addresses 263 Daniele Ceccarelli 264 Ericsson 265 Torshamnsgatan 21 266 Kista - Stockholm 267 Sweden 269 Email: daniele.ceccarelli@ericsson.com 271 Lou Berger 272 LabN Consulting, L.L.C. 274 Email: lberger@labn.net