idnits 2.17.1 draft-ietf-detnet-topology-yang-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 14, 2019) is 1922 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) == Unused Reference: 'I-D.ietf-detnet-dp-sol-ip' is defined on line 675, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-dp-sol-mpls' is defined on line 680, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-flow-information-model' is defined on line 685, but no explicit reference was found in the text == Unused Reference: 'I-D.geng-detnet-info-distribution' is defined on line 706, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-use-cases' is defined on line 711, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-teas-yang-te' is defined on line 721, but no explicit reference was found in the text == Unused Reference: 'I-D.thubert-tsvwg-detnet-transport' is defined on line 733, but no explicit reference was found in the text == Unused Reference: 'I-D.varga-detnet-service-model' is defined on line 738, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1CB' is defined on line 743, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Q-2014' is defined on line 749, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Qbu' is defined on line 754, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Qbv' is defined on line 759, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Qcc' is defined on line 764, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Qch' is defined on line 769, but no explicit reference was found in the text == Unused Reference: 'IEEE802.1Qci' is defined on line 775, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 781, but no explicit reference was found in the text == Unused Reference: 'RFC4875' is defined on line 786, but no explicit reference was found in the text == Unused Reference: 'RFC8342' is defined on line 793, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-finn-detnet-bounded-latency-02 ** 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-10 == Outdated reference: A later version (-02) exists of draft-ietf-detnet-dp-sol-ip-01 == Outdated reference: A later version (-02) exists of draft-ietf-detnet-dp-sol-mpls-01 == Outdated reference: A later version (-14) exists of draft-ietf-detnet-flow-information-model-02 ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-flow-information-model (ref. 'I-D.ietf-detnet-flow-information-model') == Outdated reference: A later version (-04) exists of draft-geng-detnet-info-distribution-03 == Outdated reference: A later version (-20) exists of draft-ietf-detnet-yang-00 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-17 == Outdated reference: A later version (-22) exists of draft-ietf-teas-yang-te-topo-18 Summary: 2 errors (**), 0 flaws (~~), 29 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Geng 3 Internet-Draft M. Chen 4 Intended status: Standards Track Huawei Technologies 5 Expires: July 18, 2019 Z. Li 6 China Mobile 7 R. Rahman 8 Cisco Systems 9 January 14, 2019 11 Deterministic Networking (DetNet) Topology YANG Model 12 draft-ietf-detnet-topology-yang-00 14 Abstract 16 This document defines a YANG data model for Deterministic Networking 17 (DetNet) topology discovery and capability configuration. 19 The YANG module defined in this document conforms to the Network 20 Management Datastore Architecture (NMDA). 22 Requirements Language 24 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 25 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 26 document are to be interpreted as described in RFC 2119 [RFC2119]. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on July 18, 2019. 45 Copyright Notice 47 Copyright (c) 2019 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (https://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. DetNet Topology Model . . . . . . . . . . . . . . . . . . . . 3 65 3.1. DetNet Node Attributes . . . . . . . . . . . . . . . . . 4 66 3.2. DetNet Link Attributes . . . . . . . . . . . . . . . . . 4 67 3.3. DetNet Link Terminate Point Attributes . . . . . . . . . 5 68 4. DetNet Topology YANG Structure . . . . . . . . . . . . . . . 7 69 5. DetNet Topology YANG Model . . . . . . . . . . . . . . . . . 9 70 6. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 14 71 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 72 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15 73 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 74 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 75 10.1. Normative References . . . . . . . . . . . . . . . . . . 15 76 10.2. Informative References . . . . . . . . . . . . . . . . . 16 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 79 1. Introduction 81 Deterministic Networking (DetNet) [I-D.ietf-detnet-architecture] is 82 defined to provide high-quality network service with extremely low 83 packet loss rate, bounded low latency and jitter. 85 DetNet YANG [RFC7950] [RFC6991] models are used for DetNet service 86 configuration, QoS configuration and topology discovery. DetNet 87 service and QoS configuration models are defined in 88 [I-D.ietf-detnet-yang]. This document defines DetNet topology model 89 that can be used for DetNet topology/capability discovery and device 90 configuration. DetNet topology model is an augmentation of the ietf- 91 te-toplogy model [I-D.ietf-teas-yang-te-topo]. 93 2. Terminologies 95 This document uses the terminologies defined in 96 [I-D.ietf-detnet-architecture]. 98 3. DetNet Topology Model 100 A DetNet topology is composed of a set of DetNet nodes and DetNet 101 links. DetNet nodes represent the network devices that can transport 102 DetNet services, which are connected by DetNet links. A DetNet Link 103 Terminate Point(LTP) is the connection point between a DetNet node 104 and a DetNet link, which represents the port or interface of a DetNet 105 node. The concept of DetNet node/link/LTP are similar as TE 106 node/link/LTP which are defined in [I-D.ietf-teas-yang-te-topo]. 108 Figure 1 shows a simple DetNet topology: A is a DetNet node, B is 109 DetNet a LTP, and C is a DetNet link. 111 +---+ +---+ 112 | A |o(B)--(C)--| | 113 +---+ +---+ 115 Figure 1. An example of DetNet Topology 117 DetNet topology model (ietf-detnet-topology) augments ietf-te- 118 topology model [I-D.ietf-teas-yang-te-topo] to cover the following 119 groups of attributes, which are necessary for supporting DetNet 120 congestion protection and service protection: 122 o Bandwidth related attributes (e.g., bandwidth reserved for 123 DetNet); 125 o Buffer/queue management related attributes (e.g., queue management 126 parameters, etc.); 128 o PREOF (Packet Replication, Elimination and Ordering Function) 129 capabilities and parameters (e.g., maximum out-of-order packets, 130 etc.); 132 o Delay related attributes (e.g., node processing delay, queuing 133 delay, link delay, etc.); 135 The above attributes are categorized into three types: node 136 attributes, link attributes and LTP attributes. The detailed 137 descriptions and model definitions are specified in section 3.1, 3.2 138 and 3.3, respectively. 140 3.1. DetNet Node Attributes 142 Section 4.3 of [I-D.finn-detnet-bounded-latency] gives a DetNet time 143 model, which defines that the delay within a node includes five 144 parts: processing delay, regulation delay, queuing delay, output 145 delay and preemption delay. The processing delay, queuing delay and 146 regulation delay are variable in general, but for DetNet, these 147 delays should be bounded, which is the basic assumption of 148 deterministic networking. These bounded delay parameters are 149 necessary to perform DetNet path computation. Among this delay 150 attributes, processing delay and regulation delay are node relevant, 151 and the queuing delay is LTP relevant. In addition, in order to 152 simplify the model and implementation, the processing delay and 153 regulation delay are combined as processing delay, and the preemption 154 delay is included in queuing delay. [Editor notes: more comments and 155 inputs need here]. 157 For the DetNet node attributes, the following variables are 158 introduced: 160 o Maximum DetNet packet processing delay 162 o Minimum DetNet packet processing delay 164 o Maximum DetNet packet processing delay variation 166 The modeling structure is shown below: 168 augment /nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes: 169 +--rw detnet-node-attributes 170 +--rw minimum-packet-processing-delay? uint32 171 +--rw maximum-packet-processing-delay? uint32 172 +--rw maximum-packet-processing-delay-variation? uint32 174 3.2. DetNet Link Attributes 176 DetNet link attributes include link delay and link bandwidth for 177 DetNet. This document introduces the following link related 178 attributes: 180 o Link delay: link delay is a constant that only depends on the 181 physical connection. It has been defined in ietf-te-topology 182 [I-D.ietf-teas-yang-te-topo], and DetNet can reuse it directly. 184 o Maximum DetNet reservable bandwidth: the maximum reservable 185 bandwidth that is allocated to DetNet. For a 10G link, if 50% of 186 the bandwidth is allocated to DetNet, then the maximum DetNet 187 reservable bandwidth is 5G. That means there are 5G bandwidth 188 that can be used by DetNet flows. 190 o Reserved DetNet bandwidth: the bandwidth that has been reserved 191 for DetNet flows. 193 o Available DetNet bandwidth: the bandwidth that is available for 194 new DetNet flows. 196 The DetNet link attributes are modeled within a link, and the YANG 197 module structure is shown below: 199 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes: 200 +--rw detnet-link-attributes 201 +--rw maximum-reservable-bandwidth 202 | +--rw te-bandwidth 203 | +--rw (technology)? 204 | +--:(generic) 205 | +--rw generic? te-bandwidth 206 +--rw reserved-detnet-bandwidth 207 | +--rw te-bandwidth 208 | +--rw (technology)? 209 | +--:(generic) 210 | +--rw generic? te-bandwidth 211 +--rw available-detnet-bandwidth 212 +--rw te-bandwidth 213 +--rw (technology)? 214 +--:(generic) 215 +--rw generic? te-bandwidth 217 3.3. DetNet Link Terminate Point Attributes 219 The concept of LTP is introduced in [I-D.ietf-teas-yang-te-topo], and 220 this section introduces attributes for DetNet LTP. 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 The above functions are modeled as a set of capabilities and relevant 235 parameters, which are listed below: 237 o in-order-capability: indicates whether a LTP has the in-order 238 delivery capability. 240 o maximum-number-of-out-of-order-packets: indicates the maximum 241 number of out-of-order packets that an LTP can support, it depends 242 on the reserved buffer size for packet reordering. 244 o replication-capability: indicates whether a LTP has the packet 245 replication capability. 247 o elimination-capability: indicates whether a LTP has the packet 248 elimination capability. 250 In addition, DetNet LTP also includes queuing management algorithms 251 and queuing delay attributes. In the context of DetNet, the delay of 252 queuing is bounded, and the bound depends on what queuing management 253 method is used and how many buffers are allocated. More information 254 can be found in [I-D.finn-detnet-bounded-latency]. Queuing related 255 attributes are listed below: 257 o queuing-algorithm-capabilities: it is modeled as a list that 258 includes all queuing algorithms that a LTP supports. 260 o detnet-queues: it's modeled as a list that includes all queues of 261 a DetNet LTP. For each queue, it has the following attributes: 263 o queue-identifier: an identifier of a queue. It could be an 264 internal identifier that is only used within a node. Or it could 265 be used by a centralized controller to specify in which specific 266 queue a flow/packet is required to enter. 268 o queue-buffer-size: the size of a queue with unit of bytes. 270 o enabled-queuing-algorithm: indicates what queuing management 271 algorithm is enabled. 273 o maximum-queuing-delay: the maximum queuing delay that a packet 274 will undergo when transmitted through the queue. 276 o minimum-queuing-delay: the minimum queuing delay that a packet 277 will undergo when transmitted through the queue. 279 o maximum-queuing-delay-variation: the maximum queuing delay 280 variation that a packet will undergo when transmitted the queue. 282 The DetNet LTP attributes are modeled within a LTP, the YANG module 283 structure is shown below: 285 augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te: 286 +--rw detnet-terminate-point-attributes 287 +--rw elimination-capability? boolean 288 +--rw replication-capability? boolean 289 +--rw in-ordering-capability 290 | +--rw in-ordering-capability? boolean 291 | +--rw maximum-out-of-order-packets? uint32 292 +--rw queuing-algorithm-capabilities 293 | +--rw credit-based-shaping? boolean 294 | +--rw time-aware-shaping? boolean 295 | +--rw cyclic-queuing-and-forwarding? boolean 296 | +--rw asynchronous-traffic-shaping? boolean 297 +--rw queues* [queue-identifier] 298 +--rw queue-identifier uint32 299 +--rw queue-buffer-size? uint32 300 +--rw enabled-queuing-algorithm 301 | +--rw credit-based-shaping? boolean 302 | +--rw time-aware-shaping? boolean 303 | +--rw cyclic-queuing-and-forwarding? boolean 304 | +--rw asynchronous-traffic-shaping? boolean 305 +--rw minimum-queuing-delay? uint32 306 +--rw maximum-queuing-delay? uint32 307 +--rw maximum-queuing-delay-variation? uint32 309 4. DetNet Topology YANG Structure 310 module: ietf-detnet-topology 311 augment /nw:networks/nw:network/nw:network-types/tet:te-topology: 312 +--rw detnet-topology! 313 augment /nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes: 314 +--rw detnet-node-attributes 315 +--rw minimum-packet-processing-delay? uint32 316 +--rw maximum-packet-processing-delay? uint32 317 +--rw maximum-packet-processing-delay-variation? uint32 318 augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes: 319 +--rw detnet-link-attributes 320 +--rw maximum-reservable-bandwidth 321 | +--rw te-bandwidth 322 | +--rw (technology)? 323 | +--:(generic) 324 | +--rw generic? te-bandwidth 325 +--rw reserved-detnet-bandwidth 326 | +--rw te-bandwidth 327 | +--rw (technology)? 328 | +--:(generic) 329 | +--rw generic? te-bandwidth 330 +--rw available-detnet-bandwidth 331 +--rw te-bandwidth 332 +--rw (technology)? 333 +--:(generic) 334 +--rw generic? te-bandwidth 335 augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te: 336 +--rw detnet-terminate-point-attributes 337 +--rw elimination-capability? boolean 338 +--rw replication-capability? boolean 339 +--rw in-ordering-capability 340 | +--rw in-ordering-capability? boolean 341 | +--rw maximum-out-of-order-packets? uint32 342 +--rw queuing-algorithm-capabilities 343 | +--rw credit-based-shaping? boolean 344 | +--rw time-aware-shaping? boolean 345 | +--rw cyclic-queuing-and-forwarding? boolean 346 | +--rw asynchronous-traffic-shaping? boolean 347 +--rw queues* [queue-identifier] 348 +--rw queue-identifier uint32 349 +--rw queue-buffer-size? uint32 350 +--rw enabled-queuing-algorithm 351 | +--rw credit-based-shaping? boolean 352 | +--rw time-aware-shaping? boolean 353 | +--rw cyclic-queuing-and-forwarding? boolean 354 | +--rw asynchronous-traffic-shaping? boolean 355 +--rw minimum-queuing-delay? uint32 356 +--rw maximum-queuing-delay? uint32 357 +--rw maximum-queuing-delay-variation? uint32 359 5. DetNet Topology YANG Model 361 file "ietf-detnet-topology@20190114.yang" 362 module ietf-detnet-topology { 363 yang-version 1.1; 364 namespace "urn:ietf:params:xml:ns:yang:ietf-detnet-topology"; 365 prefix "detnet-topology"; 367 import ietf-te-types { 368 prefix "te-types"; 369 } 371 import ietf-te-topology { 372 prefix "tet"; 373 } 375 import ietf-network { 376 prefix "nw"; 377 } 379 import ietf-network-topology { 380 prefix "nt"; 381 } 383 organization 384 "IETF Deterministic Networking(DetNet)Working Group"; 386 contact 387 "WG Web: 388 WG List: 390 WG Chair: Lou Berger 391 393 Janos Farkas 394 396 Editor: Xuesong Geng 397 399 Editor: Mach Chen 400 402 Editor: Zhenqiang Li 403 405 Editor: Reshad Rahman 406 "; 408 description 409 "This YANG module augments the 'ietf-te-topology' 410 module with DetNet related capabilities and 411 parameters."; 413 revision "2018-09-10" { 414 description "Initial revision"; 415 reference "RFC XXXX: draft-geng-detnet-config-yang-05"; 416 } 418 grouping detnet-queuing-algorithms { 419 description 420 "Relationship with IEEE 802.1 TSN YANG models is TBD."; 421 } 423 grouping detnet-node-attributes{ 424 description 425 "DetNet node related attributes."; 426 leaf minimum-packet-processing-delay{ 427 type uint32; 428 description 429 "Minimum packet processing delay 430 in a node. The unit of the delay 431 is microsecond(us)"; 432 } 433 leaf maximum-packet-processing-delay{ 434 type uint32; 435 description 436 "Maximum packet processing delay 437 in a node. The unit of the delay 438 is microsecond(us)"; 439 } 440 leaf maximum-packet-processing-delay-variation{ 441 type uint32; 442 description 443 "Maximum packet processing delay 444 variation in a node. The unit of 445 the delay variation is microsecond(us)"; 446 } 447 } 449 grouping detnet-link-attributes{ 450 description 451 "DetNet link related attributes."; 453 container maximum-reservable-bandwidth{ 454 uses te-types:te-bandwidth; 455 description 456 "This container specifies the maximum bandwidth 457 that is reserved for DetNet on this link."; 458 } 460 container reserved-detnet-bandwidth{ 461 uses te-types:te-bandwidth; 462 description 463 "This container specifies the bandwidth that has 464 been reserved for DetNet on this link."; 465 } 466 container available-detnet-bandwidth{ 467 uses te-types:te-bandwidth; 468 description 469 "This container specifies the bandwidth that is 470 available for new DetNet flows on this link."; 471 } 472 } 474 grouping detnet-terminate-point-attributes{ 475 description 476 "DetNet terminate point related attributes."; 478 leaf elimination-capability{ 479 type boolean; 480 description 481 "Indicates whether a node is able to do packet 482 elimination."; 483 reference 484 "Section 3.2.2.3 of 485 draft-ietf-detnet-architecture"; 487 } 488 leaf replication-capability{ 489 type boolean; 490 description 491 "Indicates whether a node is able to do packet 492 replication."; 493 reference 494 "Section 3.2.2.2 of 495 draft-ietf-detnet-architecture"; 496 } 497 container in-ordering-capability { 498 description 499 "Indicates the parameters needed for 500 packet in-ordering."; 501 reference 502 "Section 3.2.2.1 of 503 draft-ietf-detnet-architecture"; 505 leaf in-ordering-capability { 506 type boolean; 507 description 508 "Indicates whether a node is able to do packet 509 in-ordering."; 510 } 511 leaf maximum-out-of-order-packets { 512 type uint32; 513 description 514 "The maximum number of out-of-order packets."; 515 } 516 } 518 container queuing-algorithm-capabilities { 519 description 520 "All queuing algorithms that a LTP supports."; 521 uses detnet-queuing-algorithms; 522 } 524 list queues { 525 key "queue-identifier"; 526 description 527 "A list of DetNet queues."; 528 leaf queue-identifier { 529 type uint32; 530 description 531 "The identifier of the queue."; 532 } 533 leaf queue-buffer-size { 534 type uint32; 535 description 536 "The size of the queue with unit of bytes."; 537 } 539 container enabled-queuing-algorithm { 540 description 541 "The queuing algorithms that are enabled on the queue."; 542 uses detnet-queuing-algorithms; 543 } 545 leaf minimum-queuing-delay{ 546 type uint32; 547 description 548 "The minimum queuing delay of the queue. 549 The unit of the delay is microsecond(us)"; 550 } 551 leaf maximum-queuing-delay{ 552 type uint32; 553 description 554 "The maximum queuing delay of the queue. 555 The unit of the delay is microsecond(us)"; 556 } 557 leaf maximum-queuing-delay-variation{ 558 type uint32; 559 description 560 "The maximum queuing delay variation of the queue. 561 The unit of the delay variation is microsecond(us)"; 562 } 563 } 564 } 566 augment "/nw:networks/nw:network/nw:network-types/tet:te-topology"{ 567 description 568 "Introduce new network type for TE topology."; 569 container detnet-topology { 570 presence "Indicates DetNet topology."; 571 description 572 "Its presence identifies the DetNet topology type"; 573 } 574 } 576 augment "/nw:networks/nw:network/nw:node/tet:te/" 577 + "tet:te-node-attributes" { 578 when "../../../nw:network-types/tet:te-topology/" 579 + "detnet-topology:detnet-topology" { 580 description 581 "Augmentation parameters apply only for networks with 582 DetNet topology type."; 583 } 584 description 585 "Augmentation parameters apply for DetNet node attributes."; 586 container detnet-node-attributes { 587 description 588 "Attributes for DetNet node."; 589 uses detnet-node-attributes; 590 } 591 } 593 augment "/nw:networks/nw:network/nt:link/tet:te/" 594 + "tet:te-link-attributes" { 595 when "../../../nw:network-types/tet:te-topology/" 596 + "detnet-topology:detnet-topology" { 597 description 598 "Augmentation parameters apply only for networks with 599 DetNet topology type."; 600 } 601 description 602 "Augmentation parameters apply for DetNet link attributes."; 603 container detnet-link-attributes { 604 description 605 "Attributes for DetNet link."; 606 uses detnet-link-attributes; 607 } 608 } 610 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 611 + "tet:te" { 612 when "../../../nw:network-types/tet:te-topology/" 613 + "detnet-topology:detnet-topology" { 614 description 615 "Augmentation parameters apply only for networks with 616 DetNet topology type."; 617 } 618 description 619 "Augmentation parameters apply for DetNet 620 link termination point."; 621 container detnet-terminate-point-attributes { 622 description 623 "Attributes for DetNet link terminate point."; 624 uses detnet-terminate-point-attributes; 625 } 626 } 627 } //topology module 629 631 6. Open Issues 633 There are some open issues that are still under discussion: 635 o The Relationship with 802.1 TSN YANG models is TBD. TSN YANG 636 models include: P802.1Qcw, which defines TSN YANG for Qbv, Qbu, 637 and Qci, and P802.1CBcv, which defines YANG for 802.1CB. The 638 possible problem here is how to avoid possible overlap among yang 639 models defined in IETF and IEEE. A common YANG model may be 640 defined in the future to shared by both TSN and DetNet. More 641 discussion are needed here. 643 o How to support DetNet OAM is TBD. 645 These issues will be resolved in the following versions of the draft. 647 7. IANA Considerations 649 This document makes no request of IANA. 651 Note to RFC Editor: this section may be removed on publication as an 652 RFC. 654 8. Security Considerations 656 658 9. Acknowledgements 660 10. References 662 10.1. Normative References 664 [I-D.finn-detnet-bounded-latency] 665 Finn, N., Boudec, J., Mohammadpour, E., Zhang, J., Varga, 666 B., and J. Farkas, "DetNet Bounded Latency", draft-finn- 667 detnet-bounded-latency-02 (work in progress), October 668 2018. 670 [I-D.ietf-detnet-architecture] 671 Finn, N., Thubert, P., Varga, B., and J. Farkas, 672 "Deterministic Networking Architecture", draft-ietf- 673 detnet-architecture-10 (work in progress), December 2018. 675 [I-D.ietf-detnet-dp-sol-ip] 676 Korhonen, J. and B. Varga, "DetNet IP Data Plane 677 Encapsulation", draft-ietf-detnet-dp-sol-ip-01 (work in 678 progress), October 2018. 680 [I-D.ietf-detnet-dp-sol-mpls] 681 Korhonen, J. and B. Varga, "DetNet MPLS Data Plane 682 Encapsulation", draft-ietf-detnet-dp-sol-mpls-01 (work in 683 progress), October 2018. 685 [I-D.ietf-detnet-flow-information-model] 686 Farkas, J., Varga, B., Cummings, R., Jiang, Y., and Y. 687 Zha, "DetNet Flow Information Model", draft-ietf-detnet- 688 flow-information-model-02 (work in progress), October 689 2018. 691 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 692 Requirement Levels", BCP 14, RFC 2119, 693 DOI 10.17487/RFC2119, March 1997, 694 . 696 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 697 RFC 6991, DOI 10.17487/RFC6991, July 2013, 698 . 700 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 701 RFC 7950, DOI 10.17487/RFC7950, August 2016, 702 . 704 10.2. Informative References 706 [I-D.geng-detnet-info-distribution] 707 Geng, X., Chen, M., and Z. Li, "IGP-TE Extensions for 708 DetNet Information Distribution", draft-geng-detnet-info- 709 distribution-03 (work in progress), October 2018. 711 [I-D.ietf-detnet-use-cases] 712 Grossman, E., "Deterministic Networking Use Cases", draft- 713 ietf-detnet-use-cases-20 (work in progress), December 714 2018. 716 [I-D.ietf-detnet-yang] 717 Geng, X., Chen, M., Li, Z., and R. Rahman, "DetNet 718 Configuration YANG Model", draft-ietf-detnet-yang-00 (work 719 in progress), October 2018. 721 [I-D.ietf-teas-yang-te] 722 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and 723 I. Bryskin, "A YANG Data Model for Traffic Engineering 724 Tunnels and Interfaces", draft-ietf-teas-yang-te-17 (work 725 in progress), October 2018. 727 [I-D.ietf-teas-yang-te-topo] 728 Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 729 O. Dios, "YANG Data Model for Traffic Engineering (TE) 730 Topologies", draft-ietf-teas-yang-te-topo-18 (work in 731 progress), June 2018. 733 [I-D.thubert-tsvwg-detnet-transport] 734 Thubert, P., "A Transport Layer for Deterministic 735 Networks", draft-thubert-tsvwg-detnet-transport-01 (work 736 in progress), October 2017. 738 [I-D.varga-detnet-service-model] 739 Varga, B. and J. Farkas, "DetNet Service Model", draft- 740 varga-detnet-service-model-02 (work in progress), May 741 2017. 743 [IEEE802.1CB] 744 "IEEE, "Frame Replication and Elimination for Reliability 745 (IEEE Draft P802.1CB)", 2017, 746 .", 747 2016. 749 [IEEE802.1Q-2014] 750 "IEEE, "IEEE Std 802.1Q Bridges and Bridged Networks", 751 2014, .", 752 2014. 754 [IEEE802.1Qbu] 755 "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks - 756 Amendment 26: Frame Preemption", 2016, 757 .", 2016. 759 [IEEE802.1Qbv] 760 "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks - 761 Amendment 25: Enhancements for Scheduled Traffic", 2015, 762 .", 2016. 764 [IEEE802.1Qcc] 765 "IEEE, "Stream Reservation Protocol (SRP) Enhancements and 766 Performance Improvements (IEEE Draft P802.1Qcc)", 2017, 767 .". 769 [IEEE802.1Qch] 770 "IEEE, "Cyclic Queuing and Forwarding (IEEE Draft 771 P802.1Qch)", 2017, 772 .", 773 2016. 775 [IEEE802.1Qci] 776 "IEEE, "Per-Stream Filtering and Policing (IEEE Draft 777 P802.1Qci)", 2016, 778 .", 779 2016. 781 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., 782 and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 783 Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, 784 . 786 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 787 Yasukawa, Ed., "Extensions to Resource Reservation 788 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 789 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, 790 DOI 10.17487/RFC4875, May 2007, 791 . 793 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 794 and R. Wilton, "Network Management Datastore Architecture 795 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 796 . 798 Authors' Addresses 800 Xuesong Geng 801 Huawei Technologies 803 Email: gengxuesong@huawei.com 805 Mach(Guoyi) Chen 806 Huawei Technologies 808 Email: mach.chen@huawei.com 810 Zhenqiang Li 811 China Mobile 813 Email: lizhenqiang@chinamobile.com 815 Reshad Rahman 816 Cisco Systems 818 Email: rrahman@cisco.com