idnits 2.17.1 draft-ietf-lsr-ospf-yang-augmentation-v1-04.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 == Line 138 has weird spacing: '...face-id ine...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 29, 2021) is 1093 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) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349) ** Obsolete normative reference: RFC 8920 (Obsoleted by RFC 9492) Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet A. Lindem 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track Y. Qu 5 Expires: October 31, 2021 Futurewei 6 April 29, 2021 8 OSPF YANG Model Augmentations for Additional Features - Version 1 9 draft-ietf-lsr-ospf-yang-augmentation-v1-04 11 Abstract 13 This document defines YANG data modules augmenting the IETF OSPF YANG 14 model to provide support for Traffic Engineering Extensions to OSPF 15 Version 3 as defined in RF 5329, OSPF Two-Part Metric as defined in 16 RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and OSPF 17 Link-Local Signaling (LLS) Extensions for Local Interface ID 18 Advertisement as defined in RFC 8510. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on October 31, 2021. 37 Copyright Notice 39 Copyright (c) 2021 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 56 2. YANG Module for Traffic Engineering Extesions to OSPF Version 57 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 8 59 4. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 13 60 5. YANG Module for OSPF LLS Extenstion for Local Interface ID 61 Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 18 62 6. YANG Module for OSPF Application-Specific Link Attributes . . 20 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 65 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 66 10. Normative References . . . . . . . . . . . . . . . . . . . . 27 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 69 1. Overview 71 YANG [RFC6020] [RFC7950] is a data definition language used to define 72 the contents of a conceptual data store that allows networked devices 73 to be managed using NETCONF [RFC6241]. YANG is proving relevant 74 beyond its initial confines, as bindings to other interfaces (e.g., 75 ReST) and encodings other than XML (e.g., JSON) are being defined. 76 Furthermore, YANG data models can be used as the basis for 77 implementation of other interfaces, such as CLI and programmatic 78 APIs. 80 This document defines YANG data modules augmenting the IETF OSPF YANG 81 model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to 82 provide support for configuration and operational state for the 83 following OSPF features: 85 RFC5329: Traffic Engineering Extensions to OSPF Version 3 [RFC5329]. 87 RFC8042: OSPF Two-Part Metric [RFC8042]. 89 RFC8379: OSPF Graceful Link Shutdown [RFC8379]. 91 RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local 92 Interface ID Advertisement[RFC8510]. 94 The augmentations defined in this document requires support for the 95 OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF 96 configuration and state. The OSPF YANG model augments the ietf- 97 routing YANG model defined in [RFC8022]. 99 1.1. Requirements Language 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in [RFC2119]. 105 2. YANG Module for Traffic Engineering Extesions to OSPF Version 3 107 This document defines a YANG module for Traffic Engineering 108 Extersions to OSPF Version 3 as defined in [RFC5329]. It is an 109 augmentation of the OSPF base model. 111 module: ietf-ospfv3-te 112 augment /rt:routing/rt:control-plane-protocols 113 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 114 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 115 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 116 /ospf:body: 117 +--ro ospfv3-intra-area-te 118 +--ro router-address-tlv 119 | +--ro router-address? inet:ipv6-address 120 +--ro link-tlv 121 +--ro link-type ospf:router-link-type 122 +--ro local-if-ipv6-addrs 123 | +--ro local-if-ipv6-addr* inet:ipv6-address 124 +--ro remote-if-ipv6-addrs 125 | +--ro remote-if-ipv6-addr* inet:ipv6-address 126 +--ro te-metric? uint32 127 +--ro max-bandwidth? 128 | rt-types:bandwidth-ieee-float32 129 +--ro max-reservable-bandwidth? 130 | rt-types:bandwidth-ieee-float32 131 +--ro unreserved-bandwidths 132 | +--ro unreserved-bandwidth* 133 | +--ro priority? uint8 134 | +--ro unreserved-bandwidth? 135 | rt-types:bandwidth-ieee-float32 136 +--ro admin-group? uint32 137 +--ro neighbor-id 138 | +--ro nbr-interface-id inet:ipv4-address 139 | +--ro nbr-router-id yang:dotted-quad 140 +--ro unknown-tlvs 141 +--ro unknown-tlv* 142 +--ro type? uint16 143 +--ro length? uint16 144 +--ro value? yang:hex-string 146 file "ietf-ospfv3-te@2020-04-24.yang" 147 module ietf-ospfv3-te { 148 yang-version 1.1; 149 namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-te"; 151 prefix ospfv3-te; 153 import ietf-inet-types { 154 prefix "inet"; 155 reference "RFC 6991: Common YANG Data Types"; 156 } 158 import ietf-yang-types { 159 prefix "yang"; 160 reference "RFC 6991: Common YANG Data Types"; 161 } 163 import ietf-routing-types { 164 prefix "rt-types"; 165 reference "RFC 8294: Common YANG Data Types for the 166 Routing Area"; 167 } 169 import ietf-routing { 170 prefix "rt"; 171 } 173 import ietf-ospf { 174 prefix "ospf"; 175 } 177 organization 178 "IETF LSR - Link State Routing Working Group"; 180 contact 181 "WG Web: 182 WG List: 184 Author: Yingzhen Qu 185 186 Author: Acee Lindem 187 "; 189 description 190 "This YANG module defines the configuration and operational 191 state for OSPFv3 extensions to support intra-area Traffic 192 Engineering (TE) as defined in RFC 5329. 194 Copyright (c) 2019 IETF Trust and the persons identified as 195 authors of the code. All rights reserved. 197 Redistribution and use in source and binary forms, with or 198 without modification, is permitted pursuant to, and subject 199 to the license terms contained in, the Simplified BSD License 200 set forth in Section 4.c of the IETF Trust's Legal Provisions 201 Relating to IETF Documents 202 (http://trustee.ietf.org/license-info). 204 This version of this YANG module is part of RFC XXXX; 205 see the RFC itself for full legal notices."; 207 reference "RFC XXXX"; 209 revision 2020-04-24 { 210 description 211 "Initial version"; 212 reference 213 "RFC XXXX: A YANG Data Model for OSPFv3 TE."; 214 } 216 identity ospfv3-intra-area-te-lsa { 217 base ospf:ospfv3-lsa-type; 218 description 219 "OSPFv3 Intrea-area TE LSA."; 220 } 222 grouping ospfv3-intra-area-te { 223 description "Grouping for OSPFv3 intra-area-te-lsa."; 224 container ospfv3-intra-area-te { 225 container router-address-tlv { 226 description "The router IPv6 address tlv advertises a 227 reachable IPv6 address."; 228 leaf router-address { 229 type inet:ipv6-address; 230 description 231 "Router IPv6 address."; 232 } 233 } 235 container link-tlv { 236 description "Describes a singel link, and it is constructed 237 of a set of Sub-TLVs."; 238 leaf link-type { 239 type ospf:router-link-type; 240 mandatory true; 241 description "Link type."; 242 } 244 container local-if-ipv6-addrs { 245 description "All local interface IPv6 addresses."; 246 leaf-list local-if-ipv6-addr { 247 type inet:ipv6-address; 248 description 249 "List of local interface IPv6 addresses."; 250 } 251 } 253 container remote-if-ipv6-addrs { 254 description "All remote interface IPv6 addresses."; 255 leaf-list remote-if-ipv6-addr { 256 type inet:ipv6-address; 257 description 258 "List of remote interface IPv6 addresses."; 259 } 260 } 262 leaf te-metric { 263 type uint32; 264 description "TE metric."; 265 } 267 leaf max-bandwidth { 268 type rt-types:bandwidth-ieee-float32; 269 description "Maximum bandwidth."; 270 } 272 leaf max-reservable-bandwidth { 273 type rt-types:bandwidth-ieee-float32; 274 description "Maximum reservable bandwidth."; 275 } 277 container unreserved-bandwidths { 278 description "All unreserved bandwidths."; 279 list unreserved-bandwidth { 280 leaf priority { 281 type uint8 { 282 range "0 .. 7"; 283 } 284 description "Priority from 0 to 7."; 285 } 286 leaf unreserved-bandwidth { 287 type rt-types:bandwidth-ieee-float32; 288 description "Unreserved bandwidth."; 289 } 290 description 291 "List of unreserved bandwidths for different 292 priorities."; 293 } 294 } 296 leaf admin-group { 297 type uint32; 298 description 299 "Administrative group/Resource Class/Color."; 300 } 302 container neighbor-id { 303 description "Neighbor link identitification."; 304 leaf nbr-interface-id { 305 type inet:ipv4-address; 306 mandatory true; 307 description "The neighbor's interface ID."; 308 } 309 leaf nbr-router-id { 310 type yang:dotted-quad; 311 mandatory true; 312 description "The neighbor's router ID."; 313 } 314 } 316 uses ospf:unknown-tlvs; 317 } 319 description "OSPFv3 Intra-Area-TE-LSA."; 320 reference "RFC 5329: Traffic Engineering Extensions to OSPF 321 : Version 3."; 322 } 323 } 325 augment "/rt:routing/" 326 + "rt:control-plane-protocols/rt:control-plane-protocol/" 327 + "ospf:ospf/ospf:areas/" 328 + "ospf:area/ospf:database/" 329 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 330 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 331 + "ospf:ospfv3/ospf:body" { 332 when "../../../../../../../../../" 333 + "rt:type = 'ospf:ospfv3'" { 334 description 335 "This augmentation is only valid for OSPFv3."; 336 } 337 description 338 "OSPFv3 Intrea-Area-TE-LSA."; 340 uses ospfv3-intra-area-te; 341 } 342 } 343 345 3. YANG Module for OSPF Two-Part Metric 347 This document defines a YANG module for OSPF Two-Part Metric feature 348 as defined in [RFC8042]. It is an augmentation of the OSPF base 349 model. 351 module: ietf-ospf-two-part-metric 352 augment /rt:routing/rt:control-plane-protocols 353 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 354 /ospf:interfaces/ospf:interface: 355 +--rw two-part-metric 356 +--rw enable? boolean 357 +--rw int-input-cost? ospf:ospf-link-metric 358 augment /rt:routing/rt:control-plane-protocols 359 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 360 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 361 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 362 /ospf:body/ospf:opaque/ospf:extended-link-opaque 363 /ospf:extended-link-tlv: 364 +--ro network-to-router-metric-sub-tlvs 365 +--ro net-to-rtr-sub-tlv* 366 +--ro mt-id? uint8 367 +--ro mt-metric? uint16 368 augment /rt:routing/rt:control-plane-protocols 369 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 370 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 371 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 372 /ospf:body/ospf:opaque/ospf:te-opaque/ospf:link-tlv: 373 +--ro network-to-router-te-metric? uint32 374 augment /rt:routing/rt:control-plane-protocols 375 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 376 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 377 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 378 /ospf:body/ospfv3-te:ospfv3-intra-area-te/ospfv3-te:link-tlv: 379 +--ro network-to-router-te-metric? uint32 381 file "ietf-ospf-two-part-metric@2020-04-24.yang" 382 module ietf-ospf-two-part-metric { 383 yang-version 1.1; 384 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric"; 386 prefix ospf-two-metric; 388 import ietf-routing { 389 prefix "rt"; 390 } 392 import ietf-ospf { 393 prefix "ospf"; 394 } 396 import ietf-ospfv3-te { 397 prefix "ospfv3-te"; 398 } 399 organization 400 "IETF LSR - Link State Routing Working Group"; 402 contact 403 "WG Web: 404 WG List: 406 Author: Yingzhen Qu 407 408 Author: Acee Lindem 409 "; 411 description 412 "This YANG module defines the configuration and operational 413 state for OSPF Two-Part Metric feature as defined in RFC 8042. 415 Copyright (c) 2019 IETF Trust and the persons identified as 416 authors of the code. All rights reserved. 418 Redistribution and use in source and binary forms, with or 419 without modification, is permitted pursuant to, and subject 420 to the license terms contained in, the Simplified BSD License 421 set forth in Section 4.c of the IETF Trust's Legal Provisions 422 Relating to IETF Documents 423 (http://trustee.ietf.org/license-info). 425 This version of this YANG module is part of RFC XXXX; 426 see the RFC itself for full legal notices."; 428 reference "RFC XXXX"; 430 revision 2020-04-24 { 431 description 432 "Initial version"; 433 reference 434 "RFC XXXX: A YANG Data Model for OSPF."; 435 } 437 identity two-part-metric { 438 base ospf:informational-capability; 439 description 440 "When set, the router is capable of supporting OSPF 441 two-part metrics."; 442 reference 443 "RFC 8042: OSPF Two-Part Metric"; 444 } 446 /* RFC 8042 */ 447 augment "/rt:routing/rt:control-plane-protocols/" 448 + "rt:control-plane-protocol/ospf:ospf/" 449 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 450 when "../../../../../rt:type = 'ospf:ospfv2' or " 451 + "../../../../../rt:type = 'ospf:ospfv3'" { 452 description 453 "This augments the OSPF interface configuration 454 when used."; 455 } 456 description 457 "This augments the OSPF protocol interface 458 configuration with two-part metric."; 460 container two-part-metric { 461 when "enum-value(../ospf:interface-type) = 2" { 462 description 463 "Two-part metric when link type is multi-access."; 464 } 465 leaf enable { 466 type boolean; 467 default false; 468 description 469 "Enable two-part metric."; 470 } 471 leaf int-input-cost { 472 type ospf:ospf-link-metric; 473 description 474 "Link state metric from the two-part-metric network 475 to this router."; 476 } 477 description 478 "Interface two part metric configuration."; 479 } 480 } 482 augment "/rt:routing/" 483 + "rt:control-plane-protocols/rt:control-plane-protocol/" 484 + "ospf:ospf/ospf:areas/" 485 + "ospf:area/ospf:database/" 486 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 487 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 488 + "ospf:ospfv2/ospf:body/ospf:opaque/" 489 + "ospf:extended-link-opaque/ospf:extended-link-tlv" { 490 when "../../../../../../../../../../../../" 491 + "rt:type = 'ospf:ospfv2'" { 492 description 493 "This augmentation is only valid for OSPFv2."; 494 } 495 description 496 "Network-to-Router metric sub tlv for OSPFv2 extended link TLV 497 in type 10 opaque LSA."; 499 container network-to-router-metric-sub-tlvs { 500 description "Network-to-Router metric sub TLV."; 501 list net-to-rtr-sub-tlv { 502 leaf mt-id { 503 type uint8; 504 description "Multi-Topology Identifier (MT-ID)."; 505 } 506 leaf mt-metric { 507 type uint16; 508 description "Network-to-router metric."; 509 } 510 description 511 "Network-to-Router metric sub-TLV."; 512 } 513 } 514 } 516 augment "/rt:routing/" 517 + "rt:control-plane-protocols/rt:control-plane-protocol/" 518 + "ospf:ospf/ospf:areas/" 519 + "ospf:area/ospf:database/" 520 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 521 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 522 + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:te-opaque/" 523 + "ospf:link-tlv" { 524 when "../../../../../../../../../../../../" 525 + "rt:type = 'ospf:ospfv2'" { 526 description 527 "This augmentation is only valid for OSPFv2."; 528 } 529 description 530 "Traffic Engineering Network-to-Router Sub-TLV."; 531 leaf network-to-router-te-metric { 532 type uint32; 533 description "Network to Router TE metric."; 534 reference 535 "RFC 8042 - OSPF Two-Part Metric"; 536 } 537 } 539 augment "/rt:routing/" 540 + "rt:control-plane-protocols/rt:control-plane-protocol/" 541 + "ospf:ospf/ospf:areas/" 542 + "ospf:area/ospf:database/" 543 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 544 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 545 + "ospf:ospfv3/ospf:body/ospfv3-te:ospfv3-intra-area-te/" 546 + "ospfv3-te:link-tlv" { 547 when "../../../../../../../../../../../" 548 + "rt:type = 'ospf:ospfv3'" { 549 description 550 "This augmentation is only valid for OSPFv3."; 551 } 552 description 553 "Traffic Engineering Network-to-Router Sub-TLV."; 554 leaf network-to-router-te-metric { 555 type uint32; 556 description "Network to Router TE metric."; 557 reference 558 "RFC 8042 - OSPF Two-Part Metric"; 559 } 560 } 561 } 562 564 4. YANG Module for OSPF Graceful Link Shutdown 566 This document defines a YANG module for OSPF Graceful Link Shutdown 567 feature as defined in [RFC8379]. It is an augmentation of the OSPF 568 base model. 570 module: ietf-ospf-graceful-link-shutdown 571 augment /rt:routing/rt:control-plane-protocols 572 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 573 /ospf:interfaces/ospf:interface: 574 +--rw graceful-link-shutdown 575 +--rw enable? boolean 576 augment /rt:routing/rt:control-plane-protocols 577 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 578 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 579 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 580 /ospf:body/ospf:opaque/ospf:extended-link-opaque 581 /ospf:extended-link-tlv: 582 +--ro graceful-link-shutdown-sub-tlv! 583 +--ro remote-address-sub-tlv 584 | +--ro remote-address? inet:ipv4-address 585 +--ro local-remote-int-id-sub-tlv 586 +--ro local-int-id? uint32 587 +--ro remote-int-id? uint32 588 augment /rt:routing/rt:control-plane-protocols 589 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 590 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 591 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 592 /ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 593 /ospfv3-e-lsa:link-tlv: 594 +--ro graceful-link-shutdown-sub-tlv! 596 file "ietf-ospf-graceful-link-shutdown@2020-10-31.yang" 597 module ietf-ospf-graceful-link-shutdown { 598 yang-version 1.1; 599 namespace 600 "urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown"; 602 prefix ospf-grace-linkdown; 604 import ietf-inet-types { 605 prefix "inet"; 606 } 608 import ietf-routing { 609 prefix "rt"; 610 } 612 import ietf-ospf { 613 prefix "ospf"; 614 } 616 import ietf-ospfv3-extended-lsa { 617 prefix "ospfv3-e-lsa"; 618 } 620 organization 621 "IETF LSR - Link State Routing Working Group"; 623 contact 624 "WG Web: 625 WG List: 627 Author: Yingzhen Qu 628 629 Author: Acee Lindem 630 "; 632 description 633 "This YANG module defines the configuration and operational 634 state for OSPF Graceful Link Shutdown feature as defined 635 in RFC 8379. 637 This YANG model conforms to the Network Management 638 Datastore Architecture (NDMA) as described in RFC 8342. 640 Copyright (c) 2020 IETF Trust and the persons identified as 641 authors of the code. All rights reserved. 643 Redistribution and use in source and binary forms, with or 644 without modification, is permitted pursuant to, and subject 645 to the license terms contained in, the Simplified BSD License 646 set forth in Section 4.c of the IETF Trust's Legal Provisions 647 Relating to IETF Documents 648 (http://trustee.ietf.org/license-info). 650 This version of this YANG module is part of RFC XXXX; 651 see the RFC itself for full legal notices."; 653 reference "RFC XXXX"; 655 revision 2020-10-31 { 656 description 657 "Initial version"; 658 reference 659 "RFC XXXX: A YANG Data Model for OSPF."; 660 } 662 /* RFC 8379 */ 663 augment "/rt:routing/rt:control-plane-protocols/" 664 + "rt:control-plane-protocol/ospf:ospf/" 665 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 666 when "../../../../../rt:type = 'ospf:ospfv2' or " 667 + "../../../../../rt:type = 'ospf:ospfv3'" { 668 description 669 "This augments the OSPF interface configuration 670 when used."; 671 } 672 description 673 "This augments the OSPF protocol interface 674 configuration with segment routing."; 676 container graceful-link-shutdown { 677 leaf enable { 678 type boolean; 679 default false; 680 description 681 "Enable OSPF graceful link shutdown."; 682 } 683 description 684 "OSPF Graceful Link Shutdown."; 685 } 686 } 688 /* Database */ 689 augment "/rt:routing/" 690 + "rt:control-plane-protocols/rt:control-plane-protocol/" 691 + "ospf:ospf/ospf:areas/" 692 + "ospf:area/ospf:database/" 693 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 694 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 695 + "ospf:ospfv2/ospf:body/ospf:opaque/" 696 + "ospf:extended-link-opaque/ospf:extended-link-tlv" { 697 when "../../../../../../../../../../../../" 698 + "rt:type = 'ospf:ospfv2'" { 699 description 700 "This augmentation is only valid for OSPFv2."; 701 } 702 description 703 "OSPF graceful link shutdown for OSPFv2 extended link TLV 704 in type 10 opaque LSA."; 706 container graceful-link-shutdown-sub-tlv { 707 presence "Enable graceful link shutdown"; 708 description 709 "Graceful-Link-Shutdown sub-TLV identifies the link as being 710 gracefully shutdown."; 712 } 714 container remote-address-sub-tlv { 715 leaf remote-address { 716 type inet:ipv4-address; 717 description 718 "Remote IPv4 address used to identify a particular link 719 on the remote side."; 720 } 721 description 722 "This sub-TLV specifies the IPv4 address of the remote 723 endpoint on the link."; 724 } 726 container local-remote-int-id-sub-tlv { 727 leaf local-int-id { 728 type uint32; 729 description "Local interface ID."; 730 } 731 leaf remote-int-id { 732 type uint32; 733 description "Remote interface ID."; 734 } 735 description 736 "This sub-TLV specifies Local and Remote Interface IDs."; 737 } 738 } 740 augment "/rt:routing/" 741 + "rt:control-plane-protocols/rt:control-plane-protocol/" 742 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 743 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 744 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 745 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 746 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 747 when "'ospf:../../../../../../../../../" 748 + "rt:type' = 'ospf:ospfv3'" { 749 description 750 "This augmentation is only valid for OSPFv3 751 E-Router LSAs"; 752 } 753 container graceful-link-shutdown-sub-tlv { 754 presence "Enable graceful link shutdown"; 755 description 756 "Graceful-Link-Shutdown sub-TLV identifies the link as being 757 gracefully shutdown."; 758 } 759 description 760 "Augment OSPFv3 Area scope router-link TLV."; 761 } 762 } 763 765 5. YANG Module for OSPF LLS Extenstion for Local Interface ID 766 Advertisement 768 This document defines a YANG module for OSPF Link-Local Signaling 769 (LLS) Extensions for Local Interface ID Advertisement feature as 770 defined in [RFC8510]. It is an augmentation of the OSPF base model. 772 module: ietf-ospf-lls-local-id 773 augment /rt:routing/rt:control-plane-protocols 774 /rt:control-plane-protocol/ospf:ospf: 775 +--rw lls-int-id 776 +--rw enable? boolean 778 file "ietf-ospf-lls-local-id@2020-04-24.yang" 779 module ietf-ospf-lls-local-id { 780 yang-version 1.1; 781 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id"; 783 prefix ospf-lls-localid; 785 import ietf-routing { 786 prefix "rt"; 787 } 789 import ietf-ospf { 790 prefix "ospf"; 791 } 793 organization 794 "IETF LSR - Link State Routing Working Group"; 796 contact 797 "WG Web: 798 WG List: 800 Author: Yingzhen Qu 801 802 Author: Acee Lindem 803 "; 805 description 806 "This YANG module defines the configuration and operational 807 state for OSPF Link-Local Signaling (LLS) Extensions for Local 808 Interface ID Advertisement feature as defined in RFC 8510. 810 Copyright (c) 2019 IETF Trust and the persons identified as 811 authors of the code. All rights reserved. 813 Redistribution and use in source and binary forms, with or 814 without modification, is permitted pursuant to, and subject 815 to the license terms contained in, the Simplified BSD License 816 set forth in Section 4.c of the IETF Trust's Legal Provisions 817 Relating to IETF Documents 818 (http://trustee.ietf.org/license-info). 820 This version of this YANG module is part of RFC XXXX; 821 see the RFC itself for full legal notices."; 823 reference "RFC XXXX"; 825 revision 2020-04-24 { 826 description 827 "Initial version"; 828 reference 829 "RFC XXXX: A YANG Data Model for OSPF."; 830 } 832 augment "/rt:routing/rt:control-plane-protocols" 833 + "/rt:control-plane-protocol/ospf:ospf" { 834 when "../rt:type = 'ospf:ospfv2' or " 835 + "../rt:type = 'ospf:ospfv3'" { 836 description 837 "This augments the OSPF routing protocol when used."; 838 } 839 description 840 "This augments the OSPF protocol configuration 841 to support LLS extesnions for interfacde ID as 842 defined in RFC 8510."; 843 container lls-int-id { 844 leaf enable { 845 type boolean; 846 default false; 847 description 848 "Enable LLS to advertise local interface ID."; 849 } 850 description 851 "OSPF LLS Extensions for interface ID."; 852 } 853 } 854 } 855 857 6. YANG Module for OSPF Application-Specific Link Attributes 859 This document defines a YANG module for OSPF Application-Specific 860 Link Attributes feature as defined in [RFC8920]. It is an 861 augmentation of the OSPF base model. 863 module: ietf-ospf-link-attr 864 augment /rt:routing/rt:control-plane-protocols 865 /rt:control-plane-protocol/ospf:ospf: 866 +--rw ospf-link-attr 867 +--rw (link-attr-op-mode) 868 +--:(legacy) 869 | +--rw legacy? empty 870 +--:(transition) 871 | +--rw transition? empty 872 +--:(app-specific) 873 +--rw app-specific? empty 874 augment /rt:routing/rt:control-plane-protocols 875 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 876 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 877 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 878 /ospf:body/ospf:opaque/ospf:extended-link-opaque 879 /ospf:extended-link-tlv: 880 +--ro application-specific-link-attributes-sub-tlvs 881 +--ro asla-sub-tlvs* [] 882 +--ro sabm-length? uint8 883 +--ro udabm-length? uint8 884 +--ro sabm 885 | +--ro sabm-bits* identityref 886 +--ro udabm 887 +--ro link-attributes-sub-sub-tlvs 888 +--ro unknown-tlvs 889 +--ro unknown-tlv* [] 890 +--ro type? uint16 891 +--ro length? uint16 892 +--ro value? yang:hex-string 893 augment /rt:routing/rt:control-plane-protocols 894 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 895 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 896 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 897 /ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 898 /ospfv3-e-lsa:link-tlv: 899 +--ro application-specific-link-attributes-sub-tlvs 900 +--ro asla-sub-tlvs* [] 901 +--ro sabm-length? uint8 902 +--ro udabm-length? uint8 903 +--ro sabm 904 | +--ro sabm-bits* identityref 905 +--ro udabm 906 +--ro link-attributes-sub-sub-tlvs 907 +--ro unknown-tlvs 908 +--ro unknown-tlv* [] 909 +--ro type? uint16 910 +--ro length? uint16 911 +--ro value? yang:hex-string 913 file "ietf-ospf-link-attr@2020-10-31.yang" 914 module ietf-ospf-link-attr { 915 yang-version 1.1; 916 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr"; 918 prefix ospf-link-attr; 920 import ietf-routing { 921 prefix "rt"; 922 reference "RFC 8349: A YANG Data Model for Routing 923 Management (NMDA Version)"; 924 } 926 import ietf-ospf { 927 prefix "ospf"; 928 } 930 import ietf-ospfv3-extended-lsa { 931 prefix "ospfv3-e-lsa"; 932 } 934 organization 935 "IETF LSR - Link State Routing Working Group"; 937 contact 938 "WG Web: 939 WG List: 941 Author: Yingzhen Qu 942 943 Author: Acee Lindem 944 945 Author: Stephane Litkowski 946 "; 948 description 949 "This YANG module defines the configuration and operational 950 state for OSPF application specific link attributes feature 951 as defined in RFC xxxx. 953 This YANG model conforms to the Network Management 954 Datastore Architecture (NMDA) as described in RFC 8342. 956 Copyright (c) 2020 IETF Trust and the persons identified as 957 authors of the code. All rights reserved. 959 Redistribution and use in source and binary forms, with or 960 without modification, is permitted pursuant to, and subject 961 to the license terms contained in, the Simplified BSD License 962 set forth in Section 4.c of the IETF Trust's Legal Provisions 963 Relating to IETF Documents 964 (http://trustee.ietf.org/license-info). 966 This version of this YANG module is part of RFC XXXX; 967 see the RFC itself for full legal notices. 969 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 970 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 971 'MAY', and 'OPTIONAL' in this document are to be interpreted as 972 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 973 they appear in all capitals, as shown here."; 975 reference "RFC XXXX"; 977 revision 2020-10-31 { 978 description 979 "Initial version"; 980 reference 981 "RFC XXXX: A YANG Data Model for OSPF application specific 982 link attributes."; 983 } 985 identity sabm-bit { 986 description 987 "Base identity for sabm bits."; 988 } 990 identity rsvp-te-bit { 991 base sabm-bit; 992 description 993 "R bit, RSVP-TE."; 994 } 996 identity sr-policy-bit { 997 base sabm-bit; 998 description 999 "S bit, Segment Routing Policy."; 1000 } 1002 identity lfa-bit { 1003 base sabm-bit; 1004 description 1005 "F bit, Loop Free Alternate (LFA). Includes all LFA types."; 1006 } 1008 grouping application-specific-link-attributes-sub-tlvs { 1009 description 1010 "OSPF Application-Specific Link Attributes (ASLA) sub-TLV. 1011 The ASLA sub-TLV is a sub-TLV of the OSPFv2 Extended Link 1012 TLV [RFC7684] and OSPFv3 Router-Link TLV [RFC8362]."; 1014 container application-specific-link-attributes-sub-tlvs { 1015 description "Application-Specific Link Attributes sub-TLV."; 1016 list asla-sub-tlvs { 1017 leaf sabm-length { 1018 type uint8; 1019 description 1020 "Standard Application Identifier Bit Mask Length in 1021 octets."; 1022 } 1023 leaf udabm-length { 1024 type uint8; 1025 description 1026 "User Defined Application Identifier Bit Mask Length 1027 in octets."; 1028 } 1029 container sabm { 1030 leaf-list sabm-bits { 1031 type identityref { 1032 base sabm-bit; 1033 } 1034 description 1035 "SABM bits list. This list will contain 1036 identities for the bits which are set in the 1037 SABA bits."; 1038 } 1039 description 1040 "Standard Application Identifier Bit Mask."; 1041 } 1042 container udabm { 1043 description 1044 "User Defined Application Identifier Bit Mask. 1045 This container is to be augmented by user defined 1046 applications."; 1048 } 1049 container link-attributes-sub-sub-tlvs { 1050 uses ospf:unknown-tlvs; 1051 description 1052 "Link Attributes sub-sub-TLVs."; 1053 } 1054 description 1055 "List of application-Specific Link Attributes sub-TLVs."; 1056 } 1057 } 1058 } 1060 augment "/rt:routing/rt:control-plane-protocols" 1061 + "/rt:control-plane-protocol/ospf:ospf" { 1062 when "../rt:type = 'ospf:ospfv2' or " 1063 + "../rt:type = 'ospf:ospfv3'" { 1064 description 1065 "This augments the OSPF routing protocol when used."; 1066 } 1067 description 1068 "This augments OSPF protocol configuration 1069 with application-specific link attributes."; 1071 container ospf-link-attr { 1072 choice link-attr-op-mode { 1073 mandatory "true"; 1074 leaf legacy { 1075 type empty; 1076 description 1077 "Only send legacy advertisements."; 1078 } 1079 leaf transition { 1080 type empty; 1081 description 1082 "Send both application-specific and legacy 1083 advertisements."; 1084 } 1085 leaf app-specific{ 1086 type empty; 1087 description 1088 "Only send application-specific advertisements."; 1089 } 1090 description 1091 "Link attributes mode"; 1092 } 1093 description 1094 "Link attributes operation mode."; 1095 } 1097 } 1099 /* Database */ 1100 augment "/rt:routing/" 1101 + "rt:control-plane-protocols/rt:control-plane-protocol/" 1102 + "ospf:ospf/ospf:areas/" 1103 + "ospf:area/ospf:database/" 1104 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 1105 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 1106 + "ospf:ospfv2/ospf:body/ospf:opaque/" 1107 + "ospf:extended-link-opaque/ospf:extended-link-tlv" { 1108 when "../../../../../../../../../../../../" 1109 + "rt:type = 'ospf:ospfv2'" { 1110 description 1111 "This augmentation is only valid for OSPFv2."; 1112 } 1113 description 1114 "OSPF Application-Specific Link Attributes (ASLA) sub-TLV is 1115 a sub-TLV of OSPFv2 Extended Link TLV (RFC7684)."; 1117 uses application-specific-link-attributes-sub-tlvs; 1118 } 1120 augment "/rt:routing/" 1121 + "rt:control-plane-protocols/rt:control-plane-protocol/" 1122 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 1123 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 1124 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 1125 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 1126 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 1127 when "'ospf:../../../../../../../../../" 1128 + "rt:type' = 'ospf:ospfv3'" { 1129 description 1130 "This augmentation is only valid for OSPFv3 1131 E-Router LSAs"; 1132 } 1133 description 1134 "Augment OSPFv3 Area scope router-link TLV."; 1136 uses application-specific-link-attributes-sub-tlvs; 1137 } 1138 } 1139 1141 7. Security Considerations 1143 The YANG modules specified in this document define a schema for data 1144 that is designed to be accessed via network management protocols such 1145 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1146 is the secure transport layer, and the mandatory-to-implement secure 1147 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1148 is HTTPS, and the mandatory-to-implement secure transport is TLS 1149 [RFC5246]. 1151 The NETCONF access control model [RFC6536] provides the means to 1152 restrict access for particular NETCONF or RESTCONF users to a pre- 1153 configured subset of all available NETCONF or RESTCONF protocol 1154 operations and content. 1156 There are a number of data nodes defined in the modules that are 1157 writable/creatable/deletable (i.e., config true, which is the 1158 default). These data nodes may be considered sensitive or vulnerable 1159 in some network environments. Write operations (e.g., edit-config) 1160 to these data nodes without proper protection can have a negative 1161 effect on network operations. 1163 Some of the readable data nodes in the modules may be considered 1164 sensitive or vulnerable in some network environments. It is thus 1165 important to control read access (e.g., via get, get-config, or 1166 notification) to these data nodes. The exposure of the Link State 1167 Database (LSDB) will expose the detailed topology of the network. 1168 This may be undesirable since both due to the fact that exposure may 1169 facilitate other attacks. Additionally, network operators may 1170 consider their topologies to be sensitive confidential data. 1172 8. IANA Considerations 1174 This document registers URIs in the IETF XML registry [RFC3688]. 1175 Following the format in [RFC3688], the following registrations is 1176 requested to be made: 1178 URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te 1179 Registrant Contact: The IESG. 1180 XML: N/A, the requested URI is an XML namespace. 1182 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 1183 Registrant Contact: The IESG. 1184 XML: N/A, the requested URI is an XML namespace. 1186 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 1187 Registrant Contact: The IESG. 1188 XML: N/A, the requested URI is an XML namespace. 1190 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 1191 Registrant Contact: The IESG. 1192 XML: N/A, the requested URI is an XML namespace. 1194 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr 1195 Registrant Contact: The IESG. 1196 XML: N/A, the requested URI is an XML namespace. 1198 This document registers the YANG modules in the YANG Module Names 1199 registry [RFC6020]. 1201 name: ietf-ospfv3-te 1202 namespace: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te 1203 prefix: ospfv3-te 1204 reference: RFC XXXX 1206 name: ietf-ospf-two-metric 1207 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 1208 prefix: ospf-two-metric 1209 reference: RFC XXXX 1211 name: ietf-ospf-grace-linkdown 1212 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 1213 prefix: ospf-grace-linkdown 1214 reference: RFC XXXX 1216 name: ietf-ospf-lls-localid 1217 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 1218 prefix: ospf-lls-localid 1219 reference: RFC XXXX 1221 name: ietf-ospf-link-attr 1222 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr 1223 prefix: ospf-link-attr 1224 reference: RFC XXXX 1226 9. Acknowledgements 1228 This document was produced using Marshall Rose's xml2rfc tool. 1230 The YANG model was developed using the suite of YANG tools written 1231 and maintained by numerous authors. 1233 10. Normative References 1235 [I-D.ietf-ospf-yang] 1236 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 1237 "YANG Data Model for OSPF Protocol", draft-ietf-ospf- 1238 yang-29 (work in progress), October 2019. 1240 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1241 Requirement Levels", BCP 14, RFC 2119, 1242 DOI 10.17487/RFC2119, March 1997, 1243 . 1245 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1246 DOI 10.17487/RFC3688, January 2004, 1247 . 1249 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 1250 (TLS) Protocol Version 1.2", RFC 5246, 1251 DOI 10.17487/RFC5246, August 2008, 1252 . 1254 [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., 1255 "Traffic Engineering Extensions to OSPF Version 3", 1256 RFC 5329, DOI 10.17487/RFC5329, September 2008, 1257 . 1259 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1260 the Network Configuration Protocol (NETCONF)", RFC 6020, 1261 DOI 10.17487/RFC6020, October 2010, 1262 . 1264 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1265 and A. Bierman, Ed., "Network Configuration Protocol 1266 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1267 . 1269 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1270 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1271 . 1273 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1274 Protocol (NETCONF) Access Control Model", RFC 6536, 1275 DOI 10.17487/RFC6536, March 2012, 1276 . 1278 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1279 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1280 . 1282 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 1283 Management", RFC 8022, DOI 10.17487/RFC8022, November 1284 2016, . 1286 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1287 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1288 . 1290 [RFC8042] Zhang, Z., Wang, L., and A. Lindem, "OSPF Two-Part 1291 Metric", RFC 8042, DOI 10.17487/RFC8042, December 2016, 1292 . 1294 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 1295 Routing Management (NMDA Version)", RFC 8349, 1296 DOI 10.17487/RFC8349, March 2018, 1297 . 1299 [RFC8379] Hegde, S., Sarkar, P., Gredler, H., Nanduri, M., and L. 1300 Jalil, "OSPF Graceful Link Shutdown", RFC 8379, 1301 DOI 10.17487/RFC8379, May 2018, 1302 . 1304 [RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P. 1305 Pillay-Esnault, "OSPF Link-Local Signaling (LLS) 1306 Extensions for Local Interface ID Advertisement", 1307 RFC 8510, DOI 10.17487/RFC8510, January 2019, 1308 . 1310 [RFC8920] Psenak, P., Ed., Ginsberg, L., Henderickx, W., Tantsura, 1311 J., and J. Drake, "OSPF Application-Specific Link 1312 Attributes", RFC 8920, DOI 10.17487/RFC8920, October 2020, 1313 . 1315 Authors' Addresses 1317 Acee Lindem 1318 Cisco Systems 1319 301 Midenhall Way 1320 Cary, NC 27513 1322 EMail: acee@cisco.com 1323 Yingzhen Qu 1324 Futurewei 1325 2330 Central Expressway 1326 Santa Clara, CA 95050 1327 USA 1329 EMail: yingzhen.qu@futurewei.com