idnits 2.17.1 draft-acee-lsr-ospf-yang-augmentation-v1-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 (July 7, 2019) is 1749 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** 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) == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-23 Summary: 3 errors (**), 0 flaws (~~), 3 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: Informational Y. Qu 5 Expires: January 8, 2020 Futurewei 6 July 7, 2019 8 OSPF YANG Model Augmentations for Additional Features - Version 1 9 draft-acee-lsr-ospf-yang-augmentation-v1-00 11 Abstract 13 This document defines YANG data modules augmenting the IETF OSPF YANG 14 model to provide support for OSPF Two-Part Metric as defined in RFC 15 8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and OSPF 16 Link-Local Signaling (LLS) Extensions for Local Interface ID 17 Advertisement as defined in RFC 8510. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 8, 2020. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 2. YANG Module for OSPF Two-Part Metric . . . . . . . . . . . . 3 56 3. YANG Module for OSPF Graceful Link Shutdown . . . . . . . . . 6 57 4. YANG Module for OSPF LLS Extenstion for Local Interface ID 58 Advertisement . . . . . . . . . . . . . . . . . . . . . . . . 11 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 61 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 62 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 63 8.1. Normative References . . . . . . . . . . . . . . . . . . 15 64 8.2. Informative References . . . . . . . . . . . . . . . . . 16 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 67 1. Overview 69 YANG [RFC6020] [RFC7950] is a data definition language used to define 70 the contents of a conceptual data store that allows networked devices 71 to be managed using NETCONF [RFC6241]. YANG is proving relevant 72 beyond its initial confines, as bindings to other interfaces (e.g., 73 ReST) and encodings other than XML (e.g., JSON) are being defined. 74 Furthermore, YANG data models can be used as the basis for 75 implementation of other interfaces, such as CLI and programmatic 76 APIs. 78 This document defines YANG data modules augmenting the IETF OSPF YANG 79 model [I-D.ietf-ospf-yang], which itself augments [RFC8349], to 80 provide support for configuration and operational state for the 81 following OSPF features: 83 RFC8042: OSPF Two-Part Metric [RFC8042]. 85 RFC8379: OSPF Graceful Link Shutdown [RFC8379]. 87 RFC8510: OSPF Link-Local Signaling (LLS) Extensions for Local 88 Interface ID Advertisement[RFC8510]. 90 The augmentations defined in this document requires support for the 91 OSPF base model[I-D.ietf-ospf-yang] which defines basic OSPF 92 configuration and state. The OSPF YANG model augments the ietf- 93 routing YANG model defined in [RFC8022]. 95 1.1. Requirements Language 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119]. 101 2. YANG Module for OSPF Two-Part Metric 103 This document defines a YANG module for OSPF Two-Part Metric feature 104 as defined in [RFC8042]. It is an augmentation of the OSPF base 105 model. 107 module: ietf-ospf-two-part-metric 108 augment /rt:routing/rt:control-plane-protocols 109 /rt:control-plane-protocol/ospf:ospf/ospf:areas 110 /ospf:area/ospf:interfaces/ospf:interface: 111 +--rw two-part-metric 112 +--rw enable? boolean 113 +--rw int-input-cost? uint16 114 augment /rt:routing/rt:control-plane-protocols 115 /rt:control-plane-protocol/ospf:ospf/ospf:areas 116 /ospf:area/ospf:database/ospf:area-scope-lsa-type 117 /ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version 118 /ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque 119 /ospf:extended-link-tlvs/ospf:extended-link-tlv: 120 +--ro network-to-router-metric-sub-tlvs 121 +--ro net-to-rtr-sub-tlv* 122 +--ro mt-id? uint8 123 +--ro mt-metric? uint16 125 file "ietf-ospf-two-part-metric@2019-07-05.yang" 126 module ietf-ospf-two-part-metric { 127 yang-version 1.1; 128 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-two-part-metric"; 130 prefix ospf-two-metric; 132 import ietf-routing { 133 prefix "rt"; 134 } 136 import ietf-ospf { 137 prefix "ospf"; 138 } 140 organization 141 "IETF LSR - Link State Routing Working Group"; 143 contact 144 "WG Web: 145 WG List: 147 Author: Yingzhen Qu 148 149 Author: Acee Lindem 150 "; 152 description 153 "This YANG module defines the configuration and operational 154 state for OSPF Two-Part Metric feature as defined in RFC 8042. 156 Copyright (c) 2019 IETF Trust and the persons identified as 157 authors of the code. All rights reserved. 159 Redistribution and use in source and binary forms, with or 160 without modification, is permitted pursuant to, and subject 161 to the license terms contained in, the Simplified BSD License 162 set forth in Section 4.c of the IETF Trust's Legal Provisions 163 Relating to IETF Documents 164 (http://trustee.ietf.org/license-info). 166 This version of this YANG module is part of RFC XXXX; 167 see the RFC itself for full legal notices."; 169 reference "RFC XXXX"; 171 revision 2019-07-05 { 172 description 173 "Initial version"; 174 reference 175 "RFC XXXX: A YANG Data Model for OSPF."; 176 } 178 /* RFC 8042 */ 179 augment "/rt:routing/rt:control-plane-protocols/" 180 + "rt:control-plane-protocol/ospf:ospf/" 181 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 182 when "../../../../../rt:type = 'ospf:ospfv2' or " 183 + "../../../../../rt:type = 'ospf:ospfv3'" { 184 description 185 "This augments the OSPF interface configuration 186 when used."; 187 } 188 description 189 "This augments the OSPF protocol interface 190 configuration with two-part metric."; 192 container two-part-metric { 193 when "enum-value(../ospf:interface-type) = 2" { 194 description 195 "Two-part metric when link type is multi-access."; 196 } 197 leaf enable { 198 type boolean; 199 default false; 200 description 201 "Enable two-part metric."; 202 } 203 leaf int-input-cost { 204 type uint16; 205 description 206 "Link state metric from the two-part-metric network 207 to this router."; 208 } 209 description 210 "Interface two part metric configuration."; 211 } 212 } 214 augment "/rt:routing/" 215 + "rt:control-plane-protocols/rt:control-plane-protocol/" 216 + "ospf:ospf/ospf:areas/" 217 + "ospf:area/ospf:database/" 218 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 219 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 220 + "ospf:ospfv2/ospf:body/ospf:opaque/" 221 + "ospf:extended-link-tlvs/ospf:extended-link-tlv" { 222 when "../../../../../../../../../../../../" 223 + "rt:type = 'ospf:ospfv2'" { 224 description 225 "This augmentation is only valid for OSPFv2."; 226 } 227 description 228 "Network-to-Router metric sub tlv for OSPFv2 extended link TLV 229 in type 10 opaque LSA."; 231 container network-to-router-metric-sub-tlvs { 232 description "Network-to-Router metric sub TLV."; 233 list net-to-rtr-sub-tlv { 234 leaf mt-id { 235 type uint8; 236 description "Multi-Topology Identifier (MT-ID)."; 237 } 238 leaf mt-metric { 239 type uint16; 240 description "Network-to-router metric."; 241 } 242 description 243 "Network-to-Router metric sub-TLV."; 244 } 245 } 246 } 247 } 248 250 3. YANG Module for OSPF Graceful Link Shutdown 252 This document defines a YANG module for OSPF Graceful Link Shutdown 253 feature as defined in [RFC8379]. It is an augmentation of the OSPF 254 base model. 256 module: ietf-ospf-graceful-link-shutdown 257 augment /rt:routing/rt:control-plane-protocols 258 /rt:control-plane-protocol/ospf:ospf/ospf:areas 259 /ospf:area/ospf:interfaces/ospf:interface: 260 +--rw graceful-link-shutdown 261 +--rw enable? boolean 262 augment /rt:routing/rt:control-plane-protocols 263 /rt:control-plane-protocol/ospf:ospf/ospf:areas 264 /ospf:area/ospf:database/ospf:area-scope-lsa-type 265 /ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version 266 /ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque 267 /ospf:extended-link-tlvs/ospf:extended-link-tlv: 268 +--ro grace-link-shut-sub-tlv! 269 +--ro remote-address-sub-tlv 270 | +--ro remote-address? inet:ipv4-address 271 +--ro local-remote-int-id-sub-tlv 272 +--ro local-int-id? uint32 273 +--ro remote-int-id? uint32 274 augment /rt:routing/rt:control-plane-protocols 275 /rt:control-plane-protocol/ospf:ospf/ospf:areas 276 /ospf:area/ospf:database/ospf:area-scope-lsa-type 277 /ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version 278 /ospf:ospfv3/ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router 279 /ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv: 280 +--ro grace-link-shut-sub-tlv! 281 augment /rt:routing/rt:control-plane-protocols 282 /rt:control-plane-protocol/ospf:ospf/ospf:database 283 /ospf:as-scope-lsa-type/ospf:as-scope-lsas 284 /ospf:as-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 285 /ospf:body/ospfv3-e-lsa:e-router 286 /ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv: 287 +--ro grace-link-shut-sub-tlv! 289 file "ietf-ospf-graceful-link-shutdown@2019-07-05.yang" 290 module ietf-ospf-graceful-link-shutdown { 291 yang-version 1.1; 292 namespace 293 "urn:ietf:params:xml:ns:yang:ietf-ospf-graceful-link-shutdown"; 295 prefix ospf-grace-linkdown; 297 import ietf-inet-types { 298 prefix "inet"; 299 } 301 import ietf-routing { 302 prefix "rt"; 304 } 306 import ietf-ospf { 307 prefix "ospf"; 308 } 310 import ietf-ospfv3-extended-lsa { 311 prefix "ospfv3-e-lsa"; 312 } 314 organization 315 "IETF LSR - Link State Routing Working Group"; 317 contact 318 "WG Web: 319 WG List: 321 Author: Yingzhen Qu 322 323 Author: Acee Lindem 324 "; 326 description 327 "This YANG module defines the configuration and operational 328 state for OSPF Graceful Link Shutdown feature as defined 329 in RFC 8379. 331 Copyright (c) 2019 IETF Trust and the persons identified as 332 authors of the code. All rights reserved. 334 Redistribution and use in source and binary forms, with or 335 without modification, is permitted pursuant to, and subject 336 to the license terms contained in, the Simplified BSD License 337 set forth in Section 4.c of the IETF Trust's Legal Provisions 338 Relating to IETF Documents 339 (http://trustee.ietf.org/license-info). 341 This version of this YANG module is part of RFC XXXX; 342 see the RFC itself for full legal notices."; 344 reference "RFC XXXX"; 346 revision 2019-07-05 { 347 description 348 "Initial version"; 349 reference 350 "RFC XXXX: A YANG Data Model for OSPF."; 352 } 354 /* RFC 8379 */ 355 augment "/rt:routing/rt:control-plane-protocols/" 356 + "rt:control-plane-protocol/ospf:ospf/" 357 + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { 358 when "../../../../../rt:type = 'ospf:ospfv2' or " 359 + "../../../../../rt:type = 'ospf:ospfv3'" { 360 description 361 "This augments the OSPF interface configuration 362 when used."; 363 } 364 description 365 "This augments the OSPF protocol interface 366 configuration with segment routing."; 368 container graceful-link-shutdown { 369 leaf enable { 370 type boolean; 371 default false; 372 description 373 "Enable OSPF graceful link shutdown."; 374 } 375 description 376 "OSPF Graceful Link Shutdown."; 377 } 378 } 380 /* Database */ 381 augment "/rt:routing/" 382 + "rt:control-plane-protocols/rt:control-plane-protocol/" 383 + "ospf:ospf/ospf:areas/" 384 + "ospf:area/ospf:database/" 385 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 386 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" 387 + "ospf:ospfv2/ospf:body/ospf:opaque/" 388 + "ospf:extended-link-tlvs/ospf:extended-link-tlv" { 389 when "../../../../../../../../../../../../" 390 + "rt:type = 'ospf:ospfv2'" { 391 description 392 "This augmentation is only valid for OSPFv2."; 393 } 394 description 395 "OSPF graceful link shutdown for OSPFv2 extended link TLV 396 in type 10 opaque LSA."; 398 container graceful-link-shutdown-sub-tlv { 399 presence "Enable graceful link shutdown"; 400 description 401 "Graceful-Link-Shutdown sub-TLV identifies the link as being 402 gracefully shutdown."; 403 } 405 container remote-address-sub-tlv { 406 leaf remote-address { 407 type inet:ipv4-address; 408 description 409 "Remote IPv4 address used to identify a particular link 410 on the remote side."; 411 } 412 description 413 "This sub-TLV specifies the IPv4 address of the remote 414 endpoint on the link."; 415 } 417 container local-remote-int-id-sub-tlv { 418 leaf local-int-id { 419 type uint32; 420 description "Local interface ID."; 421 } 422 leaf remote-int-id { 423 type uint32; 424 description "Remote interface ID."; 425 } 426 description 427 "This sub-TLV specifies Local and Remote Interface IDs."; 428 } 429 } 431 augment "/rt:routing/" 432 + "rt:control-plane-protocols/rt:control-plane-protocol/" 433 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 434 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 435 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 436 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 437 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 438 when "'ospf:../../../../../../../../../" 439 + "rt:type' = 'ospf:ospfv3'" { 440 description 441 "This augmentation is only valid for OSPFv3 442 E-Router LSAs"; 443 } 444 container graceful-link-shutdown-sub-tlv { 445 presence "Enable graceful link shutdown"; 446 description 447 "Graceful-Link-Shutdown sub-TLV identifies the link as being 448 gracefully shutdown."; 449 } 450 description 451 "Augemnt OSPFv3 Area scope router-link TLV."; 452 } 454 augment "/rt:routing/" 455 + "rt:control-plane-protocols/rt:control-plane-protocol/" 456 + "ospf:ospf/ospf:database/" 457 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 458 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 459 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" 460 + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 461 when "'ospf:../../../../../../../" 462 + "rt:type' = 'ospf:ospfv3'" { 463 description 464 "This augmentation is only valid for OSPFv3 465 E-Router LSAs"; 466 } 467 container graceful-link-shutdown-sub-tlv { 468 presence "Enable graceful link shutdown"; 469 description 470 "Graceful-Link-Shutdown sub-TLV identifies the link as being 471 gracefully shutdown."; 472 } 473 description 474 "Augemnt OSPFv3 AS scope router-link TLV."; 475 } 476 } 477 479 4. YANG Module for OSPF LLS Extenstion for Local Interface ID 480 Advertisement 482 This document defines a YANG module for OSPF Link-Local Signaling 483 (LLS) Extensions for Local Interface ID Advertisement feature as 484 defined in [RFC8510]. It is an augmentation of the OSPF base model. 486 module: ietf-ospf-lls-local-id 487 augment /rt:routing/rt:control-plane-protocols 488 /rt:control-plane-protocol/ospf:ospf: 489 +--rw lls-int-id 490 +--rw enable? boolean 492 file "ietf-ospf-lls-local-id@2019-07-05.yang" 493 module ietf-ospf-lls-local-id { 494 yang-version 1.1; 495 namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-lls-local-id"; 497 prefix ospf-lls-localid; 499 import ietf-routing { 500 prefix "rt"; 501 } 503 import ietf-ospf { 504 prefix "ospf"; 505 } 507 organization 508 "IETF LSR - Link State Routing Working Group"; 510 contact 511 "WG Web: 512 WG List: 514 Author: Yingzhen Qu 515 516 Author: Acee Lindem 517 "; 519 description 520 "This YANG module defines the configuration and operational 521 state for OSPF Link-Local Signaling (LLS) Extensions for Local 522 Interface ID Advertisement feature as defined in RFC 8510. 524 Copyright (c) 2019 IETF Trust and the persons identified as 525 authors of the code. All rights reserved. 527 Redistribution and use in source and binary forms, with or 528 without modification, is permitted pursuant to, and subject 529 to the license terms contained in, the Simplified BSD License 530 set forth in Section 4.c of the IETF Trust's Legal Provisions 531 Relating to IETF Documents 532 (http://trustee.ietf.org/license-info). 534 This version of this YANG module is part of RFC XXXX; 535 see the RFC itself for full legal notices."; 537 reference "RFC XXXX"; 539 revision 2019-07-05 { 540 description 541 "Initial version"; 542 reference 543 "RFC XXXX: A YANG Data Model for OSPF."; 544 } 546 augment "/rt:routing/rt:control-plane-protocols" 547 + "/rt:control-plane-protocol/ospf:ospf" { 548 when "../rt:type = 'ospf:ospfv2' or " 549 + "../rt:type = 'ospf:ospfv3'" { 550 description 551 "This augments the OSPF routing protocol when used."; 552 } 553 description 554 "This augments the OSPF protocol configuration 555 to support LLS extesnions for interfacde ID as 556 defined in RFC 8510."; 557 container lls-int-id { 558 leaf enable { 559 type boolean; 560 default false; 561 description 562 "Enable LLS to advertise local interface ID."; 563 } 564 description 565 "OSPF LLS Extensions for interface ID."; 566 } 567 } 568 } 569 571 5. Security Considerations 573 The YANG modules specified in this document define a schema for data 574 that is designed to be accessed via network management protocols such 575 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 576 is the secure transport layer, and the mandatory-to-implement secure 577 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 578 is HTTPS, and the mandatory-to-implement secure transport is TLS 579 [RFC5246]. 581 The NETCONF access control model [RFC6536] provides the means to 582 restrict access for particular NETCONF or RESTCONF users to a pre- 583 configured subset of all available NETCONF or RESTCONF protocol 584 operations and content. 586 There are a number of data nodes defined in the modules that are 587 writable/creatable/deletable (i.e., config true, which is the 588 default). These data nodes may be considered sensitive or vulnerable 589 in some network environments. Write operations (e.g., edit-config) 590 to these data nodes without proper protection can have a negative 591 effect on network operations. 593 Some of the readable data nodes in the modules may be considered 594 sensitive or vulnerable in some network environments. It is thus 595 important to control read access (e.g., via get, get-config, or 596 notification) to these data nodes. The exposure of the Link State 597 Database (LSDB) will expose the detailed topology of the network. 598 This may be undesirable since both due to the fact that exposure may 599 facilitate other attacks. Additionally, network operators may 600 consider their topologies to be sensitive confidential data. 602 6. IANA Considerations 604 This document registers URIs in the IETF XML registry [RFC3688]. 605 Following the format in [RFC3688], the following registrations is 606 requested to be made: 608 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 609 Registrant Contact: The IESG. 610 XML: N/A, the requested URI is an XML namespace. 612 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 613 Registrant Contact: The IESG. 614 XML: N/A, the requested URI is an XML namespace. 616 URI: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 617 Registrant Contact: The IESG. 618 XML: N/A, the requested URI is an XML namespace. 620 This document registers the YANG modules in the YANG Module Names 621 registry [RFC6020]. 623 name: ietf-ospf-two-metric 624 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-two-metric 625 prefix: ospf-two-metric 626 reference: RFC XXXX 628 name: ietf-ospf-grace-linkdown 629 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-grace-linkdown 630 prefix: ospf-grace-linkdown 631 reference: RFC XXXX 633 name: ietf-ospf-lls-localid 634 namespace: urn:ietf:params:xml:ns:yang:ietf-ospf-lls-localid 635 prefix: ospf-lls-localid 636 reference: RFC XXXX 638 7. Acknowledgements 640 This document was produced using Marshall Rose's xml2rfc tool. 642 The YANG model was developed using the suite of YANG tools written 643 and maintained by numerous authors. 645 8. References 647 8.1. Normative References 649 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 650 Requirement Levels", BCP 14, RFC 2119, 651 DOI 10.17487/RFC2119, March 1997, 652 . 654 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 655 DOI 10.17487/RFC3688, January 2004, 656 . 658 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 659 (TLS) Protocol Version 1.2", RFC 5246, 660 DOI 10.17487/RFC5246, August 2008, 661 . 663 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 664 the Network Configuration Protocol (NETCONF)", RFC 6020, 665 DOI 10.17487/RFC6020, October 2010, 666 . 668 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 669 and A. Bierman, Ed., "Network Configuration Protocol 670 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 671 . 673 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 674 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 675 . 677 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 678 Protocol (NETCONF) Access Control Model", RFC 6536, 679 DOI 10.17487/RFC6536, March 2012, 680 . 682 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 683 RFC 7950, DOI 10.17487/RFC7950, August 2016, 684 . 686 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 687 Management", RFC 8022, DOI 10.17487/RFC8022, November 688 2016, . 690 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 691 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 692 . 694 [RFC8042] Zhang, Z., Wang, L., and A. Lindem, "OSPF Two-Part 695 Metric", RFC 8042, DOI 10.17487/RFC8042, December 2016, 696 . 698 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 699 Routing Management (NMDA Version)", RFC 8349, 700 DOI 10.17487/RFC8349, March 2018, 701 . 703 [RFC8379] Hegde, S., Sarkar, P., Gredler, H., Nanduri, M., and L. 704 Jalil, "OSPF Graceful Link Shutdown", RFC 8379, 705 DOI 10.17487/RFC8379, May 2018, 706 . 708 [RFC8510] Psenak, P., Ed., Talaulikar, K., Henderickx, W., and P. 709 Pillay-Esnault, "OSPF Link-Local Signaling (LLS) 710 Extensions for Local Interface ID Advertisement", 711 RFC 8510, DOI 10.17487/RFC8510, January 2019, 712 . 714 8.2. Informative References 716 [I-D.ietf-ospf-yang] 717 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 718 "YANG Data Model for OSPF Protocol", draft-ietf-ospf- 719 yang-23 (work in progress), July 2019. 721 Authors' Addresses 723 Acee Lindem 724 Cisco Systems 725 301 Midenhall Way 726 Cary, NC 27513 728 EMail: acee@cisco.com 729 Yingzhen Qu 730 Futurewei 731 2330 Central Expressway 732 Santa Clara, CA 95050 733 USA 735 EMail: yingzhen.qu@futurewei.com