idnits 2.17.1 draft-ietf-ccamp-ospf-availability-extension-12.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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (November 10, 2017) is 2359 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 285, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE754-2008' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group H. Long, M.Ye 2 Internet Draft Huawei Technologies Co., Ltd 3 Intended status: Standards Track G. Mirsky 4 ZTE 5 A.D'Alessandro 6 Telecom Italia S.p.A 7 H. Shah 8 Ciena 9 Expires: May 2018 November 10, 2017 11 OSPF-Traffic Engineering Link Availability Extension for Links with 12 Variable Discrete Bandwidth 13 draft-ietf-ccamp-ospf-availability-extension-12.txt 15 Abstract 17 A network may contain links with variable discrete bandwidth, e.g., 18 copper, radio, etc. The bandwidth of such links may change 19 discretely in reaction to changing external environment. 20 Availability is typically used for describing such links during 21 network planning. This document defines a new type of the 22 Generalized Switching Capability-specific information (SCSI) TLV to 23 extend the Generalized Multi-Protocol Label Switching (GMPLS) Open 24 Shortest Path First (OSPF) routing protocol. The extension can be 25 used for route computation in a network that contains links with 26 variable discrete bandwidth. Note, this document only covers the 27 mechanisms by which the availability information is distributed. The 28 mechanisms by which availability information of a link is determined 29 and the use of the distributed information for route computation are 30 outside the scope of this document. It is intended that technology- 31 specific documents will reference this document to describe specific 32 uses. 34 Status of this Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF), its areas, and its working groups. Note that 41 other groups may also distribute working documents as Internet- 42 Drafts. 44 Internet-Drafts are draft documents valid for a maximum of six 45 months and may be updated, replaced, or obsoleted by other documents 46 at any time. It is inappropriate to use Internet-Drafts as 47 reference material or to cite them other than as "work in progress." 49 The list of current Internet-Drafts can be accessed at 50 http://www.ietf.org/ietf/1id-abstracts.txt 52 The list of Internet-Draft Shadow Directories can be accessed at 53 http://www.ietf.org/shadow.html 55 This Internet-Draft will expire on April 10, 2018. 57 Copyright Notice 59 Copyright (c) 2017 IETF Trust and the persons identified as the 60 document authors. All rights reserved. 62 This document is subject to BCP 78 and the IETF Trust's Legal 63 Provisions Relating to IETF Documents 64 (http://trustee.ietf.org/license-info) in effect on the date of 65 publication of this document. Please review these documents 66 carefully, as they describe your rights and restrictions with 67 respect to this document. Code Components extracted from this 68 document must include Simplified BSD License text as described in 69 Section 4.e of the Trust Legal Provisions and are provided without 70 warranty as described in the Simplified BSD License. 72 Table of Contents 74 1. Introduction ................................................ 3 75 2. Acronyms .................................................... 3 76 3. Overview .................................................... 4 77 4. TE Metric Extension to OSPF-TE............................... 4 78 4.1. Availability SCSI-TLV................................... 4 79 4.2. Processing Procedures................................... 5 80 5. Security Considerations...................................... 6 81 6. IANA Considerations ......................................... 7 82 7. References .................................................. 7 83 7.1. Normative References.................................... 7 84 7.2. Informative References.................................. 8 85 8. Acknowledgments ............................................. 8 87 Conventions used in this document 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and 90 "OPTIONAL" in this document are to be interpreted as described in 91 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 92 capitals, as shown here. 94 1. Introduction 96 Some data plane technologies, e.g., microwave, and copper, allow 97 seamless change of maximum physical bandwidth through a set of known 98 discrete values. The parameter, availability, as described in 99 [G.827], [F.1703] and [P.530] is often used to describe the link 100 capacity. The availability is a time scale, representing a proportion 101 of the operating time that the requested bandwidth is ensured. To 102 set up an LSP across these links, availability information is 103 required by the nodes to verify the bandwidth before making a 104 bandwidth reservation. Assigning different availability classes 105 over such links provides for a more efficient planning of link 106 capacity to support different types of services. The link 107 availability information will be determined by the operator and 108 statically configured. It will usually be determined from the 109 availability requirements of the services expected to be carried on 110 the LSP. For example, voice service usually needs "five nines" 111 availability, while non-real time services may adequately perform at 112 four or three nines availability. For the route computation, both 113 the availability information and the bandwidth resource information 114 are needed. Since different service types may need different 115 availability guarantees, multiple pairs 116 may be required to be associated with a link. 118 In this document, a new type of the Generalized SCSI TLV, 119 Availability TLV is defined. It is intended that technology-specific 120 documents will reference this document to describe specific uses. 121 The signaling extension to support links with discrete bandwidth is 122 defined in [I-D. ietf-ccamp-rsvp-te-bandwidth-availability]. 124 2. Acronyms 126 The following acronyms are used in this draft: 128 GMPLS Generalized Multi-Protocol Label Switching 130 LSA Link State Advertisement 132 ISCD Interface Switching Capability Descriptor 133 LSP Label Switched Path 135 OSPF Open Shortest Path First 137 PSN Packet Switched Network 139 SCSI Switching Capability-specific information 141 SNR Signal-to-noise Ratio 143 SONET-SDH Synchronous Optical Network - Synchronous Digital 144 Hierarchy 146 SPF Shortest Path First 148 TE Traffic Engineering 150 TLV Type Length Value 152 3. Overview 154 A node which has link(s) with variable bandwidth attached should 155 include < availability, bandwidth> information list in its OSPF 156 Traffic Engineering (TE) LSA messages. The list provides the mapping 157 between the link nominal bandwidth and its availability level. This 158 information is used for path calculation by the node(s). The setup 159 of a Label Switched Path requires this information to be flooded in 160 the network and used by the nodes or the PCE for the path 161 computation. In this document, a new type of the Generalized SCSI 162 TLV, Availability TLV is defined. The computed path can then be 163 provisioned via the signaling protocol [I-D. ietf-ccamp-rsvp-te- 164 bandwidth-availability]. 166 Note, the mechanisms described in this document only distribute 167 availability information. The methods for measuring the information 168 or using the information for route computation are outside the scope 169 of this document. 171 4. TE Metric Extension to OSPF-TE 173 4.1. Availability SCSI-TLV 175 The Generalized SCSI is defined in [I-D. ietf-teas-gmpls-scsi]. The 176 Availability TLV defined in this document is a new type of 177 Generalized SCSI-TLV. The Availability SCSI-TLV can be included for 178 one or more times. The Availability SCSI-TLV has the following 179 format: 181 0 1 2 3 182 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 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Type | Length | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | Availability level | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | LSP Bandwidth at Availability level n | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 Type: 0x0001, 16 bits. 192 Length: 2 octets, 16 bits. 194 Availability level: 32 bits 196 This field is a binary32-format floating point number as defined by 197 [IEEE754-2008]. The bytes are transmitted in network order; that is, 198 the byte containing the sign bit is transmitted first. This field 199 describes the decimal value of availability guarantee of the 200 switching capability in the Interface Switching Capability 201 Descriptor (ISCD) [RFC4202] object. The value MUST be less than 1. 202 The Availability level is usually expressed in the value of 203 0.99/0.999/0.9999/0.99999. 205 LSP Bandwidth at Availability level n: 32 bits 207 This field is a 32-bit IEEE floating point number as defined by 208 [IEEE754-2008]. The bytes are transmitted in network order; that is, 209 the byte containing the sign bit is transmitted first. This field 210 describes the LSP Bandwidth for the Availability level represented 211 in the Availability field. The units are bytes per second. 213 4.2. Processing Procedures 215 The ISCD allows routing protocols such as OSPF to carry technology 216 specific information in the Switching Capability-specific 217 information (SCSI) field, see [RFC4203]. A node advertising an 218 interface with a Switching Capability which supports variable 219 bandwidth attached SHOULD contain one or more Availability SCSI-TLVs 220 in its OSPF TE LSA messages. Each Availability SCSI-TLV provides the 221 information about how much bandwidth a link can support for a 222 specified availability. This information may be used for path 223 calculation by the node(s). 225 The Availability SCSI-TLV MUST NOT be sent in ISCDs with Switching 226 Capability field values that have not been defined to support the 227 Availability SCSI-TLV. Non-supporting nodes would see such as a 228 malformed ISCD/LSA. 230 Absence of the Availability SCSI-TLV in an ISCD containing Switching 231 Capability field values that have been defined to support the 232 Availability SCSI-TLV, SHALL be interpreted as representing fixed- 233 bandwidth link with the highest availability value. 235 Only one Availability SCSI-TLV for the specific availability level 236 SHOULD be sent. If multiple are present, the Availability SCSI-TLV 237 with the lowest bandwidth value SHALL be processed. If an 238 Availability SCSI-TLV with an invalid value (e.g., large than 1) is 239 received, the Availability SCSI-TLV will be ignored. 241 5. Security Considerations 243 This document does not introduce security issues beyond those 244 discussed in [RFC4203]. As with [RFC4203], it specifies the content 245 of an Opaque LSAs in OSPFv2. As Opaque LSAs are not used for 246 Shortest Path First (SPF) computation or normal routing, the 247 extensions specified here have no direct effect on IP routing. 248 Tampering with GMPLS TE LSAs may have an impact on the ability to 249 set up connections in the underlying data plane network. As the 250 additional availability information may represent information that 251 an operator may wish to keep private, consideration should be given 252 to securing this information. [RFC3630] notes that the security 253 mechanisms described in [RFC2328] apply to Opaque LSAs carried in 254 OSPFv2. An analysis of the security of OSPF is provided in 255 [RFC6863] and applies to the extensions to OSPF as described in this 256 document. Any new mechanisms developed to protect the transmission 257 of information carried in Opaque LSAs will also automatically 258 protect the extensions defined in this document. 260 Please refer to [RFC5920] for details on security threats; defensive 261 techniques; monitoring, detection, and reporting of security 262 attacks; and requirements. 264 6. IANA Considerations 266 This document introduces a new type for availability of the 267 Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for 268 OSPF v2. Technology-specific documents will reference this document 269 to describe specific use of this Availability SCSI-TLV. 271 IANA has created a registry called the "Generalized SCSI (Switching 272 Capability Specific Information) TLVs Types" registry. The registry 273 is needed to be updated to include the Availability SCSI-TLV. This 274 document proposes a suggested value for the Availability SCSI-TLV; 275 it is requested that the suggested value be granted by IANA. 277 Note (Please REMOVE this note before publication): the registry will 278 be created by draft-ietf-teas-gmpls-scsi. The requested value should 279 be added to it when it is created. 281 Type Description Reference 283 --- ------------------ ----------- 285 0x01 Availability [This ID] 287 7. References 289 7.1. Normative References 291 [I-D. ietf-teas-gmpls-scsi] Ceccarelli, D. and Berger, L., 292 "Generalized Routing Interface Switching Capability 293 Descriptor Switching Capability Specific Information", 294 Work in Progress, August, 2017. 296 [RFC4202] Kompella, K. and Rekhter, Y. (Editors), "Routing 297 Extensions in Support of Generalized Multi-Protocol Label 298 Switching (GMPLS)", RFC 4202, October 2005. 300 [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions 301 in Support of Generalized Multi-Protocol Label Switching 302 (GMPLS)", RFC 4203, October 2005. 304 [IEEE754-2008] IEEE standards, "IEEE Standard for Floating-Point 305 Arithmetic", IEEE Standard 754, August 2008 307 7.2. Informative References 309 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 310 Requirement Levels", RFC 2119, March 1997. 312 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 314 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 315 (TE) Extensions to OSPF Version 2", RFC 3630, September 316 2003. 318 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 319 Networks", RFC 5920, July 2010. 321 [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security 322 According to the Keying and Authentication for Routing 323 Protocols (KARP) Design Guide", RFC 6863, March 2013. 325 [G.827] ITU-T Recommendation, "Availability performance parameters 326 and objectives for end-to-end international constant bit- 327 rate digital paths", September, 2003. 329 [F.1703] ITU-R Recommendation, "Availability objectives for real 330 digital fixed wireless links used in 27 500 km 331 hypothetical reference paths and connections", January, 332 2005. 334 [P.530] ITU-R Recommendation," Propagation data and prediction 335 methods required for the design of terrestrial line-of- 336 sight systems", February, 2012 338 [I-D. ietf-ccamp-rsvp-te-bandwidth-availability] H., Long, M., Ye, 339 Mirsky, G., Alessandro, A., Shah, H., "Ethernet Traffic 340 Parameters with Availability Information", Work in 341 Progress, August, 2017 343 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 344 2119 Key Words", RFC 8174, May 2017. 346 8. Acknowledgments 348 The authors would like to thank Acee Lindem, Daniele Ceccarelli, Lou 349 Berger for their comments on the document. 351 Authors' Addresses 353 Hao Long 354 Huawei Technologies Co., Ltd. 355 No.1899, Xiyuan Avenue, Hi-tech Western District 356 Chengdu 611731, P.R.China 358 Phone: +86-18615778750 359 Email: longhao@huawei.com 361 Min Ye 362 Huawei Technologies Co., Ltd. 363 No.1899, Xiyuan Avenue, Hi-tech Western District 364 Chengdu 611731, P.R.China 366 Email: amy.yemin@huawei.com 368 Greg Mirsky 369 ZTE 371 Email: gregimirsky@gmail.com 373 Alessandro D'Alessandro 374 Telecom Italia S.p.A 376 Email: alessandro.dalessandro@telecomitalia.it 378 Himanshu Shah 379 Ciena Corp. 380 3939 North First Street 381 San Jose, CA 95134 382 US 384 Email: hshah@ciena.com