idnits 2.17.1 draft-ietf-lsr-ospf-yang-augmentation-v1-02.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 : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 137 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 (July 12, 2020) is 1383 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) 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: January 13, 2021 Futurewei 6 July 12, 2020 8 OSPF YANG Model Augmentations for Additional Features - Version 1 9 draft-ietf-lsr-ospf-yang-augmentation-v1-02 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 January 13, 2021. 37 Copyright Notice 39 Copyright (c) 2020 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 . . . . . . . . . 12 60 5. YANG Module for OSPF LLS Extenstion for Local Interface ID 61 Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 17 62 6. YANG Module for OSPF Application-Specific Link Attributes . . 19 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 65 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 28 68 10.2. Informative References . . . . . . . . . . . . . . . . . 29 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 71 1. Overview 73 YANG [RFC6020] [RFC7950] is a data definition language used to define 74 the contents of a conceptual data store that allows networked devices 75 to be managed using NETCONF [RFC6241]. YANG is proving relevant 76 beyond its initial confines, as bindings to other interfaces (e.g., 77 ReST) and encodings other than XML (e.g., JSON) are being defined. 78 Furthermore, YANG data models can be used as the basis for 79 implementation of other interfaces, such as CLI and programmatic 80 APIs. 82 This document defines YANG data modules augmenting the IETF OSPF YANG 83 model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to 84 provide support for configuration and operational state for the 85 following OSPF features: 87 RFC5329: Traffic Engineering Extensions to OSPF Version 3 [RFC5329]. 89 RFC8042: OSPF Two-Part Metric [RFC8042]. 91 RFC8379: OSPF Graceful Link Shutdown [RFC8379]. 93 RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local 94 Interface ID Advertisement[RFC8510]. 96 The augmentations defined in this document requires support for the 97 OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF 98 configuration and state. The OSPF YANG model augments the ietf- 99 routing YANG model defined in [RFC8022]. 101 1.1. Requirements Language 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 2. YANG Module for Traffic Engineering Extesions to OSPF Version 3 109 This document defines a YANG module for Traffic Engineering 110 Extersions to OSPF Version 3 as defined in [RFC5329]. It is an 111 augmentation of the OSPF base model. 113 module: ietf-ospfv3-te 114 augment /rt:routing/rt:control-plane-protocols 115 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 116 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 117 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 118 /ospf:body: 119 +--ro ospfv3-intra-area-te 120 +--ro router-address-tlv 121 | +--ro router-address? inet:ipv6-address 122 +--ro link-tlv 123 +--ro link-type ospf:router-link-type 124 +--ro local-if-ipv6-addrs 125 | +--ro local-if-ipv6-addr* inet:ipv6-address 126 +--ro remote-if-ipv6-addrs 127 | +--ro remote-if-ipv6-addr* inet:ipv6-address 128 +--ro te-metric? uint32 129 +--ro max-bandwidth? rt-types:bandwidth-ieee-float32 130 +--ro max-reservable-bandwidth? rt-types:bandwidth-ieee-float32 131 +--ro unreserved-bandwidths 132 | +--ro unreserved-bandwidth* 133 | +--ro priority? uint8 134 | +--ro unreserved-bandwidth? rt-types:bandwidth-ieee-float32 135 +--ro admin-group? uint32 136 +--ro neighbor-id 137 | +--ro nbr-interface-id inet:ipv4-address 138 | +--ro nbr-router-id yang:dotted-quad 139 +--ro unknown-tlvs 140 +--ro unknown-tlv* 141 +--ro type? uint16 142 +--ro length? uint16 143 +--ro value? yang:hex-string 145 file "ietf-ospfv3-te@2020-04-24.yang" 146 module ietf-ospfv3-te { 147 yang-version 1.1; 148 namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-te"; 150 prefix ospfv3-te; 152 import ietf-inet-types { 153 prefix "inet"; 154 reference "RFC 6991: Common YANG Data Types"; 155 } 157 import ietf-yang-types { 158 prefix "yang"; 159 reference "RFC 6991: Common YANG Data Types"; 160 } 162 import ietf-routing-types { 163 prefix "rt-types"; 164 reference "RFC 8294: Common YANG Data Types for the 165 Routing Area"; 166 } 168 import ietf-routing { 169 prefix "rt"; 170 } 172 import ietf-ospf { 173 prefix "ospf"; 174 } 176 organization 177 "IETF LSR - Link State Routing Working Group"; 179 contact 180 "WG Web: 181 WG List: 183 Author: Yingzhen Qu 184 185 Author: Acee Lindem 186 "; 188 description 189 "This YANG module defines the configuration and operational 190 state for OSPFv3 extensions to support intra-area Traffic 191 Engineering (TE) as defined in RFC 5329. 193 Copyright (c) 2019 IETF Trust and the persons identified as 194 authors of the code. All rights reserved. 196 Redistribution and use in source and binary forms, with or 197 without modification, is permitted pursuant to, and subject 198 to the license terms contained in, the Simplified BSD License 199 set forth in Section 4.c of the IETF Trust's Legal Provisions 200 Relating to IETF Documents 201 (http://trustee.ietf.org/license-info). 203 This version of this YANG module is part of RFC XXXX; 204 see the RFC itself for full legal notices."; 206 reference "RFC XXXX"; 208 revision 2020-04-24 { 209 description 210 "Initial version"; 211 reference 212 "RFC XXXX: A YANG Data Model for OSPFv3 TE."; 213 } 215 identity ospfv3-intra-area-te-lsa { 216 base ospf:ospfv3-lsa-type; 217 description 218 "OSPFv3 Intrea-area TE LSA."; 219 } 221 grouping ospfv3-intra-area-te { 222 description "Grouping for OSPFv3 intra-area-te-lsa."; 223 container ospfv3-intra-area-te { 224 container router-address-tlv { 225 description "The router IPv6 address tlv advertises a reachable 226 IPv6 address."; 227 leaf router-address { 228 type inet:ipv6-address; 229 description 230 "Router IPv6 address."; 231 } 232 } 234 container link-tlv { 235 description "Describes a singel link, and it is constructed 236 of a set of Sub-TLVs."; 237 leaf link-type { 238 type ospf:router-link-type; 239 mandatory true; 240 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"; 385 prefix ospf-two-metric; 387 import ietf-routing { 388 prefix "rt"; 389 } 391 import ietf-ospf { 392 prefix "ospf"; 393 } 395 import ietf-ospfv3-te { 396 prefix "ospfv3-te"; 397 } 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"; 434 reference 435 "RFC XXXX: A YANG Data Model for OSPF."; 436 } 438 identity two-part-metric { 439 base ospf:informational-capability; 440 description 441 "When set, the router is capable of supporting OSPF 442 two-part metrics."; 443 reference 444 "RFC 8042: OSPF Two-Part Metric"; 445 } 447 /* RFC 8042 */ 448 augment "/rt:routing/rt:control-plane-protocols/" 449 + "rt:control-plane-protocol/ospf:ospf/" 450 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 451 when "../../../../../rt:type = 'ospf:ospfv2' or " 452 + "../../../../../rt:type = 'ospf:ospfv3'" { 453 description 454 "This augments the OSPF interface configuration 455 when used."; 456 } 457 description 458 "This augments the OSPF protocol interface 459 configuration with two-part metric."; 461 container two-part-metric { 462 when "enum-value(../ospf:interface-type) = 2" { 463 description 464 "Two-part metric when link type is multi-access."; 465 } 466 leaf enable { 467 type boolean; 468 default false; 469 description 470 "Enable two-part metric."; 471 } 472 leaf int-input-cost { 473 type ospf:ospf-link-metric; 474 description 475 "Link state metric from the two-part-metric network 476 to this router."; 477 } 478 description 479 "Interface two part metric configuration."; 480 } 481 } 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! 595 augment /rt:routing/rt:control-plane-protocols 596 /rt:control-plane-protocol/ospf:ospf/ospf:database 597 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 598 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 599 /ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 600 /ospfv3-e-lsa:link-tlv: 601 +--ro graceful-link-shutdown-sub-tlv! 603 file "ietf-ospf-graceful-link-shutdown@2020-04-24.yang" 604 module ietf-ospf-graceful-link-shutdown { 605 yang-version 1.1; 606 namespace 607 "urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown"; 609 prefix ospf-grace-linkdown; 611 import ietf-inet-types { 612 prefix "inet"; 613 } 615 import ietf-routing { 616 prefix "rt"; 618 } 620 import ietf-ospf { 621 prefix "ospf"; 622 } 624 import ietf-ospfv3-extended-lsa { 625 prefix "ospfv3-e-lsa"; 626 } 628 organization 629 "IETF LSR - Link State Routing Working Group"; 631 contact 632 "WG Web: 633 WG List: 635 Author: Yingzhen Qu 636 637 Author: Acee Lindem 638 "; 640 description 641 "This YANG module defines the configuration and operational 642 state for OSPF Graceful Link Shutdown feature as defined 643 in RFC 8379. 645 Copyright (c) 2019 IETF Trust and the persons identified as 646 authors of the code. All rights reserved. 648 Redistribution and use in source and binary forms, with or 649 without modification, is permitted pursuant to, and subject 650 to the license terms contained in, the Simplified BSD License 651 set forth in Section 4.c of the IETF Trust's Legal Provisions 652 Relating to IETF Documents 653 (http://trustee.ietf.org/license-info). 655 This version of this YANG module is part of RFC XXXX; 656 see the RFC itself for full legal notices."; 658 reference "RFC XXXX"; 660 revision 2020-04-24 { 661 description 662 "Initial version"; 663 reference 664 "RFC XXXX: A YANG Data Model for OSPF."; 666 } 668 /* RFC 8379 */ 669 augment "/rt:routing/rt:control-plane-protocols/" 670 + "rt:control-plane-protocol/ospf:ospf/" 671 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 672 when "../../../../../rt:type = 'ospf:ospfv2' or " 673 + "../../../../../rt:type = 'ospf:ospfv3'" { 674 description 675 "This augments the OSPF interface configuration 676 when used."; 677 } 678 description 679 "This augments the OSPF protocol interface 680 configuration with segment routing."; 682 container graceful-link-shutdown { 683 leaf enable { 684 type boolean; 685 default false; 686 description 687 "Enable OSPF graceful link shutdown."; 688 } 689 description 690 "OSPF Graceful Link Shutdown."; 691 } 692 } 694 /* Database */ 695 augment "/rt:routing/" 696 + "rt:control-plane-protocols/rt:control-plane-protocol/" 697 + "ospf:ospf/ospf:areas/" 698 + "ospf:area/ospf:database/" 699 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 700 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 701 + "ospf:ospfv2/ospf:body/ospf:opaque/" 702 + "ospf:extended-link-opaque/ospf:extended-link-tlv" { 703 when "../../../../../../../../../../../../" 704 + "rt:type = 'ospf:ospfv2'" { 705 description 706 "This augmentation is only valid for OSPFv2."; 707 } 708 description 709 "OSPF graceful link shutdown for OSPFv2 extended link TLV 710 in type 10 opaque LSA."; 712 container graceful-link-shutdown-sub-tlv { 713 presence "Enable graceful link shutdown"; 714 description 715 "Graceful-Link-Shutdown sub-TLV identifies the link as being 716 gracefully shutdown."; 717 } 719 container remote-address-sub-tlv { 720 leaf remote-address { 721 type inet:ipv4-address; 722 description 723 "Remote IPv4 address used to identify a particular link 724 on the remote side."; 725 } 726 description 727 "This sub-TLV specifies the IPv4 address of the remote 728 endpoint on the link."; 729 } 731 container local-remote-int-id-sub-tlv { 732 leaf local-int-id { 733 type uint32; 734 description "Local interface ID."; 735 } 736 leaf remote-int-id { 737 type uint32; 738 description "Remote interface ID."; 739 } 740 description 741 "This sub-TLV specifies Local and Remote Interface IDs."; 742 } 743 } 745 augment "/rt:routing/" 746 + "rt:control-plane-protocols/rt:control-plane-protocol/" 747 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 748 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 749 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 750 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 751 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 752 when "'ospf:../../../../../../../../../" 753 + "rt:type' = 'ospf:ospfv3'" { 754 description 755 "This augmentation is only valid for OSPFv3 756 E-Router LSAs"; 757 } 758 container graceful-link-shutdown-sub-tlv { 759 presence "Enable graceful link shutdown"; 760 description 761 "Graceful-Link-Shutdown sub-TLV identifies the link as being 762 gracefully shutdown."; 763 } 764 description 765 "Augemnt OSPFv3 Area scope router-link TLV."; 766 } 768 augment "/rt:routing/" 769 + "rt:control-plane-protocols/rt:control-plane-protocol/" 770 + "ospf:ospf/ospf:database/" 771 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 772 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 773 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 774 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 775 when "'ospf:../../../../../../../" 776 + "rt:type' = 'ospf:ospfv3'" { 777 description 778 "This augmentation is only valid for OSPFv3 779 E-Router LSAs"; 780 } 781 container graceful-link-shutdown-sub-tlv { 782 presence "Enable graceful link shutdown"; 783 description 784 "Graceful-Link-Shutdown sub-TLV identifies the link as being 785 gracefully shutdown."; 786 } 787 description 788 "Augemnt OSPFv3 AS scope router-link TLV."; 789 } 790 } 791 793 5. YANG Module for OSPF LLS Extenstion for Local Interface ID 794 Advertisement 796 This document defines a YANG module for OSPF Link-Local Signaling 797 (LLS) Extensions for Local Interface ID Advertisement feature as 798 defined in [RFC8510]. It is an augmentation of the OSPF base model. 800 module: ietf-ospf-lls-local-id 801 augment /rt:routing/rt:control-plane-protocols 802 /rt:control-plane-protocol/ospf:ospf: 803 +--rw lls-int-id 804 +--rw enable? boolean 806 file "ietf-ospf-lls-local-id@2020-04-24.yang" 807 module ietf-ospf-lls-local-id { 808 yang-version 1.1; 809 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id"; 811 prefix ospf-lls-localid; 813 import ietf-routing { 814 prefix "rt"; 815 } 817 import ietf-ospf { 818 prefix "ospf"; 819 } 821 organization 822 "IETF LSR - Link State Routing Working Group"; 824 contact 825 "WG Web: 826 WG List: 828 Author: Yingzhen Qu 829 830 Author: Acee Lindem 831 "; 833 description 834 "This YANG module defines the configuration and operational 835 state for OSPF Link-Local Signaling (LLS) Extensions for Local 836 Interface ID Advertisement feature as defined in RFC 8510. 838 Copyright (c) 2019 IETF Trust and the persons identified as 839 authors of the code. All rights reserved. 841 Redistribution and use in source and binary forms, with or 842 without modification, is permitted pursuant to, and subject 843 to the license terms contained in, the Simplified BSD License 844 set forth in Section 4.c of the IETF Trust's Legal Provisions 845 Relating to IETF Documents 846 (http://trustee.ietf.org/license-info). 848 This version of this YANG module is part of RFC XXXX; 849 see the RFC itself for full legal notices."; 851 reference "RFC XXXX"; 853 revision 2020-04-24 { 854 description 855 "Initial version"; 856 reference 857 "RFC XXXX: A YANG Data Model for OSPF."; 858 } 860 augment "/rt:routing/rt:control-plane-protocols" 861 + "/rt:control-plane-protocol/ospf:ospf" { 862 when "../rt:type = 'ospf:ospfv2' or " 863 + "../rt:type = 'ospf:ospfv3'" { 864 description 865 "This augments the OSPF routing protocol when used."; 866 } 867 description 868 "This augments the OSPF protocol configuration 869 to support LLS extesnions for interfacde ID as 870 defined in RFC 8510."; 871 container lls-int-id { 872 leaf enable { 873 type boolean; 874 default false; 875 description 876 "Enable LLS to advertise local interface ID."; 877 } 878 description 879 "OSPF LLS Extensions for interface ID."; 880 } 881 } 882 } 883 885 6. YANG Module for OSPF Application-Specific Link Attributes 887 This document defines a YANG module for OSPF Application-Specific 888 Link Attributes feature as defined in 889 [I-D.ietf-ospf-te-link-attr-reuse]. It is an augmentation of the 890 OSPF base model. 892 module: ietf-ospf-link-attr 893 augment /rt:routing/rt:control-plane-protocols 894 /rt:control-plane-protocol/ospf:ospf: 895 +--rw ospf-link-attr 896 +--rw (link-attr-op-mode) 897 +--:(legacy) 898 | +--rw legacy? empty 899 +--:(transition) 900 | +--rw transition? empty 901 +--:(app-specific) 902 +--rw app-specific? empty 904 augment /rt:routing/rt:control-plane-protocols 905 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 906 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 907 /ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2 908 /ospf:body/ospf:opaque/ospf:extended-link-opaque 909 /ospf:extended-link-tlv: 910 +--ro application-specific-link-attributes-sub-tlvs 911 +--ro asla-sub-tlvs* [] 912 +--ro sabm-length? uint8 913 +--ro udabm-length? uint8 914 +--ro sabm 915 | +--ro sabm-bits* identityref 916 +--ro udabm 917 +--ro link-attributes-sub-sub-tlvs 918 +--ro unknown-tlvs 919 +--ro unknown-tlv* [] 920 +--ro type? uint16 921 +--ro length? uint16 922 +--ro value? yang:hex-string 923 augment /rt:routing/rt:control-plane-protocols 924 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 925 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 926 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 927 /ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 928 /ospfv3-e-lsa:link-tlv: 929 +--ro application-specific-link-attributes-sub-tlvs 930 +--ro asla-sub-tlvs* [] 931 +--ro sabm-length? uint8 932 +--ro udabm-length? uint8 933 +--ro sabm 934 | +--ro sabm-bits* identityref 935 +--ro udabm 936 +--ro link-attributes-sub-sub-tlvs 937 +--ro unknown-tlvs 938 +--ro unknown-tlv* [] 939 +--ro type? uint16 940 +--ro length? uint16 941 +--ro value? yang:hex-string 942 augment /rt:routing/rt:control-plane-protocols 943 /rt:control-plane-protocol/ospf:ospf/ospf:database 944 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 945 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 946 /ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 947 /ospfv3-e-lsa:link-tlv: 948 +--ro application-specific-link-attributes-sub-tlvs 949 +--ro asla-sub-tlvs* [] 950 +--ro sabm-length? uint8 951 +--ro udabm-length? uint8 952 +--ro sabm 953 | +--ro sabm-bits* identityref 954 +--ro udabm 955 +--ro link-attributes-sub-sub-tlvs 956 +--ro unknown-tlvs 957 +--ro unknown-tlv* [] 958 +--ro type? uint16 959 +--ro length? uint16 960 +--ro value? yang:hex-string 962 file "ietf-ospf-link-attr@2020-07-12.yang" 963 module ietf-ospf-link-attr { 964 yang-version 1.1; 965 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr"; 967 prefix ospf-link-attr; 969 import ietf-routing { 970 prefix "rt"; 971 reference "RFC 8349: A YANG Data Model for Routing 972 Management (NMDA Version)"; 973 } 975 import ietf-ospf { 976 prefix "ospf"; 977 } 979 import ietf-ospfv3-extended-lsa { 980 prefix "ospfv3-e-lsa"; 981 } 983 organization 984 "IETF LSR - Link State Routing Working Group"; 986 contact 987 "WG Web: 988 WG List: 990 Author: Yingzhen Qu 991 992 Author: Acee Lindem 993 994 Author: Stephane Litkowski 995 "; 997 description 998 "This YANG module defines the configuration and operational 999 state for OSPF application specific link attributes feature 1000 as defined in RFC xxxx. 1002 This YANG model conforms to the Network Management 1003 Datastore Architecture (NMDA) as described in RFC 8242. 1005 Copyright (c) 2020 IETF Trust and the persons identified as 1006 authors of the code. All rights reserved. 1008 Redistribution and use in source and binary forms, with or 1009 without modification, is permitted pursuant to, and subject 1010 to the license terms contained in, the Simplified BSD License 1011 set forth in Section 4.c of the IETF Trust's Legal Provisions 1012 Relating to IETF Documents 1013 (http://trustee.ietf.org/license-info). 1015 This version of this YANG module is part of RFC XXXX; 1016 see the RFC itself for full legal notices. 1018 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 1019 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 1020 'MAY', and 'OPTIONAL' in this document are to be interpreted as 1021 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 1022 they appear in all capitals, as shown here."; 1024 reference "RFC XXXX"; 1026 revision 2020-07-12 { 1027 description 1028 "Initial version"; 1029 reference 1030 "RFC XXXX: A YANG Data Model for OSPF application specific 1031 link attributes."; 1032 } 1034 identity sabm-bit { 1035 description 1036 "Base identity for sabm bits."; 1037 } 1039 identity rsvp-te-bit { 1040 base sabm-bit; 1041 description 1042 "R bit, RSVP-TE."; 1043 } 1045 identity sr-policy-bit { 1046 base sabm-bit; 1047 description 1048 "S bit, Segment Routing Policy."; 1049 } 1051 identity lfa-bit { 1052 base sabm-bit; 1053 description 1054 "F bit, Loop Free Alternate (LFA). Includes all LFA types."; 1055 } 1057 grouping application-specific-link-attributes-sub-tlvs { 1058 description 1059 "OSPF Application-Specific Link Attributes (ASLA) sub-TLV. 1060 The ASLA sub-TLV is a sub-TLV of the OSPFv2 Extended Link 1061 TLV [RFC7684] and OSPFv3 Router-Link TLV [RFC8362]."; 1063 container application-specific-link-attributes-sub-tlvs { 1064 description "Application-Specific Link Attributes sub-TLV."; 1065 list asla-sub-tlvs { 1066 leaf sabm-length { 1067 type uint8; 1068 description 1069 "Standard Application Identifier Bit Mask Length in 1070 octets."; 1071 } 1072 leaf udabm-length { 1073 type uint8; 1074 description 1075 "User Defined Application Identifier Bit Mask Length 1076 in octets."; 1077 } 1078 container sabm { 1079 leaf-list sabm-bits { 1080 type identityref { 1081 base sabm-bit; 1082 } 1083 description 1084 "SABM bits list. This list will contain 1085 identities for the bits which are set in the 1086 SABA bits."; 1087 } 1088 description 1089 "Standard Application Identifier Bit Mask."; 1090 } 1091 container udabm { 1092 description 1093 "User Defined Application Identifier Bit Mask. 1094 This container is to be augmented by user defined 1095 applications."; 1096 } 1097 container link-attributes-sub-sub-tlvs { 1098 uses ospf:unknown-tlvs; 1099 description 1100 "Link Attributes sub-sub-TLVs."; 1101 } 1102 } 1103 } 1104 } 1106 augment "/rt:routing/rt:control-plane-protocols" 1107 + "/rt:control-plane-protocol/ospf:ospf" { 1108 when "../rt:type = 'ospf:ospfv2' or " 1109 + "../rt:type = 'ospf:ospfv3'" { 1110 description 1111 "This augments the OSPF routing protocol when used."; 1112 } 1113 description 1114 "This augments OSPF protocol configuration 1115 with application-specific link attributes."; 1117 container ospf-link-attr { 1118 choice link-attr-op-mode { 1119 mandatory "true"; 1120 leaf legacy { 1121 type empty; 1122 description 1123 "Only send legacy advertisements."; 1124 } 1125 leaf transition { 1126 type empty; 1127 description 1128 "Send both application-specific and legacy advertisements."; 1129 } 1130 leaf app-specific{ 1131 type empty; 1132 description 1133 "Only send application-specific advertisements."; 1134 } 1135 description 1136 "Link attributes mode"; 1137 } 1138 description 1139 "Link attributes operation mode."; 1140 } 1141 } 1142 /* Database */ 1143 augment "/rt:routing/" 1144 + "rt:control-plane-protocols/rt:control-plane-protocol/" 1145 + "ospf:ospf/ospf:areas/" 1146 + "ospf:area/ospf:database/" 1147 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 1148 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 1149 + "ospf:ospfv2/ospf:body/ospf:opaque/" 1150 + "ospf:extended-link-opaque/ospf:extended-link-tlv" { 1151 when "../../../../../../../../../../../../" 1152 + "rt:type = 'ospf:ospfv2'" { 1153 description 1154 "This augmentation is only valid for OSPFv2."; 1155 } 1156 description 1157 "OSPF Application-Specific Link Attributes (ASLA) sub-TLV is 1158 a sub-TLV of OSPFv2 Extended Link TLV (RFC7684)."; 1160 uses application-specific-link-attributes-sub-tlvs; 1161 } 1163 augment "/rt:routing/" 1164 + "rt:control-plane-protocols/rt:control-plane-protocol/" 1165 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 1166 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 1167 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 1168 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 1169 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 1170 when "'ospf:../../../../../../../../../" 1171 + "rt:type' = 'ospf:ospfv3'" { 1172 description 1173 "This augmentation is only valid for OSPFv3 1174 E-Router LSAs"; 1175 } 1176 description 1177 "Augment OSPFv3 Area scope router-link TLV."; 1179 uses application-specific-link-attributes-sub-tlvs; 1180 } 1182 augment "/rt:routing/" 1183 + "rt:control-plane-protocols/rt:control-plane-protocol/" 1184 + "ospf:ospf/ospf:database/" 1185 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 1186 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 1187 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 1188 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 1189 when "'ospf:../../../../../../../" 1190 + "rt:type' = 'ospf:ospfv3'" { 1191 description 1192 "This augmentation is only valid for OSPFv3 1193 E-Router LSAs"; 1194 } 1195 description 1196 "Augment OSPFv3 AS scope router-link TLV."; 1198 uses application-specific-link-attributes-sub-tlvs; 1199 } 1200 } 1201 1203 7. Security Considerations 1205 The YANG modules specified in this document define a schema for data 1206 that is designed to be accessed via network management protocols such 1207 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1208 is the secure transport layer, and the mandatory-to-implement secure 1209 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1210 is HTTPS, and the mandatory-to-implement secure transport is TLS 1211 [RFC5246]. 1213 The NETCONF access control model [RFC6536] provides the means to 1214 restrict access for particular NETCONF or RESTCONF users to a pre- 1215 configured subset of all available NETCONF or RESTCONF protocol 1216 operations and content. 1218 There are a number of data nodes defined in the modules that are 1219 writable/creatable/deletable (i.e., config true, which is the 1220 default). These data nodes may be considered sensitive or vulnerable 1221 in some network environments. Write operations (e.g., edit-config) 1222 to these data nodes without proper protection can have a negative 1223 effect on network operations. 1225 Some of the readable data nodes in the modules may be considered 1226 sensitive or vulnerable in some network environments. It is thus 1227 important to control read access (e.g., via get, get-config, or 1228 notification) to these data nodes. The exposure of the Link State 1229 Database (LSDB) will expose the detailed topology of the network. 1230 This may be undesirable since both due to the fact that exposure may 1231 facilitate other attacks. Additionally, network operators may 1232 consider their topologies to be sensitive confidential data. 1234 8. IANA Considerations 1236 This document registers URIs in the IETF XML registry [RFC3688]. 1237 Following the format in [RFC3688], the following registrations is 1238 requested to be made: 1240 URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te 1241 Registrant Contact: The IESG. 1242 XML: N/A, the requested URI is an XML namespace. 1244 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 1245 Registrant Contact: The IESG. 1246 XML: N/A, the requested URI is an XML namespace. 1248 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 1249 Registrant Contact: The IESG. 1250 XML: N/A, the requested URI is an XML namespace. 1252 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 1253 Registrant Contact: The IESG. 1254 XML: N/A, the requested URI is an XML namespace. 1256 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr 1257 Registrant Contact: The IESG. 1258 XML: N/A, the requested URI is an XML namespace. 1260 This document registers the YANG modules in the YANG Module Names 1261 registry [RFC6020]. 1263 name: ietf-ospfv3-te 1264 namespace: urn:ietf:params:xml:ns:yang:ietf-ospfv3-te 1265 prefix: ospfv3-te 1266 reference: RFC XXXX 1268 name: ietf-ospf-two-metric 1269 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 1270 prefix: ospf-two-metric 1271 reference: RFC XXXX 1273 name: ietf-ospf-grace-linkdown 1274 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 1275 prefix: ospf-grace-linkdown 1276 reference: RFC XXXX 1278 name: ietf-ospf-lls-localid 1279 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 1280 prefix: ospf-lls-localid 1281 reference: RFC XXXX 1282 name: ietf-ospf-link-attr 1283 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-link-attr 1284 prefix: ospf-link-attr 1285 reference: RFC XXXX 1287 9. Acknowledgements 1289 This document was produced using Marshall Rose's xml2rfc tool. 1291 The YANG model was developed using the suite of YANG tools written 1292 and maintained by numerous authors. 1294 10. References 1296 10.1. Normative References 1298 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1299 Requirement Levels", BCP 14, RFC 2119, 1300 DOI 10.17487/RFC2119, March 1997, 1301 . 1303 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1304 DOI 10.17487/RFC3688, January 2004, 1305 . 1307 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 1308 (TLS) Protocol Version 1.2", RFC 5246, 1309 DOI 10.17487/RFC5246, August 2008, 1310 . 1312 [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., 1313 "Traffic Engineering Extensions to OSPF Version 3", 1314 RFC 5329, DOI 10.17487/RFC5329, September 2008, 1315 . 1317 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1318 the Network Configuration Protocol (NETCONF)", RFC 6020, 1319 DOI 10.17487/RFC6020, October 2010, 1320 . 1322 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1323 and A. Bierman, Ed., "Network Configuration Protocol 1324 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1325 . 1327 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1328 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1329 . 1331 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1332 Protocol (NETCONF) Access Control Model", RFC 6536, 1333 DOI 10.17487/RFC6536, March 2012, 1334 . 1336 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1337 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1338 . 1340 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 1341 Management", RFC 8022, DOI 10.17487/RFC8022, November 1342 2016, . 1344 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1345 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1346 . 1348 [RFC8042] Zhang, Z., Wang, L., and A. Lindem, "OSPF Two-Part 1349 Metric", RFC 8042, DOI 10.17487/RFC8042, December 2016, 1350 . 1352 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 1353 Routing Management (NMDA Version)", RFC 8349, 1354 DOI 10.17487/RFC8349, March 2018, 1355 . 1357 [RFC8379] Hegde, S., Sarkar, P., Gredler, H., Nanduri, M., and L. 1358 Jalil, "OSPF Graceful Link Shutdown", RFC 8379, 1359 DOI 10.17487/RFC8379, May 2018, 1360 . 1362 [RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P. 1363 Pillay-Esnault, "OSPF Link-Local Signaling (LLS) 1364 Extensions for Local Interface ID Advertisement", 1365 RFC 8510, DOI 10.17487/RFC8510, January 2019, 1366 . 1368 10.2. Informative References 1370 [I-D.ietf-ospf-te-link-attr-reuse] 1371 Psenak, P., Ginsberg, L., Henderickx, W., Tantsura, J., 1372 and J. Drake, "OSPF Application-Specific Link Attributes", 1373 draft-ietf-ospf-te-link-attr-reuse-16 (work in progress), 1374 June 2020. 1376 [I-D.ietf-ospf-yang] 1377 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 1378 "YANG Data Model for OSPF Protocol", draft-ietf-ospf- 1379 yang-29 (work in progress), October 2019. 1381 Authors' Addresses 1383 Acee Lindem 1384 Cisco Systems 1385 301 Midenhall Way 1386 Cary, NC 27513 1388 EMail: acee@cisco.com 1390 Yingzhen Qu 1391 Futurewei 1392 2330 Central Expressway 1393 Santa Clara, CA 95050 1394 USA 1396 EMail: yingzhen.qu@futurewei.com