idnits 2.17.1 draft-geng-detnet-info-distribution-00.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 13, 2017) is 2601 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-00 ** Obsolete normative reference: RFC 7810 (Obsoleted by RFC 8570) -- Obsolete informational reference (is this intentional?): RFC 5316 (Obsoleted by RFC 9346) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Interdomain Routing Working Group X. Geng 3 Internet-Draft M. Chen 4 Intended status: Experimental Huawei 5 Expires: September 14, 2017 March 13, 2017 7 IGP-TE Extensions for DetNet Information Distribution 8 draft-geng-detnet-info-distribution-00 10 Abstract 12 There are requirements in diverse industries to establish multi-hop 13 paths for characterized flows with bounded end-to-end latency and 14 extremely low packet loss rate. Deterministic Networking (DetNet) 15 can provide service satisfying the requirements. 17 This document describes extensions to IGP-TE, including OSPF-TE and 18 ISIS-TE to distribute information of DetNet, which can be used for 19 DetNet path computation/selection. 21 This document only covers the mechanisms by which DetNet information 22 is distributed. The mechanisms for measuring, calculating or 23 configuring DetNet capabilities, resources and other relevant 24 parameters are out of the scope. 26 Requirements Language 28 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 29 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 30 document are to be interpreted as described in RFC 2119 [RFC2119]. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on September 14, 2017. 49 Copyright Notice 51 Copyright (c) 2017 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 3. DetNet Extensions to OSPF TE . . . . . . . . . . . . . . . . 4 69 3.1. Congestion Protection Method sub-TLV . . . . . . . . . . 4 70 3.2. Maximum DetNet Reservable Bandwidth sub-TLV . . . . . . . 5 71 3.3. Available DetNet Bandwidth sub-TLV . . . . . . . . . . . 6 72 3.4. Min/Max Queuing Delay sub-TLV . . . . . . . . . . . . . . 6 73 4. DetNet Extensions to ISIS TE . . . . . . . . . . . . . . . . 7 74 4.1. Congestion Protection Method . . . . . . . . . . . . . . 7 75 4.2. Maximum DetNet Reservable Bandwidth . . . . . . . . . . . 8 76 4.3. Available DetNet Bandwidth . . . . . . . . . . . . . . . 9 77 4.4. Min/Max Queuing Delay . . . . . . . . . . . . . . . . . . 9 78 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 79 5.1. Sub-TLVs for Link TLV . . . . . . . . . . . . . . . . . . 10 80 5.2. Sub-TLVs for TLVs 22, 23, 141, 222, and 223 . . . . . . . 10 81 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 82 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 83 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 84 8.1. Normative References . . . . . . . . . . . . . . . . . . 11 85 8.2. Informative References . . . . . . . . . . . . . . . . . 11 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 88 1. Introduction 90 There are many use cases from diverse industries which have the need 91 in common for deterministic service, for example: audio video 92 production, industrial process control and mobile access networks. 93 The requirements can be summarized as: 95 Deterministic minimum and maximum end-to-end latency from source 96 to destination 97 Extremely low packet loss rate 99 Deterministic Networking (DetNet) can satisfy the requirements by the 100 following techniques: 102 o Congestion Protection by reserving data plane resources for DetNet 103 flows in intermediate nodes along the path 105 o Explicit Route that do not rapidly change with the network 106 topology 108 o Seamless Redundant which can distribute DetNet flow packets over 109 multi paths to ensure delivery of each packet spite of the loss of 110 a path 112 To make the above techniques work, it's necessary to know the 113 capabilities (e.g., DetNet capable or not, which congestion 114 protection algorithms are supported, etc.), resources (e.g, dedicated 115 bandwidth for DetNet, buffers, etc.), performance (e.g., 116 device/queue/link delay etc.) and other relevant information of each 117 DetNet capable node. Then, a DetNet path computation element (e.g., 118 PCE or ingress of a DetNet flow) can use these information to compute 119 a path that satisfies the requirement of a specific DetNet flow. 120 Specifically, according to the requirements stated in DetNet 121 architecture, the information should include: 123 o Whether a node is DetNet capable 125 o Congestion protection methods supported by a DetNet capable node; 127 o Dedicated bandwidth for DetNet flows; 129 o Device and link delay; 131 Some of information (e.g., Link delay/loss ) can be distributed and 132 collected through the Traffic Engineering (TE) metric extensions 133 [RFC7471], [RFC7810]. 135 This document defines extensions to OSPF and ISIS to distribute the 136 above DetNet information that can not distributed by the existing 137 protocols. 139 2. Terminology 141 All the DetNet related terminologies used in this document conform to 142 the DetNet architecture [I-D.ietf-detnet-architecture]. 144 3. DetNet Extensions to OSPF TE 146 This document defines new OSPF TE sub-TLVs for Link TLV to distribute 147 the DetNet required information as stated in Section 1. These sub- 148 TLVs includes: 150 ______________________________________________________________ 151 | Type | Length | Value | 152 -------------------------------------------------------------- 153 | TBD1 | 4 | Congestion Control Method | 154 | TBD2 | 4 | Max DetNet Reservable Bandwidth | 155 | TBD3 | 4 | Available DetNet Bandwidth | 156 | TBD4 | 8 | Min/Max Queuing Delay | 157 |________|_______________|___________________________________| 159 3.1. Congestion Protection Method sub-TLV 161 This Congestion Protection (CP) Method sub-TLV is used to advertise 162 the DetNet flow congestion protection methods used in transit nodes. 163 It may be required by some DetNet flows that all the transit nodes 164 along the path SHOULD use the same congestion protection method. 165 Some typical congestion protection methods are listed as below: 167 Time Aware Shaping [IIEEE802.1Qbv] 169 Credit Based Shaper [IEEE802.1Q-2014] 171 Cyclic Queuing and Forwarding [IEEE802.1Qch] 173 Asynchronous Traffic Shaping [IEEE802.1Qcr] 175 The format of this sub-TLV is shown in the following diagram: 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | Type (TBD1) | Length(4) | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | RESERVED | CP Methods | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 The Type field is 2 octets in length, and the value is TBD1. 187 The Length field is 2 octets in length and its value is 4. 189 The RESERVED field is reserved for future use. It MUST be set to 0 190 when sent and MUST be ignored when received. 192 This Congestion Control Method field presents the congestion 193 protection method used in the transit node. 195 Five congestion protection methods are introduced in this document: 197 _______________________________________________________________ 198 | Value | Congestion Control Mechanisms | 199 --------------------------------------------------------------- 200 | 0 | Reserved | 201 | 1 | Time Aware Shaper | 202 | 2 | Credit Based Shaper | 203 | 3 | Time Aware Shaper and Credit Based Shaper | 204 | 4 | Cyclic Queuing and Forwarding | 205 | 5 | Asynchronous Traffic Shaping | 206 | 6-254 | Unassigned | 207 | 255 | Reserved | 208 |___________|_________________________________________________| 210 3.2. Maximum DetNet Reservable Bandwidth sub-TLV 212 This sub-TLV specifies the maximum amount of bandwidth that is 213 reserved for DetNet on this link. Note that this value SHOULD be 214 smaller than the value of Maximum Reservable Bandwidth sub-TLV 215 [RFC3630]. The value normally depends on the Congestion Protection 216 Method and is user-configurable. In some particular Congestion 217 Protection Method (e.g. Credit Based shaper in AVB), this value will 218 affect the calculation of maximum queuing delay of the DetNet flow. 219 The units are bytes per second. 221 The format of this sub-TLV is shown in the following diagram: 223 0 1 2 3 224 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 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 | Type(TBD2) | Length(4) | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 | RESERVED | Maximum DetNet Reservable Bandwidth | 229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 The Type field is 2 octets in length, and the value is TBD2. 233 The Length field is 2 octets in length and its value is 4. 235 The RESERVED field is reserved for future use. It MUST be set to 0 236 when sent and MUST be ignored when received. 238 This Maximum DetNet Reservable Bandwidth presents the maximum 239 bandwidth that may be reserved for DetNet. 241 3.3. Available DetNet Bandwidth sub-TLV 243 This sub-TLV specifies the available bandwidth that can be reserved 244 for DetNet flow on this link for now. Considering that there is no 245 generally accepted DetNet traffic classification, this value contains 246 all the available DetNet Bandwidth from different DetNet traffic 247 classes (if there is any), which differs from the Unreserved 248 Bandwidth defined in [RFC3630]. 250 The format of this sub-TLV is shown in the following diagram: 252 0 1 2 3 253 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 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | (Type)TBD3 | (Length)4 | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | RESERVED | Available DetNet Bandwidth | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 The Type field is 2 octets in length, and the value is TBD3. 262 The Length field is 2 octets in length and its value is 4. 264 The RESERVED field is reserved for future use. It MUST be set to 0 265 when sent and MUST be ignored when received. 267 This Available DetNet Bandwidth field presents the available 268 bandwidth for DetNet in this link. 270 3.4. Min/Max Queuing Delay sub-TLV 272 [Editor Notes: more consideration and inputs are needed for these 273 queue delays] 275 This sub-TLV advertises the minimum and maximum queuing delay values 276 of specific DetNet flow in the link. Max/Min Unidirectional Link 277 Delay Sub-TLV [RFC7471] excludes the queuing delay because of its 278 instability. With the techniques used in DetNet, the queuing delay 279 can be limited to a reasonable range, which means that the queuing 280 delay bound is stable enough to be defined as a sub-TLV and 281 advertised over the network. 283 The format of this sub-TLV is shown in the following diagram: 285 0 1 2 3 286 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 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | (Type)TBD4 | (Length)8 | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | RESERVED | Minimum DetNet Queuing Delay | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 | RESERVED | Maximum DetNet Queuing Delay | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 The Type field is 2 octets in length, and the value is TBD4. 297 The Length field is 2 octets in length and its value is 4. 299 The RESERVED field is reserved for future use. It MUST be set to 0 300 when sent and MUST be ignored when received. 302 Minimum DetNet Queuing Delay is 24-bit field carrying minimum queuing 303 delay value (in microseconds) encoded as an integer value. 304 Implementations may also add this to the value of Min Delay 305 Unidirectional Link Delay Sub-TLV [RFC7471] in order to advertise the 306 minimum delay of this link. Min Queuing Delay can be the same with 307 the Max Queuing Delay. 309 The RESERVED field is reserved for future use. It MUST be set to 0 310 when sent and MUST be ignored when received. 312 Maximum DetNet Queuing Delay is 24-bit field carrying the maximum 313 queuing delay value (in microseconds) encoded as an integer value. 314 Implementations may also add this to the value of Max Delay 315 Unidirectional Link Delay Sub-TLV [RFC7471]to order to advertise the 316 maximum delay of this link. 318 4. DetNet Extensions to ISIS TE 320 This document defines new IS-IS TE sub-TLVs that can be announced in 321 the TLVs 22, 23, 141, 222, and 223 in order to distribute DetNet 322 information. The sub-TLV extensions below build on the ones provided 323 in [RFC5305], [RFC5316]and [RFC7310]. 325 4.1. Congestion Protection Method 327 This Congestion Protection (CP) Method sub-TLV is used to advertise 328 the DetNet flow congestion protection methods used in transit nodes. 329 The reader can know more about this sub-TLV referring to section 3.1. 331 The format of this sub-TLV is shown in the following diagram: 333 0 1 2 3 334 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 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Type(TBD5) | Length(4) | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | RESERVED | Congestion Control Method | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 The Type field is 1 octet in length, and the value is TBD5. 343 The Length field is 1 octet in length and its value is 4. 345 The RESERVED field is reserved for future use. It MUST be set to 0 346 when sent and MUST be ignored when received. 348 This Congestion Control Method field presents the congestion 349 protection method used in the transit node. 351 Five congestion protection methods are introduced in this document: 353 4.2. Maximum DetNet Reservable Bandwidth 355 This sub-TLV specifies the maximum amount of bandwidth that is 356 reserved for DetNet on this link. Note that this value SHOULD be 357 smaller than the value of Maximum Reservable Link Bandwidth 358 [RFC5305]. The reader can know more about this sub-TLV referring to 359 section 3.2. 361 The format of this sub-TLV is shown in the following diagram: 363 0 1 2 3 364 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 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | Type(TBD6) | Length(4) | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | RESERVED | Maximum DetNet Reservable Bandwidth | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 The Type field is 1 octet in length, and the value is TBD6. 373 The Length field is 1 octet in length and its value is 4. 375 The RESERVED field is reserved for future use. It MUST be set to 0 376 when sent and MUST be ignored when received. 378 This Maximum DetNet Reservable Bandwidth presents the maximum 379 bandwidth that may be reserved for DetNet. 381 4.3. Available DetNet Bandwidth 383 This sub-TLV specifies the available bandwidth that can be reserved 384 for DetNet flow on this link for now. It is different from the 385 Unreserved Bandwidth sub-TLV defined in [RFC5305] referring to 386 section 3.3. 388 The format of this sub-TLV is shown in the following diagram: 390 0 1 2 3 391 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 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 | Type(TBD7) | Length(4) | 394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 395 | RESERVED | Available DetNet Bandwidth | 396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 398 The Type field is 1 octet in length, and the value is TBD7. 400 The Length field is 1 octet in length and its value is 4. 402 The RESERVED field is reserved for future use. It MUST be set to 0 403 when sent and MUST be ignored when received. 405 This Available DetNet Bandwidth field presents the available 406 bandwidth for DetNet in this link. 408 4.4. Min/Max Queuing Delay 410 The reader can know more about this sub-TLV referring to section 3.4. 412 The format of this sub-TLV is shown in the following diagram: 414 0 1 2 3 415 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 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Type(TBD8) | Length(4) | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | RESERVED | Minimum DetNet Queuing Delay | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | RESERVED | Maximum DetNet Queuing Delay | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 The Type field is 1 octet in length, and the value is TBD4. 426 The Length field is 1 octet in length and it's value is 4. 428 The RESERVED field is reserved for future use. It MUST be set to 0 429 when sent and MUST be ignored when received. 431 Minimum DetNet Queuing Delay is 24-bit field carrying minimum queuing 432 delay value (in microseconds) encoded as an integer value. 433 Implementations may also add this to the value of Min Unidirectional 434 Link Delay [RFC7810] in order to advertise the minimum delay of this 435 link. Min Queuing Delay can be the same with the Max Queuing Delay. 437 The RESERVED field is reserved for future use. It MUST be set to 0 438 when sent and MUST be ignored when received. 440 Maximum DetNet Queuing Delay is 24-bit field carrying the maximum 441 queuing delay value (in microseconds) encoded as an integer value. 442 Implementations may also add this to the value of Max Delay 443 Unidirectional Link Delay Sub-TLV [RFC7810] to order to advertise the 444 maximum delay of this link. 446 5. IANA Considerations 448 5.1. Sub-TLVs for Link TLV 450 IANA is requested to register the OSPF sub-TLVs defined in this 451 document in the sub-TLVs for Link TLV registry. 453 Type Description 454 ---- ------------------------------ 455 TBD1 Congestion Protection Method 456 TBD2 Maximum DetNet Reservable Bandwidth 457 TBD3 Available DetNet Bandwidth 458 TBD4 Min/Max Queuing Delay 460 5.2. Sub-TLVs for TLVs 22, 23, 141, 222, and 223 462 IANA is requested to register the ISIS sub-TLVs defined in this 463 document in the Sub-TLVs for TLVs 22, 23, 141, 222, and 223 registry. 465 Type Description 466 ---- ------------------------------ 467 TBD5 Congestion Protection Method 468 TBD6 Maximum DetNet Reservable Bandwidth 469 TBD7 Available DetNet Bandwidth 470 TBD8 Min/Max Queuing Delay 472 6. Security Considerations 474 This document does not introduce security issues beyond those 475 discussed in [RFC7471] and [RFC7810]. 477 7. Acknowledgements 479 8. References 481 8.1. Normative References 483 [I-D.ietf-detnet-architecture] 484 Finn, N. and P. Thubert, "Deterministic Networking 485 Architecture", draft-ietf-detnet-architecture-00 (work in 486 progress), September 2016. 488 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 489 Requirement Levels", BCP 14, RFC 2119, 490 DOI 10.17487/RFC2119, March 1997, 491 . 493 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 494 Previdi, "OSPF Traffic Engineering (TE) Metric 495 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 496 . 498 [RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and 499 Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", 500 RFC 7810, DOI 10.17487/RFC7810, May 2016, 501 . 503 8.2. Informative References 505 [IEEE802.1Q-2014] 506 "MAC Bridges and VLANs (IEEE 802.1Q-2014)", 2014. 508 [IEEE802.1Qch] 509 "Cyclic Queuing and Forwarding", 2016. 511 [IEEE802.1Qcr] 512 "Asynchronous Traffic Shaping", 2016. 514 [IIEEE802.1Qbv] 515 "Enhancements for Scheduled Traffic", 2016. 517 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 518 (TE) Extensions to OSPF Version 2", RFC 3630, 519 DOI 10.17487/RFC3630, September 2003, 520 . 522 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 523 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 524 2008, . 526 [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in 527 Support of Inter-Autonomous System (AS) MPLS and GMPLS 528 Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, 529 December 2008, . 531 [RFC7310] Lindsay, J. and H. Foerster, "RTP Payload Format for 532 Standard apt-X and Enhanced apt-X Codecs", RFC 7310, 533 DOI 10.17487/RFC7310, July 2014, 534 . 536 Authors' Addresses 538 Xuesong Geng 539 Huawei 541 Email: gengxuesong@huawei.com 543 Mach(Guoyi) Chen 544 Huawei 546 Email: mach.chen@huawei.com