idnits 2.17.1 draft-geng-detnet-info-distribution-03.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 (October 22, 2018) is 2013 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) == Outdated reference: A later version (-04) exists of draft-finn-detnet-bounded-latency-01 ** Downref: Normative reference to an Informational draft: draft-finn-detnet-bounded-latency (ref. 'I-D.finn-detnet-bounded-latency') == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-08 ** Obsolete normative reference: RFC 7810 (Obsoleted by RFC 8570) -- Obsolete informational reference (is this intentional?): RFC 5316 (Obsoleted by RFC 9346) Summary: 2 errors (**), 0 flaws (~~), 3 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: Standards Track Huawei 5 Expires: April 25, 2019 Z. Li 6 China Mobile 7 October 22, 2018 9 IGP-TE Extensions for DetNet Information Distribution 10 draft-geng-detnet-info-distribution-03 12 Abstract 14 This document extends the IGP-TE, including OSPF-TE and ISIS-TE, to 15 support DetNet by specifying new information that can be placed in 16 Link State Protocol Data Units (LSP). This information describes 17 additional details regarding the state of the network that are useful 18 for DetNet computations. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 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). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on April 25, 2019. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. DetNet Extensions to OSPF TE . . . . . . . . . . . . . . . . 4 63 3.1. DetNet Node Attributes Advertisement . . . . . . . . . . 4 64 3.1.1. Packet Processing Delay Sub-TLV . . . . . . . . . . . 4 65 3.1.2. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 5 66 3.2. DetNet Link Attributtes Advertisement . . . . . . . . . . 6 67 3.2.1. Max DetNet Reservable Bandwidth Sub-TLV . . . . . . . 7 68 3.2.2. DetNet Available Bandwidth Sub-TLV . . . . . . . . . 7 69 3.2.3. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 8 70 3.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 9 71 3.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 10 72 4. DetNet Extensions to ISIS TE . . . . . . . . . . . . . . . . 12 73 4.1. DetNet Node Attributes Advertisement . . . . . . . . . . 12 74 4.1.1. DetNet Processing Delay Sub-TLV . . . . . . . . . . . 12 75 4.1.2. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 13 76 4.2. DetNet Link Attributes Advertisement . . . . . . . . . . 14 77 4.2.1. Max DetNet Reservable Bandwidth Sub-TLV . . . . . . . 14 78 4.2.2. DetNet Available Bandwidth Sub-TLV . . . . . . . . . 15 79 4.2.3. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 16 80 4.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 16 81 4.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 17 82 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 83 5.1. Sub-TLVs for OSPF Node Attribute TLV . . . . . . . . . . 19 84 5.2. Sub-TLVs for OSPF Link TLV . . . . . . . . . . . . . . . 19 85 5.3. Sub-TLVs for ISIS Router Capability TLV . . . . . . . . . 20 86 5.4. Sub-TLVs for IS-IS TLVs 22, 23, 141, 222, and 223 . . . 20 87 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 88 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 89 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 90 8.1. Normative References . . . . . . . . . . . . . . . . . . 20 91 8.2. Informative References . . . . . . . . . . . . . . . . . 21 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 94 1. Introduction 96 There are many use cases from diverse industries which have the need 97 in common for deterministic service, for example: audio video 98 production, industrial process control and mobile access networks. 99 The requirements can be summarized as: 101 Deterministic minimum and maximum end-to-end latency from source 102 to destination 104 Extremely low packet loss rate 106 Deterministic Networking (DetNet) can satisfy the requirements by the 107 following techniques: 109 o Congestion Protection by reserving data plane resources for DetNet 110 flows in intermediate nodes along the path 112 o Explicit Route that do not rapidly change with the network 113 topology 115 o Seamless Redundant which can distribute DetNet flow packets over 116 multi paths to ensure delivery of each packet spite of the loss of 117 a path 119 To make the above techniques work, it's necessary to know the 120 capabilities (e.g., DetNet capable or not, which congestion 121 protection algorithms are supported, etc.), resources (e.g, dedicated 122 bandwidth for DetNet, buffers, etc.), performance (e.g., 123 device/queue/link delay etc.) and other relevant information of each 124 DetNet capable node. Then, a DetNet path computation element (e.g., 125 PCE or ingress of a DetNet flow) can use these information to compute 126 a path that satisfies the requirement of a specific DetNet flow. 127 Specifically, according to the requirements stated in DetNet 128 architecture, the information should include: 130 o Bandwidth related attributes (e.g., bandwidth reserved for 131 DetNet); 133 o Buffer/queue management related attributes (e.g., queue management 134 algorithm, etc.); 136 o PREOF (Packet Replication, Ordering and Elimination Function) 137 capabilities and parameters (e.g., maximum out-of-order packets, 138 etc.); 140 o Delay related attributes (e.g., node processing delay, queuing 141 delay, link delay, etc.); 143 This document defines extensions to OSPF and ISIS to distribute the 144 above DetNet information at node and/or link granularity. 146 Some of information (e.g., Link delay/loss ) can be distributed and 147 collected through Traffic Engineering (TE) metric extensions 148 [RFC7471] and [RFC7810], which are not covered by this document. 150 2. Terminology 152 All the DetNet related terminologies used in this document conform to 153 the DetNet architecture [I-D.ietf-detnet-architecture]. 155 3. DetNet Extensions to OSPF TE 157 This document defines an extension to OSPF used to advertise DetNet 158 information. 160 3.1. DetNet Node Attributes Advertisement 162 New OSPF DetNet sub-TLVs for Node Attribute TLV[RFC5786] are defined 163 to distribute the DetNet information of a node. These sub-TLVs 164 include: 166 ______________________________________________________________ 167 | Type | Length | Value | 168 |------------------------------------------------------------| 169 | TBD1 | 8 | DetNet Processing Delay | 170 | TBD4 | 4 | PREOF Capability | 171 |________|_______________|___________________________________| 173 3.1.1. Packet Processing Delay Sub-TLV 175 In the scope of DetNet, packet processing delay, which begins after 176 the packet goes into the input port and ends before the packet 177 arrives the output buffer, can expected in a known range, and the 178 value of the delay bound is specified in this sub-TLV, including: 180 o Maximum DetNet packet processing delay 182 o Minimum DetNet packet processing delay 184 o Maximum DetNet packet processing delay variation 186 The format of this sub-TLV is shown in the following diagram: 188 0 1 2 3 189 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 2 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | Type(TBD1) | Length(8) | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | RESERVED | Minimum DetNet Processing Delay | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | RESERVED | Maximum DetNet Processing Delay | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | RESERVED | Maximum DetNet Processing Delay Variation | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 The Type field is 2 octets in length, and the value is TBD1. 202 The Length field is 2 octets in length and its value is 8. 204 The RESERVED field is reserved for future use. It MUST be set to 0 205 when sent and MUST be ignored when received. 207 The Minimum DetNet Processing Delay field is 3 octets, and presents 208 the minimum delay for a DetNet flow in the device, excluding the 209 queuing delay in output port. The units are microsecond. 211 The Maximum DetNet Processing Delay field is 3 octets, and presents 212 the maximum delay for a DetNet flow in the device, excluding the 213 queuing delay in output port. The units are microsecond. 215 The Maximum DetNet Processing Delay Variation field is 3 octets in 216 length, and presents the maximum delay variation for a DetNet flow in 217 the device, excluding the queuing delay in output port. The units 218 are microsecond. 220 3.1.2. PREOF Capability Sub-TLV 222 PREOF (Packet Replication/Elimination/Ordering Function) is for 223 DetNet service protection, which includes: 225 o In-order delivery function: defined in Section 3.2.2.1 of 226 [I-D.ietf-detnet-architecture] 228 o Packet replication function: defined in Section 3.2.2.2 of 229 [I-D.ietf-detnet-architecture] 231 o Packet elimination function: defined in Section 3.2.2.3 of 232 [I-D.ietf-detnet-architecture] 234 This sub-TLV specifies a set of PREOF capabilities and relevant 235 parameters at node granularity. PREOF can also be advertised as Link 236 attribute (section 3.2.3), when not all of the ports in the node 237 support PREOF. 239 The format of this sub-TLV is shown in the following diagram: 241 0 1 2 3 242 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 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 | Type(TBD4) | Length(4) | 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 | Flags | Maximum out-of-order Packet Number | 247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 The Type field is 2 octets in length, and the value is TBD4. 251 The Length field is 2 octets in length and its value is 4. 253 The Flags field is 1 octet in length, and it is designed as follows: 255 0 1 2 3 4 5 6 7 8 256 +-+-+-+-+-+-+-+-+ 257 |R|E|O| | 258 +-+-+-+-+-+-+-+-+ 260 where: 262 o R-flag: replication-capability flag, which indicates whether a 263 link has the packet replication capability. 265 o E-flag: elimination-capability flag, which indicates whether a 266 link has the packet elimination capability 268 o O-flag: in-order-capability, which indicates whether a LTP has the 269 in-order delivery capability 271 Maximum out-of-order Packet Number field is 3 octet in length, and 272 presents the maximum number of out-of-order packets that this link 273 can support, it depends on the reserved buffer size for packet 274 reordering. This value is valid only when the O-flag is set. 276 3.2. DetNet Link Attributtes Advertisement 278 New OSPF DetNet sub-TLVs for Link TLV are defined to distribute 279 DetNet information of a link. These sub-TLVs include: 281 ______________________________________________________________ 282 | Type | Length | Value | 283 |------------------------------------------------------------| 284 | TBD2 | 4 | Max DetNet Reservable Bandwidth | 285 | TBD3 | 4 | DetNet Available Bandwidth | 286 | TBD4 | 4 | PREOF Capability | 287 | TBD5 | 4 | Queuing Algorithm Capabilities | 288 | TBD6 | 10 | Queue Parameters | 289 |________|_______________|___________________________________| 291 3.2.1. Max DetNet Reservable Bandwidth Sub-TLV 293 This sub-TLV specifies the maximum amount of bandwidth that is 294 reserved for DetNet on this link. Note that this value SHOULD be 295 smaller than the value of Maximum Reservable Bandwidth sub-TLV 296 [RFC3630]. The value normally depends on the queuing management 297 algorithm and is user-configurable. In some particular queuing 298 management algorithm (e.g. Credit Based shaper in AVB), this value 299 will affect the calculation of maximum queuing delay of the DetNet 300 flow. The units are bytes per second. 302 The format of this sub-TLV is shown in the following diagram: 304 0 1 2 3 305 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 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | Type(TBD2) | Length(4) | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 | RESERVED | Maximum DetNet Reservable Bandwidth | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 The Type field is 2 octets in length, and the value is TBD2. 314 The Length field is 2 octets in length and its value is 4. 316 The RESERVED field is reserved for future use. It MUST be set to 0 317 when sent and MUST be ignored when received. 319 This Maximum DetNet Reservable Bandwidth field is 3 octets in length, 320 and presents the maximum bandwidth that may be reserved for DetNet. 321 The units are bytes per second. 323 3.2.2. DetNet Available Bandwidth Sub-TLV 325 This sub-TLV specifies the available bandwidth that can be reserved 326 for DetNet flow on this link for now. Considering that there is no 327 generally accepted DetNet traffic classification, this value contains 328 all the available DetNet Bandwidth from different DetNet traffic 329 classes (if there is any), which differs from the Unreserved 330 Bandwidth defined in [RFC3630]. 332 The format of this sub-TLV is shown in the following diagram: 334 0 1 2 3 335 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 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Type(TBD3) | Length(4) | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | RESERVED | Available DetNet Bandwidth | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 The Type field is 2 octets in length, and the value is TBD3. 344 The Length field is 2 octets in length and its value is 4. 346 The RESERVED field is reserved for future use. It MUST be set to 0 347 when sent and MUST be ignored when received. 349 This Available DetNet Bandwidth field is 3 octets in length, and 350 presents the available bandwidth for DetNet in this link. The units 351 are bytes per second. 353 3.2.3. PREOF Capability Sub-TLV 355 PREOF (Packet Replication/Elimination/Ordering Function) is for 356 DetNet service protection, which includes : 358 o In-order delivery function: defined in Section 3.2.2.1 of 359 [I-D.ietf-detnet-architecture] 361 o Packet replication function: defined in Section 3.2.2.2 of 362 [I-D.ietf-detnet-architecture] 364 o Packet elimination function: defined in Section 3.2.2.3 of 365 [I-D.ietf-detnet-architecture] 367 This sub-TLV specifies a set of PREOF capabilities and relevant 368 parameters at link granularity. PREOF can also be advertised as node 369 attribute (section 3.1.2), when all of the ports in the node support 370 PREOF. 372 The format of this sub-TLV is shown in the following diagram: 374 0 1 2 3 375 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 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Type(TBD4) | Length(4) | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 379 | Flags | Maximum out-of-order Packet Number | 380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 The Type field is 2 octets in length, and the value is TBD4. 384 The Length field is 2 octets in length and its value is 4. 386 The Flags field is 1 octet in length, and it is designed as follows: 388 0 1 2 3 4 5 6 7 8 389 +-+-+-+-+-+-+-+-+ 390 |R|E|O| | 391 +-+-+-+-+-+-+-+-+ 393 where: 395 o R-flag: replication-capability flag, which indicates whether a 396 link has the packet replication capability. 398 o E-flag: elimination-capability flag, which indicates whether a 399 link has the packet elimination capability 401 o O-flag: in-order-capability, which indicates whether a LTP has the 402 in-order delivery capability 404 Maximum out-of-order Packet Number field is 3 octet in length, and 405 presents the maximum number of out-of-order packets that this link 406 can support, it depends on the reserved buffer size for packet 407 reordering. This value is valid only when the O-flag is set. 409 3.2.4. Queuing Algorithm Capability Sub-TLV 411 This sub-TLV specifies queuing management algorithms capabilities to 412 gaurante bounded queuing latency [I-D.finn-detnet-bounded-latency]. 414 The format of this sub-TLV is shown in the following diagram: 416 0 1 2 3 417 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 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | Type(TBD5) | Length(4) | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Flags | RESERVED | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 The Type field is 2 octets in length, and the value is TBD5. 426 The Length field is 2 octets in length and its 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 The Flags field is 1 octet in length, and it is designed as follows: 433 0 1 2 3 4 5 6 7 8 434 +-+-+-+-+-+-+-+-+ 435 |C|T|H|A| | 436 +-+-+-+-+-+-+-+-+ 438 where: 440 o C-flag: CBS flag, which indicates whether a link can support Time 441 Aware Shaping [IIEEE802.1Qbv]. 443 o T-flag: TAS flag, which indicuate whether a link can support 444 Credit Based Shaper [IEEE802.1Q-2014] 446 o H-flag: CQF flag, which indicuate whether a link can support 447 Cyclic Queuing and Forwarding [IEEE802.1Qch] 449 o A-flag: ATS flag, which indicuate whether a link can support 450 Asynchronous Traffic Shaping [IEEE802.1Qcr] 452 3.2.5. DetNet Queue Sub-TLV 454 In the context of DetNet, the delay of queuing is bounded, and the 455 bound depends on what queuing management method is used and how many 456 buffers are allocated. This sub-TLV specifies the DetNet queue 457 parameters. 459 The format of this sub-TLV is shown in the following diagram: 461 0 1 2 3 462 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 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 | Type(TBD6) | Length(10) | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | Queue Identifier | Queue Buffer Size | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 468 | Flags | Maximum Queuing Delay | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 | RESERVED | Minimum Queuing Delay | 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | RESERVED | Maximum Queuing Delay Variation | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 475 The Type field is 2 octets in length, and the value is TBD6. 477 The Length field is 2 octets in length and its value is 10. 479 The Queue Identifier field is 3 octets in length, and specifies the 480 identifier of a queue. It could be an internal identifier that is 481 only used within a node. Or it could be used by a centralized 482 controller to specify in which specific queue a flow/packet is 483 required to enter. 485 The Queue Buffer Size field is 3 octets in length, and specifies the 486 size of a queue with unit of bytes. 488 The Flags field is 1 octet in length, and it is designed as follows: 490 0 1 2 3 4 5 6 7 8 491 +-+-+-+-+-+-+-+-+ 492 |C|T|H|A| | 493 +-+-+-+-+-+-+-+-+ 495 where: 497 o C-flag: CBS flag, which indicates whether a link can support Time 498 Aware Shaping [IIEEE802.1Qbv]. 500 o T-flag: TAS flag, which indicuate whether a link can support 501 Credit Based Shaper [IEEE802.1Q-2014] 503 o H-flag: CQF flag, which indicuate whether a link can support 504 Cyclic Queuing and Forwarding [IEEE802.1Qch] 506 o A-flag: ATS flag, which indicuate whether a link can support 507 Asynchronous Traffic Shaping [IEEE802.1Qcr] 509 The RESERVED field is reserved for future use. It MUST be set to 0 510 when sent and MUST be ignored when received. 512 Minimum Queuing Delay is 3 octets in length, and carries minimum 513 queuing delay value (in microseconds) encoded as an integer value. 514 Implementations may also add this to the value of Min Delay 515 Unidirectional Link Delay Sub-TLV [RFC7471] in order to advertise the 516 minimum delay of this link. Min Queuing Delay can be the same with 517 the Max Queuing Delay. 519 Maximum Queuing Delay is 3 octets in length, and carries the maximum 520 queuing delay value (in microseconds) encoded as an integer value. 521 Implementations may also add this to the value of Max Delay 522 Unidirectional Link Delay Sub-TLV [RFC7471]to order to advertise the 523 maximum delay of this link. 525 Maximum Queuing Delay variation is 3 octets in length, and carries 526 the maximum queuing delay variation value (in microseconds) encoded 527 as an integer value. 529 The RESERVED field is reserved for future use. It MUST be set to 0 530 when sent and MUST be ignored when received. 532 4. DetNet Extensions to ISIS TE 534 This document defines an extension to IS-IS used to advertise DetNet 535 information. 537 4.1. DetNet Node Attributes Advertisement 539 The DetNet node sub-TLVs are defined within the body of the IS-IS 540 Router Capability TLV [RFC7981] to carry DetNet information. 542 4.1.1. DetNet Processing Delay Sub-TLV 544 This sub-TLV specifies the DetNet packet porcessing parameters. The 545 reader can know more about this sub-TLV referring to section 3.1. 547 The format of this sub-TLV is shown in the following diagram: 549 0 1 2 3 550 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 2 551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 552 | Type(TBD7) | Length(8) | 553 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 554 | RESERVED | Minimum DetNet Processing Delay | 555 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 556 | RESERVED | Maximum DetNet Processing Delay | 557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 | RESERVED | Maximum DetNet Processing Delay Variation | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 The Type field is 1 octets in length, and the value is TBD7. 563 The Length field is 1 octets in length and its value is 8. 565 The RESERVED field is reserved for future use. It MUST be set to 0 566 when sent and MUST be ignored when received. 568 The Minimum DetNet Processing Delay is 3 octets in length and 569 presents the minimum delay for a DetNet flow in the device, excluding 570 the queuing delay in output port. The units are microsecond. 572 The Maximum DetNet Processing Delay is 3 octets in length and 573 presents the maximum delay for a DetNet flow in the device, excluding 574 the queuing delay in output port. The units are microsecond. 576 The Maximum DetNet Processing Delay Variation is 3 octets in length 577 and presents the maximum delay variation for a DetNet flow in the 578 device, excluding the queuing delay in output port. The units are 579 microsecond. 581 4.1.2. PREOF Capability Sub-TLV 583 This sub-TLV specifies a set of PREOF capabilities and relevant 584 parameters in sub-TLV. The reader can know more about this sub-TLV 585 referring to section 3.4. 587 The format of this sub-TLV is shown in the following diagram: 589 0 1 2 3 590 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 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | Type(TBD10) | Length(4) | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | Flags | Maximum out-of-order Packet Number | 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 597 The Type field is 1 octets in length, and the value is TBD10. 599 The Length field is 1 octets in length and its value is 4. 601 The Flags field is 1 octet in length, and it is designed as follows: 603 0 1 2 3 4 5 6 7 8 604 +-+-+-+-+-+-+-+-+ 605 |R|E|O| | 606 +-+-+-+-+-+-+-+-+ 608 where: 610 o R-flag: replication-capability flag, which indicates whether a 611 link has the packet replication capability. 613 o E-flag: elimination-capability flag, which indicates whether a 614 link has the packet elimination capability 616 o O-flag: in-order-capability, which indicates whether a LTP has the 617 in-order delivery capability 619 Maximum out-of-order Packet Number field is 3 octets in length and 620 presents the maximum number of out-of-order packets that this link 621 can support, it depends on the reserved buffer size for packet 622 reordering. This value is valid only when the O-flag is set. 624 4.2. DetNet Link Attributes Advertisement 626 This document defines new IS-IS TE sub-TLVs that can be announced in 627 the TLVs 22, 23, 141, 222, and 223 in order to distribute DetNet 628 information. The sub-TLV extensions below build on the ones provided 629 in [RFC5305], [RFC5316]and [RFC7310] 631 4.2.1. Max DetNet Reservable Bandwidth Sub-TLV 633 This sub-TLV specifies the maximum amount of bandwidth that is 634 reserved for DetNet on this link. Note that this value SHOULD be 635 smaller than the value of Maximum Reservable Link Bandwidth 636 [RFC5305]. The reader can know more about this sub-TLV referring to 637 section 3.2. 639 The format of this sub-TLV is shown in the following diagram: 641 0 1 2 3 642 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 643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 644 | Type(TBD8) | Length(4) | 645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 | RESERVED | Maximum DetNet Reservable Bandwidth | 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 The Type field is 1 octets in length, and the value is TBD8. 651 The Length field is 1 octets in length and its value is 4. 653 The RESERVED field is reserved for future use. It MUST be set to 0 654 when sent and MUST be ignored when received. 656 This Maximum DetNet Reservable Bandwidth field is 3 octets in length 657 and presents the maximum bandwidth that may be reserved for DetNet. 658 The units are bytes per second. 660 4.2.2. DetNet Available Bandwidth Sub-TLV 662 This sub-TLV specifies the available bandwidth that can be reserved 663 for DetNet flow on this link for now. It is different from the 664 Unreserved Bandwidth sub-TLV defined in [RFC5305] referring to 665 section 3.3. 667 The format of this sub-TLV is shown in the following diagram: 669 0 1 2 3 670 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 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | Type(TBD9) | Length(4) | 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 674 | RESERVED | Available DetNet Bandwidth | 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 The Type field is 1 octets in length, and the value is TBD9. 679 The Length field is 1 octets in length and its value is 4. 681 The RESERVED field is reserved for future use. It MUST be set to 0 682 when sent and MUST be ignored when received. 684 This Available DetNet Bandwidth field is 3 octets in length and 685 presents the available bandwidth for DetNet in this link. The units 686 are bytes per second. 688 4.2.3. PREOF Capability Sub-TLV 690 This sub-TLV specifies a set of PREOF capabilities and relevant 691 parameters in sub-TLV. The reader can know more about this sub-TLV 692 referring to section 3.4. 694 The format of this sub-TLV is shown in the following diagram: 696 0 1 2 3 697 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 698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 | Type(TBD10) | Length(4) | 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 | Flags | Maximum out-of-order Packet Number | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 704 The Type field is 1 octets in length, and the value is TBD10. 706 The Length field is 1 octets in length and its value is 4. 708 The Flags field is 1 octet in length, and it is designed as follows: 710 0 1 2 3 4 5 6 7 8 711 +-+-+-+-+-+-+-+-+ 712 |R|E|O| | 713 +-+-+-+-+-+-+-+-+ 715 where: 717 o R-flag: replication-capability flag, which indicates whether a 718 link has the packet replication capability. 720 o E-flag: elimination-capability flag, which indicates whether a 721 link has the packet elimination capability 723 o O-flag: in-order-capability, which indicates whether a LTP has the 724 in-order delivery capability 726 Maximum out-of-order Packet Number field is 3 octets in length and 727 presents the maximum number of out-of-order packets that this link 728 can support, it depends on the reserved buffer size for packet 729 reordering. This value is valid only when the O-flag is set. 731 4.2.4. Queuing Algorithm Capability Sub-TLV 733 This sub-TLV specifies queuing management algorithms capabilities to 734 gaurante bounded queuing latency [I-D.finn-detnet-bounded-latency]. 736 The format of this sub-TLV is shown in the following diagram: 738 0 1 2 3 739 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 740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 741 | Type(TBD11) | Length(4) | 742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 743 | Flags | RESERVED | 744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 746 The Type field is 1 octets in length, and the value is TBD11. 748 The Length field is 1 octets in length and its value is 4. 750 The Flags field is 1 octet in length, and it is designed as follows: 752 0 1 2 3 4 5 6 7 8 753 +-+-+-+-+-+-+-+-+ 754 |C|T|H|A| | 755 +-+-+-+-+-+-+-+-+ 757 where: 759 o C-flag: CBS flag, which indicates whether a link can support Time 760 Aware Shaping [IIEEE802.1Qbv]. 762 o T-flag: TAS flag, which indicuate whether a link can support 763 Credit Based Shaper [IEEE802.1Q-2014] 765 o H-flag: CQF flag, which indicuate whether a link can support 766 Cyclic Queuing and Forwarding [IEEE802.1Qch] 768 o A-flag: ATS flag, which indicuate whether a link can support 769 Asynchronous Traffic Shaping [IEEE802.1Qcr] 771 4.2.5. DetNet Queue Sub-TLV 773 In the context of DetNet, the delay of queuing is bounded, and the 774 bound depends on what queuing management method is used and how many 775 buffers are allocated. This sub-TLV specifies the DetNet queue 776 parameters. 778 The format of this sub-TLV is shown in the following diagram: 780 0 1 2 3 781 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 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 | Type(TBD12) | Length(10) | 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 | Queue Identifier | Queue Buffer Size | 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 787 | Flags | Maximum Queuing Delay | 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 | RESERVED | Minimum Queuing Delay | 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 | RESERVED | Maximum Queuing Delay Variation | 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 The Type field is 1 octets in length, and the value is TBD12. 796 The Length field is 1 octets in length and its value is 10. 798 The Queue Identifier field specifies the identifier of a queue. It 799 could be an internal identifier that is only used within a node. Or 800 it could be used by a centralized controller to specify in which 801 specific queue a flow/packet is required to enter. 803 The Queue Buffer Size field specifies the size of a queue with unit 804 of bytes. 806 The Flags field is 1 octet in length, and it is designed as follows: 808 0 1 2 3 4 5 6 7 8 809 +-+-+-+-+-+-+-+-+ 810 |C|T|H|A| | 811 +-+-+-+-+-+-+-+-+ 813 where: 815 o C-flag: CBS flag, which indicates whether a link can support Time 816 Aware Shaping [IIEEE802.1Qbv]. 818 o T-flag: TAS flag, which indicuate whether a link can support 819 Credit Based Shaper [IEEE802.1Q-2014] 821 o H-flag: CQF flag, which indicuate whether a link can support 822 Cyclic Queuing and Forwarding [IEEE802.1Qch] 824 o A-flag: ATS flag, which indicuate whether a link can support 825 Asynchronous Traffic Shaping [IEEE802.1Qcr] 827 The RESERVED field is reserved for future use. It MUST be set to 0 828 when sent and MUST be ignored when received. 830 Minimum Queuing Delay is 3 octets in length and presents minimum 831 queuing delay value (in microseconds) encoded as an integer value. 832 Implementations may also add this to the value of Min Delay 833 Unidirectional Link Delay Sub-TLV [RFC7471] in order to advertise the 834 minimum delay of this link. Min Queuing Delay can be the same with 835 the Max Queuing Delay. 837 Maximum Queuing Delay is 3 octets in length and presents the maximum 838 queuing delay value (in microseconds) encoded as an integer value. 839 Implementations may also add this to the value of Max Delay 840 Unidirectional Link Delay Sub-TLV [RFC7471]to order to advertise the 841 maximum delay of this link. 843 Maximum Queuing Delay variation is 3 octets in length and presents 844 the maximum queuing delay variation value (in microseconds) encoded 845 as an integer value. 847 5. IANA Considerations 849 5.1. Sub-TLVs for OSPF Node Attribute TLV 851 IANA is requested to register the OSPF sub-TLVs defined in this 852 document in the sub-TLVs for Node Attribute TLV registry. 854 Type Description 855 ---- ------------------------------ 856 TBD1 Packet Processing Delay 857 TBD2 PREOF Capability 859 5.2. Sub-TLVs for OSPF Link TLV 861 IANA is requested to register the OSPF sub-TLVs defined in this 862 document in the sub-TLVs for Link TLV registry. 864 Type Description 865 ---- ------------------------------ 866 TBD3 Maximum DetNet Reservable Bandwidth 867 TBD4 DetNet Available Bandwidth 868 TBD5 PREOF Capability 869 TBD6 Queuing Algorithm Capabilities 870 TBD7 Queue Parameters 872 5.3. Sub-TLVs for ISIS Router Capability TLV 874 IANA is requested to register the ISIS sub-TLVs defined in this 875 document in the sub-TLVs for Router Capability TLV registry. 877 Type Description 878 ---- ------------------------------ 879 TBD8 Packet Processing Delay 880 TBD9 PREOF Capability 882 5.4. Sub-TLVs for IS-IS TLVs 22, 23, 141, 222, and 223 884 IANA is requested to register the ISIS sub-TLVs defined in this 885 document in the Sub-TLVs for TLVs 22, 23, 141, 222, and 223 registry. 887 Type Description 888 ---- ------------------------------ 889 TBD10 Maximum DetNet Reservable Bandwidth 890 TBD11 DetNet Available Bandwidth 891 TBD12 PREOF Capability 892 TBD13 Queuing Algorithm Capabilities 893 TBD14 Queue Parameters 895 6. Security Considerations 897 This document does not introduce security issues beyond those 898 discussed in [RFC7471] and [RFC7810]. 900 7. Acknowledgements 902 8. References 904 8.1. Normative References 906 [I-D.finn-detnet-bounded-latency] 907 Finn, N., Boudec, J., Mohammadpour, E., Varga, B., and J. 908 Farkas, "DetNet Bounded Latency", draft-finn-detnet- 909 bounded-latency-01 (work in progress), July 2018. 911 [I-D.ietf-detnet-architecture] 912 Finn, N., Thubert, P., Varga, B., and J. Farkas, 913 "Deterministic Networking Architecture", draft-ietf- 914 detnet-architecture-08 (work in progress), September 2018. 916 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 917 Requirement Levels", BCP 14, RFC 2119, 918 DOI 10.17487/RFC2119, March 1997, 919 . 921 [RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's 922 Local Addresses in OSPF Traffic Engineering (TE) 923 Extensions", RFC 5786, DOI 10.17487/RFC5786, March 2010, 924 . 926 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 927 Previdi, "OSPF Traffic Engineering (TE) Metric 928 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 929 . 931 [RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and 932 Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", 933 RFC 7810, DOI 10.17487/RFC7810, May 2016, 934 . 936 [RFC7981] Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions 937 for Advertising Router Information", RFC 7981, 938 DOI 10.17487/RFC7981, October 2016, 939 . 941 8.2. Informative References 943 [IEEE802.1Q-2014] 944 "MAC Bridges and VLANs (IEEE 802.1Q-2014)", 2014. 946 [IEEE802.1Qch] 947 "Cyclic Queuing and Forwarding", 2016. 949 [IEEE802.1Qcr] 950 "Asynchronous Traffic Shaping", 2016. 952 [IIEEE802.1Qbv] 953 "Enhancements for Scheduled Traffic", 2016. 955 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 956 (TE) Extensions to OSPF Version 2", RFC 3630, 957 DOI 10.17487/RFC3630, September 2003, 958 . 960 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 961 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 962 2008, . 964 [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in 965 Support of Inter-Autonomous System (AS) MPLS and GMPLS 966 Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, 967 December 2008, . 969 [RFC7310] Lindsay, J. and H. Foerster, "RTP Payload Format for 970 Standard apt-X and Enhanced apt-X Codecs", RFC 7310, 971 DOI 10.17487/RFC7310, July 2014, 972 . 974 Authors' Addresses 976 Xuesong Geng 977 Huawei 979 Email: gengxuesong@huawei.com 981 Mach(Guoyi) Chen 982 Huawei 984 Email: mach.chen@huawei.com 986 Zhenqiang 987 China Mobile 989 Email: lizhenqiang@chinamobile.com