idnits 2.17.1 draft-ietf-teas-gmpls-scsi-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 (January 12, 2017) is 2660 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 187, but not defined == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-ospf-availability-extension-08 -- 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: July 16, 2017 LabN Consulting, L.L.C. 6 January 12, 2017 8 Generalized Routing Interface Switching Capability Descriptor Switching 9 Capability Specific Information 10 draft-ietf-teas-gmpls-scsi-01 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 July 16, 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. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 67 1. Introduction 69 The Interface Switching Capability Descriptor (ISCD) [RFC4202] allows 70 routing protocols such as OSPF and ISIS to carry technology specific 71 information in the the Switching Capability-specific information 72 (SCSI) field, see [RFC4203] and [RFC5307]. The format of an SCSI 73 field is dictated by the specific technology being represented as 74 indicated by the ISCD Switching Capability (SC) type field. Existing 75 Switching Capabilities are managed by IANA in the Switching Types 76 registry and the related "IANA-GMPLS-TC-MIB" definitions. 78 [RFC7138] introduced a "sub-TLV" structure to its technology specific 79 SCSI field. The Sub-Type-Length-Value (TLV) based approach allows 80 for greater flexibility in the structure, ordering, and ability to 81 support extensions of the SC (technology) specific format. This Sub- 82 TLV approach is also used in [RFC7688]. 84 This document generalizes this approach and defines a new generalized 85 SCSI field format for use by future specific technologies and 86 Switching Capability types. The generalized SCSI carries SCSI-TLVs 87 that may be defined within the scope of a specific technology, or 88 shared across multiple technologies (e.g., 89 [I-D.ietf-ccamp-ospf-availability-extension]). This document also 90 establishes a registry for SCSI-TLV definitions that may be shared 91 across multiple technologies. 93 2. Terminology 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in [RFC2119]. 99 3. Generalized SCSI Formats 101 The Generalized SCSI is composed of zero or more variable length 102 type-length-value fields which are each called a SCSI-TLV. There are 103 no specific size restrictions on these SCSI-TLV. Size and other 104 formatting restrictions may be imposed by the routing protocol ISCD 105 field, refer to [RFC4203] and [RFC5307]. 107 The SCSI-TLV format is: 109 0 1 2 3 110 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 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | Type | Length | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 ... Value ... 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 Figure 1: TLV format 119 Type (2 octets): 120 This field indicates the type and structure of the information 121 contained in the Value field. Note that the value range of this 122 field has been split in two. The lower range is used to indicated 123 technology specific formats, while the higher range is reserved 124 for formats that can be used with more than one technology. See 125 Section 6 127 Length (2 octets): 128 This field MUST be set to the size, in octets (bytes), of the 129 Value field. The value of the field MUST be zero or divisible by 130 4. Note that this implies that the Value field can be omitted or 131 contain padding. 133 Value (variable): 134 A variable length field, formatted according to the value of the 135 Type field. This field can be omitted for certain types. 137 4. Procedures 139 The Generalized SCSI is used with ISCDs (defined in [RFC4203] and 140 [RFC5307]) of technologies whose Switching Capability definition 141 reference this document. The corollary of this is that the 142 Generalized SCSI MUST NOT be used for ISCDs of technologies whose 143 Switching Capability definition do not reference this document. 145 The Generalized SCSI MAY contain a sequence of zero or more SCSI- 146 TLVs. Sub-TLV parsing (format) errors, such as an underrun or 147 overrun, MUST be treated as a malformed ISCD. SCSI-TLVs MUST be 148 processed in the order received and, if re-originated, ordering MUST 149 be preserved. Unknown SCSI-TLVs MUST be ignored and transparently 150 processed, i.e., re-originated when appropriate. Processing related 151 to multiple SCSI-TLVs of the same type may be further refined based 152 on the definition on the type. 154 5. Security Considerations 156 This document does not introduce any security issue beyond those 157 discussed in [RFC4203] and [RFC5307]. As discussed there, the 158 information carried in ISCDs are not used for SPF computation or 159 normal routing and the extensions here defined do not have direct 160 effect on IP routing. Tampering with GMPLS TE LSAs may have an 161 effect on the underlying transport network. Mechanisms such as 162 [RFC2154] and [RFC5304] to protect the transmission of this 163 information are suggested. 165 6. IANA Considerations 167 This document defines a new SCSI-TLV that is carried in the SCSI 168 field of the ISCDs defined in [RFC4203] and [RFC5307]. The SCSI-TLV 169 includes a 16-bit type identifier (the Type field). The same Type 170 field values are applicable to the new SCSI-TLV. 172 IANA is requested to create and maintain a new registry, the 173 "Generalized SCSI (Switching Capability Specific Information) TLVs 174 Types" registry under either the the "Generalized Multi-Protocol 175 Label Switching (GMPLS) Signaling Parameters" registry or a new 176 "Generalized Multi-Protocol Label Switching (GMPLS) Routing 177 Parameters" registry. 179 The definition of the new registry is as follows: 181 Value SCSI-TLV SwitchCap Reference 182 --------- -------------------------- --------- --------- 183 0 Reserved [This ID] 184 1-32768 Unassigned, for use by [per value] 185 specific technology [This ID] 186 32768-65535 Unassigned, for others (Any, or 187 value list) [This ID] 189 New allocation requests to this registry SHALL indicate the value or 190 values to be used in the SwitchCap column. 192 The registry should be established with registration policies of 193 "Standards Action" for Standards Track documents, and "Specification 194 Required" for other documents, see [RFC5226]. The designated expert 195 is any current TEAS WG chair. 197 7. References 199 7.1. Normative References 201 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 202 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 203 RFC2119, March 1997, 204 . 206 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 207 in Support of Generalized Multi-Protocol Label Switching 208 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 209 . 211 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 212 Support of Generalized Multi-Protocol Label Switching 213 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 214 . 216 [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions 217 in Support of Generalized Multi-Protocol Label Switching 218 (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, 219 . 221 7.2. Informative References 223 [I-D.ietf-ccamp-ospf-availability-extension] 224 Long, H., Ye, M., Mirsky, G., D'Alessandro, A., and H. 225 Shah, "OSPF-TE Link Availability Extension for Links with 226 Variable Discrete Bandwidth", 227 draft-ietf-ccamp-ospf-availability-extension-08 (work in 228 progress), October 2016. 230 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 231 Digital Signatures", RFC 2154, DOI 10.17487/RFC2154, 232 June 1997, . 234 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 235 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 236 DOI 10.17487/RFC5226, May 2008, 237 . 239 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 240 Authentication", RFC 5304, DOI 10.17487/RFC5304, 241 October 2008, . 243 [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and 244 J. Drake, "Traffic Engineering Extensions to OSPF for 245 GMPLS Control of Evolving G.709 Optical Transport 246 Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, 247 . 249 [RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF 250 Enhancement for Signal and Network Element Compatibility 251 for Wavelength Switched Optical Networks", RFC 7688, 252 DOI 10.17487/RFC7688, November 2015, 253 . 255 Authors' Addresses 257 Daniele Ceccarelli 258 Ericsson 259 Torshamnsgatan 21 260 Kista - Stockholm 261 Sweden 263 Email: daniele.ceccarelli@ericsson.com 265 Lou Berger 266 LabN Consulting, L.L.C. 268 Email: lberger@labn.net