idnits 2.17.1 draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.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 (April 30, 2019) is 1795 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 324, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE754' Summary: 0 errors (**), 0 flaws (~~), 2 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: October 2019 April 30, 2019 11 Ethernet Traffic Parameters with Availability Information 12 draft-ietf-ccamp-rsvp-te-bandwidth-availability-15.txt 14 Abstract 16 A packet switching network may contain links with variable 17 bandwidth, e.g., copper, radio, etc. The bandwidth of such links is 18 sensitive to external environment (e.g., climate). Availability is 19 typically used for describing these links when doing network 20 planning. This document introduces an optional Bandwidth 21 Availability TLV in Resource ReSerVation Protocol - Traffic Engineer 22 (RSVP-TE) signaling. This extension can be used to set up a 23 Generalized Multi-Protocol Label Switching (GMPLS) Label Switched 24 Path (LSP) in conjunction with the Ethernet SENDER_TSPEC object. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six 37 months and may be updated, replaced, or obsoleted by other documents 38 at any time. It is inappropriate to use Internet-Drafts as 39 reference material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html 46 This Internet-Draft will expire on October 30, 2019. 48 Copyright Notice 50 Copyright (c) 2019 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described in 60 Section 4.e of the Trust Legal Provisions and are provided without 61 warranty as described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction ................................................ 3 66 2. Overview .................................................... 4 67 3. Extension to RSVP-TE Signaling............................... 5 68 3.1. Bandwidth Availability TLV.............................. 5 69 3.2. Signaling Process....................................... 6 70 4. Security Considerations...................................... 7 71 5. IANA Considerations ......................................... 7 72 5.1 Ethernet Sender TSpec TLVs ............................. 7 73 6. References .................................................. 8 74 6.1. Normative References.................................... 8 75 6.2. Informative References.................................. 9 76 7. Appendix: Bandwidth Availability Example..................... 9 77 8. Acknowledgments ............................................ 11 79 Conventions used in this document 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 83 "OPTIONAL" in this document are to be interpreted as described in 84 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 85 capitals, as shown here. 87 The following acronyms are used in this draft: 89 RSVP-TE Resource Reservation Protocol-Traffic Engineering 91 LSP Label Switched Path 92 SNR Signal-to-noise Ratio 94 TLV Type Length Value 96 LSA Link State Advertisement 98 1. Introduction 100 The RSVP-TE specification [RFC3209] and GMPLS extensions [RFC3473] 101 specify the signaling message including the bandwidth request for 102 setting up a Label Switched Path in a packet switching network. 104 Some data communication technologies allow seamless change of 105 maximum physical bandwidth through a set of known discrete values. 106 The parameter availability [G.827], [F.1703], [P.530] is often used 107 to describe the link capacity during network planning. The 108 availability is based on a time scale, which is a proportion of the 109 operating time that the requested bandwidth is ensured. A more 110 detailed example on the bandwidth availability can be found in 111 Appendix A. Assigning different bandwidth availability classes to 112 different types of services over such kind of links provides for a 113 more efficient planning of link capacity. To set up an LSP across 114 these links, bandwidth availability information is required for the 115 nodes to verify bandwidth satisfaction and make bandwidth 116 reservation. The bandwidth availability information should be 117 inherited from the bandwidth availability requirements of the 118 services expected to be carried on the LSP. For example, voice 119 service usually needs "five nines" bandwidth availability, while 120 non-real time services may adequately perform at four or three nines 121 bandwidth availability. Since different service types may need 122 different availabilities guarantees, multiple pairs may be required when signaling. 125 If the bandwidth availability requirement is not specified in the 126 signaling message, the bandwidth will likely be reserved as the 127 highest bandwidth availability. Suppose, for example, the bandwidth 128 with 99.999% availability of a link is 100 Mbps; the bandwidth with 129 99.99% availability is 200 Mbps. When a video application makes a 130 request for 120 Mbps without bandwidth availability requirement, the 131 system will consider the request as 120 Mbps with 99.999% bandwidth 132 availability, while the available bandwidth with 99.999% bandwidth 133 availability is only 100 Mbps, therefore the LSP path cannot be set 134 up. But, in fact, the video application doesn't need 99.999% 135 bandwidth availability; 99.99% bandwidth availability is enough. In 136 this case, the LSP could be set up if bandwidth availability is also 137 specified in the signaling message. 139 To fulfill LSP setup by signaling in these scenarios, this document 140 specifies a Bandwidth Availability TLV. The Bandwidth Availability 141 TLV can be applicable to any kind of physical links with variable 142 discrete bandwidth, such as microwave or DSL. Multiple Bandwidth 143 Availability TLVs together with multiple Ethernet Bandwidth Profiles 144 can be carried by the Ethernet SENDER_TSPEC object [RFC6003]. Since 145 the Ethernet FLOWSPEC object has the same format as the Ethernet 146 SENDER_TSPEC object [RFC6003], the Bandwidth Availability TLV can 147 also be carried by the Ethernet FLOWSPEC object. 149 2. Overview 151 A tunnel in a packet switching network may span one or more links in 152 a network. To setup a Label Switched Path (LSP), a node may collect 153 link information which is advertised in a routing message, e.g., 154 OSPF TE LSA message, by network nodes to obtain network topology 155 information, and then calculate an LSP route based on the network 156 topology. The calculated LSP route is signaled using a PATH/RESV 157 message for setting up the LSP. 159 In case that there is (are) link(s) with variable discrete bandwidth 160 in a network, a requirement list should be 161 specified for an LSP at setup. Each pair 162 in the list means the listed bandwidth with specified availability 163 is required. The list could be derived from the results of service 164 planning for the LSP. 166 A node which has link(s) with variable discrete bandwidth attached 167 should contain a information list in its 168 OSPF TE LSA messages. The list provides the mapping between the link 169 nominal bandwidth and its availability level. This information can 170 then be used for path calculation by the node(s). The routing 171 extension for availability can be found in [RFC8330]. 173 When a node initiates a PATH/RESV signaling to set up an LSP, the 174 PATH message should carry the requirement 175 list as a bandwidth request. Intermediate node(s) will allocate the 176 bandwidth resource for each availability requirement from the 177 remaining bandwidth with corresponding availability. An error 178 message may be returned if any request 179 cannot be satisfied. 181 3. Extension to RSVP-TE Signaling 183 3.1. Bandwidth Availability TLV 185 A Bandwidth Availability TLV is defined as a TLV of the Ethernet 186 SENDER_TSPEC object [RFC6003] in this document. The Ethernet 187 SENDER_TSPEC object MAY include more than one Bandwidth Availability 188 TLV. The Bandwidth Availability TLV has the following format: 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 | Type | Length | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Index | Reserved | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | Availability | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 Figure 1: Bandwidth Availability TLV 202 Type (2 octets): 0x04(suggested; TBD by IANA) 204 Length (2 octets): 0x0C. Indicates the length in bytes of the 205 whole TLV including the Type and Length fields, in this case 12 206 bytes. 208 Index (1 octet): 210 When the Bandwidth Availability TLV is included, the Ethernet 211 Bandwidth Profile TLV MUST also be included. If there are multiple 212 bandwidth requirements present (in multiple Ethernet Bandwidth 213 Profile TLVs) and they have different availability requirements, 214 multiple Bandwidth Availability TLVs MUST be carried. In such a 215 case, the Bandwidth Availability TLV has a one to one 216 correspondence with the Ethernet Bandwidth Profile TLV by having 217 the same value of Index field. If all the bandwidth requirements 218 in the Ethernet Bandwidth Profile have the same Availability 219 requirement, one Bandwidth Availability TLV SHOULD be carried. In 220 this case, the Index field is set to 0. 222 Reserved (3 octets): These bits SHOULD be set to zero when sent 223 and MUST be ignored when received. 225 Availability (4 octets): a 32-bit floating-point number [IEEE754] 226 describes the decimal value of the availability requirement for 227 this bandwidth request. The value MUST be less than 1 and is 228 usually expressed in the value of 0.99/0.999/0.9999/0.99999. The 229 IEEE floating-point number is used here to align with [RFC8330]. 230 However when representing values higher than 0.999999, the 231 floating-point number starts to introduce errors in relation to 232 intended precision. However in reality, 0.99999 is normally 233 considered as the highest availability value (5 minutes outage in 234 a year) in telecom network, therefore the use of floating-point 235 number in availability is acceptable. 237 3.2. Signaling Process 239 The source node initiates a PATH message which may carry a number of 240 bandwidth requests, including one or more Ethernet Bandwidth Profile 241 TLVs and one or more Bandwidth Availability TLVs. Each Ethernet 242 Bandwidth Profile TLV corresponds to an availability parameter in 243 the associated Bandwidth Availability TLV. 245 The intermediate and destination nodes check whether they can 246 satisfy the bandwidth requirements by comparing each bandwidth 247 request inside the SENDER_TSPEC objects with the remaining link sub- 248 bandwidth resource with respective availability guarantee on the 249 local link when the PATH message is received. 251 o When all requirement requests can 252 be satisfied (the requested bandwidth under each availability 253 parameter is smaller than or equal to the remaining bandwidth 254 under the corresponding availability parameter on its local 255 link), the node SHOULD reserve the bandwidth resource from each 256 remaining sub-bandwidth portion on its local link to set up 257 this LSP. Optionally, a higher availability bandwidth can be 258 allocated to a lower availability request when the lower 259 availability bandwidth cannot satisfy the request. 261 o When at least one requirement 262 request cannot be satisfied, the node SHOULD generate PathErr 263 message with the error code "Admission Control Error" and the 264 error value "Requested Bandwidth Unavailable" (see [RFC2205]). 266 When two LSPs request bandwidth with the same availability 267 requirement, contention MUST be resolved by comparing the node IDs, 268 with the LSP with the higher node ID being assigned the reservation. 269 This is consistent with general contention resolution mechanism 270 provided in section 4.2 of [RFC3471]. 272 When a node does not support the Bandwidth Availability TLV, the 273 node should send a PathErr message with error code "Unknown 274 Attributes TLV", as specified in [RFC5420]. An LSP could also be set 275 up in this case if there's enough bandwidth (the availability level 276 of the reserved bandwidth is unknown). When a node receives 277 Bandwidth Availability TLVs with a mix of zero index and non-zero 278 index, the message MUST be ignored and MUST NOT be propagated. When 279 a node receives Bandwidth Availability TLVs (non-zero index) with no 280 matching index value among the bandwidth-TLVs, the message MUST be 281 ignored and MUST NOT be propagated. When a node receives several 282 pairs, but there are extra bandwidth-TLVs 283 without matching the index of any Availability-TLV, the extra 284 bandwidth-TLVs MUST be ignored and MUST NOT be propagated. 286 4. Security Considerations 288 This document defines a Bandwidth Availability TLV in RSVP-TE 289 signaling used in GMPLS networks. [RFC3945] notes that 290 authentication in GMPLS systems may use the authentication 291 mechanisms of the component protocols. [RFC5920] provides an 292 overview of security vulnerabilities and protection mechanisms for 293 the GMPLS control plane. Especially section 7.1.2 of [RFC5920] 294 discusses the control-plane protection with RSVP-TE by using general 295 RSVP security tools, limiting the impact of an attack on control- 296 plane resources, and authentication for RSVP messages. Moreover, the 297 GMPLS network is often considered to be a closed network such that 298 insertion, modification, or inspection of packets by an outside 299 party is not possible. 301 5. IANA Considerations 303 IANA maintains registries and sub-registries for RSVP-TE used by 304 GMPLS. IANA is requested to make allocations from these registries 305 as set out in the following sections. 307 5.1 Ethernet Sender TSpec TLVs 309 IANA maintains a registry of GMPLS parameters called "Generalized 310 Multi-Protocol Label Switching (GMPLS) Signaling Parameters". 312 IANA has created a sub-registry called "Ethernet Sender TSpec TLVs / 313 Ethernet Flowspec TLVs" to contain the TLV type values for TLVs 314 carried in the Ethernet SENDER_TSPEC object. The sub-registry needs 315 to be updated to include the Bandwidth Availability TLV which is 316 defined as follow. This document proposes a suggested value for the 317 Availability sub-TLV; it is requested that the suggested value be 318 granted by IANA. 320 Type Description Reference 322 ----- -------------------- --------- 324 0x04 Bandwidth Availability [This ID] 326 (Suggested; TBD by IANA) 328 The registration procedure for this registry is Standards Action as 329 defined in [RFC8126]. 331 6. References 333 6.1. Normative References 335 [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and 336 S.Jamin, "Resource ReSerVation Protocol (RSVP) - Version 1 337 Functional Specification", RFC 2205, September 1997. 339 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, 340 V.,and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 341 Tunnels", RFC 3209, December 2001. 343 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 344 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 345 Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. 347 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 348 (GMPLS) Signaling Functional Description", RFC 3471, 349 January 2003. 351 [RFC5420] Farrel, A., Papadimitriou, D., Vasseur JP., and Ayyangar 352 A., "Encoding of Attributes for MPLS LSP Establishment 353 Using Resource Reservation Protocol Traffic Engineering 354 (RSVP-TE)", RFC 5420, February 2009. 356 [RFC6003] Papadimitriou, D. "Ethernet Traffic Parameters", RFC 6003, 357 October 2010. 359 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 360 2119 Key Words", BCP 14, RFC 8174, May 2017. 362 [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic",IEEE 363 754-2008, DOI 10.1109/IEEESTD.2008.4610935, 2008, 364 . 367 6.2. Informative References 369 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 370 Requirement Levels", RFC 2119, March 1997. 372 [RFC8126] Cotton,M. and Leiba,B., and Narten T., "Guidelines for 373 Writing an IANA Considerations Section in RFCs", RFC 8126, 374 June 2017. 376 [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching 377 (GMPLS) Architecture", RFC 3945, October 2004. 379 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 380 Networks", RFC 5920, July 2010. 382 [G.827] ITU-T Recommendation, "Availability performance parameters 383 and objectives for end-to-end international constant bit- 384 rate digital paths", September 2003. 386 [F.1703] ITU-R Recommendation, "Availability objectives for real 387 digital fixed wireless links used in 27 500 km 388 hypothetical reference paths and connections", January 389 2005. 391 [P.530] ITU-R Recommendation," Propagation data and prediction 392 methods required for the design of terrestrial line-of- 393 sight systems", February 2012 395 [EN 302 217] ETSI standard, "Fixed Radio Systems; Characteristics 396 and requirements for point-to-point equipment and 397 antennas", April 2009 399 [RFC8330] H., Long, M., Ye, Mirsky, G., Alessandro, A., Shah, H., 400 "OSPF Traffic Engineering (OSPF-TE) Link Availability 401 Extension for Links with Variable Discrete Bandwidth", 402 RFC8330, February 2018 404 7. Appendix: Bandwidth Availability Example 406 In a mobile backhaul network, microwave links are very popular for 407 providing connections of last hops. In case of heavy rain 408 conditions, to maintain the link connectivity, the microwave link 409 may lower the modulation level since moving to a lower modulation 410 level provides for a lower Signal-to-Noise Ratio (SNR) requirement. 411 This is called adaptive modulation technology [EN 302 217]. However, 412 a lower modulation level also means lower link bandwidth. When link 413 bandwidth is reduced because of modulation down-shifting, high- 414 priority traffic can be maintained, while lower-priority traffic is 415 dropped. Similarly, copper links may change their link bandwidth due 416 to external interference. 418 Presuming that a link has three discrete bandwidth levels: 420 The link bandwidth under modulation level 1, e.g., QPSK, is 100 421 Mbps; 423 The link bandwidth under modulation level 2, e.g., 16QAM, is 200 424 Mbps; 426 The link bandwidth under modulation level 3, e.g., 256QAM, is 400 427 Mbps. 429 On a sunny day, the modulation level 3 can be used to achieve 400 430 Mbps link bandwidth. 432 A light rain with X mm/h rate triggers the system to change the 433 modulation level from level 3 to level 2, with bandwidth changing 434 from 400 Mbps to 200 Mbps. The probability of X mm/h rain in the 435 local area is 52 minutes in a year. Then the dropped 200 Mbps 436 bandwidth has 99.99% availability. 438 A heavy rain with Y(Y>X) mm/h rate triggers the system to change the 439 modulation level from level 2 to level 1, with bandwidth changing 440 from 200 Mbps to 100 Mbps. The probability of Y mm/h rain in the 441 local area is 26 minutes in a year. Then the dropped 100 Mbps 442 bandwidth has 99.995% availability. 444 For the 100M bandwidth of the modulation level 1, only the extreme 445 weather condition can cause the whole system to be unavailable, 446 which only happens for 5 minutes in a year. So the 100 Mbps 447 bandwidth of the modulation level 1 owns the availability of 448 99.999%. 450 There are discrete buckets per availability level. Under the worst 451 weather conditions, there's only 100 Mbps capacity and that's 452 99.999% available. It's treated as effectively "always available" 453 since there's no way to do any better. If the weather is bad but not 454 the worst weather, modulation level 2 can be used, which gets an 455 additional 100 Mbps bandwidth (i.e., 200 Mbps total), so there are 456 100 Mbps in the 99.999% bucket and 100 Mbps in the 99.995% bucket. 457 In clear weather, modulate level 3 can be used to get 400 Mbps 458 total, but that's only 200 Mbps more than at modulation level 2, so 459 99.99% bucket has that "extra" 200 Mbps, and the other two buckets 460 still have their 100 Mbps each. 462 Therefore, the maximum bandwidth is 400 Mbps. According to the 463 weather condition, the sub-bandwidth and its availability are shown 464 as follows: 466 Sub-bandwidth (Mbps) Availability 468 ------------------ ------------ 470 200 99.99% 472 100 99.995% 474 100 99.999% 476 8. Acknowledgments 478 The authors would like to thank Deborah Brungard, Khuzema Pithewan, 479 Lou Berger, Yuji Tochio, Dieter Beller, and Autumn Liu for their 480 comments and contributions on the document. 482 Authors' Addresses 484 Hao Long 485 Huawei Technologies Co., Ltd. 486 No.1899, Xiyuan Avenue, Hi-tech Western District 487 Chengdu 611731, P.R.China 489 Phone: +86-18615778750 490 Email: longhao@huawei.com 492 Min Ye (editor) 493 Huawei Technologies Co., Ltd. 494 No.1899, Xiyuan Avenue, Hi-tech Western District 495 Chengdu 611731, P.R.China 497 Email: amy.yemin@huawei.com 499 Greg Mirsky (editor) 500 ZTE 502 Email: gregimirsky@gmail.com 504 Alessandro D'Alessandro 505 Telecom Italia S.p.A 507 Email: alessandro.dalessandro@telecomitalia.it 509 Himanshu Shah 510 Ciena Corp. 511 3939 North First Street 512 San Jose, CA 95134 513 US 515 Email: hshah@ciena.com