idnits 2.17.1 draft-acee-lsr-ospfv3-sr-yang-07.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 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 (21 April 2022) is 730 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC8341' is defined on line 895, but no explicit reference was found in the text == Outdated reference: A later version (-30) exists of draft-ietf-ospf-sr-yang-17 ** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349) Summary: 1 error (**), 0 flaws (~~), 5 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: 23 October 2022 Futurewei 6 21 April 2022 8 YANG Data Model for OSPFv3 Segment Routing 9 draft-acee-lsr-ospfv3-sr-yang-07 11 Abstract 13 This document defines a YANG data module augmenting the IETF OSPF 14 Segment Routing (SR) YANG model to support OSPFv3 extensions for SR. 15 It can be used to configure and manage OSPFv3 Segment Routing in MPLS 16 data plane. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on 23 October 2022. 35 Copyright Notice 37 Copyright (c) 2022 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Revised BSD License text as 46 described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Revised BSD License. 49 Table of Contents 51 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 53 2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. OSPFv3 Extensions for Segment Routing . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 17 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 57 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 58 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 59 7.1. Normative References . . . . . . . . . . . . . . . . . . 18 60 7.2. Informative References . . . . . . . . . . . . . . . . . 20 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 63 1. Overview 65 YANG [RFC7950] is a data definition language used to define the 66 contents of a conceptual data store that allows networked devices to 67 be managed using NETCONF [RFC6241]. YANG is proving relevant beyond 68 its initial confines, as bindings to other interfaces (e.g., ReST) 69 and encodings other than XML (e.g., JSON) are being defined. 70 Furthermore, YANG data models can be used as the basis for 71 implementation of other interfaces, such as CLI and programmatic 72 APIs. 74 This document defines a YANG data module augmenting the IETF OSPF SR 75 YANG model [I-D.ietf-ospf-sr-yang], and can be used to configure and 76 manage OSPFv3 extensions for Segment Routing with the MPLS data 77 plane. [RFC8666]. 79 The augmentation defined in this document requires support for both 80 the OSPF SR model and the OSPF base model[I-D.ietf-ospf-yang]. 82 1.1. Requirements Language 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC2119]. 88 2. Tree Diagrams 90 Tree diagrams used in this document follow the notation defined in 91 [RFC8340]. 93 3. OSPFv3 Extensions for Segment Routing 95 This document defines a YANG module for OSPFv3 extensions for Segment 96 Routing [RFC8666]. It is an augmentation of the OSPF SR base YANG 97 model, where the configuration for both OSPFv2 and OSPFv3 are 98 defined. 100 [RFC8022] and [RFC8349] are not referenced in the document text but 101 within the YANG module itself. 103 module: ietf-ospfv3-sr 104 augment /rt:routing/rt:control-plane-protocols 105 /rt:control-plane-protocol/ospf:ospf/ospf:database 106 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 107 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 108 /ospf:router-information: 109 +--ro sr-algorithm-tlv 110 | +--ro sr-algorithm* uint8 111 +--ro sid-range-tlvs 112 | +--ro sid-range-tlv* [] 113 | +--ro range-size? uint24 114 | +--ro sid-sub-tlv 115 | +--ro sid? uint32 116 +--ro local-block-tlvs 117 | +--ro local-block-tlv* [] 118 | +--ro range-size? uint24 119 | +--ro sid-sub-tlv 120 | +--ro sid? uint32 121 +--ro srms-preference-tlv 122 +--ro preference? uint8 123 augment /rt:routing/rt:control-plane-protocols 124 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 125 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 126 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 127 /ospf:body/ospf:router-information: 128 +--ro sr-algorithm-tlv 129 | +--ro sr-algorithm* uint8 130 +--ro sid-range-tlvs 131 | +--ro sid-range-tlv* [] 132 | +--ro range-size? uint24 133 | +--ro sid-sub-tlv 134 | +--ro sid? uint32 135 +--ro local-block-tlvs 136 | +--ro local-block-tlv* [] 137 | +--ro range-size? uint24 138 | +--ro sid-sub-tlv 139 | +--ro sid? uint32 140 +--ro srms-preference-tlv 141 +--ro preference? uint8 142 augment /rt:routing/rt:control-plane-protocols 143 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 144 /ospf:interfaces/ospf:interface/ospf:database 145 /ospf:link-scope-lsa-type/ospf:link-scope-lsas 146 /ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 147 /ospf:body/ospf:router-information: 148 +--ro sr-algorithm-tlv 149 | +--ro sr-algorithm* uint8 150 +--ro sid-range-tlvs 151 | +--ro sid-range-tlv* [] 152 | +--ro range-size? uint24 153 | +--ro sid-sub-tlv 154 | +--ro sid? uint32 155 +--ro local-block-tlvs 156 | +--ro local-block-tlv* [] 157 | +--ro range-size? uint24 158 | +--ro sid-sub-tlv 159 | +--ro sid? uint32 160 +--ro srms-preference-tlv 161 +--ro preference? uint8 162 augment /rt:routing/rt:control-plane-protocols 163 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 164 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 165 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 166 /ospf:body/ospfv3-e-lsa:e-intra-area-prefix: 167 +--ro ospfv3-extended-prefix-range-tlvs 168 +--ro extended-prefix-range-tlv* [] 169 +--ro prefix-length? uint8 170 +--ro af? uint8 171 +--ro range-size? uint16 172 +--ro prefix? inet:ip-prefix 173 +--ro perfix-sid-sub-tlvs 174 | +--ro prefix-sid-sub-tlv* [] 175 | +--ro ospfv3-prefix-sid-flags 176 | | +--ro bits* identityref 177 | +--ro algorithm? uint8 178 | +--ro sid? uint32 179 +--ro unknown-tlvs 180 +--ro unknown-tlv* [] 181 +--ro type? uint16 182 +--ro length? uint16 183 +--ro value? yang:hex-string 184 augment /rt:routing/rt:control-plane-protocols 185 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 186 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 187 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 188 /ospf:body/ospfv3-e-lsa:e-inter-area-prefix: 190 +--ro ospfv3-extended-prefix-range-tlvs 191 +--ro extended-prefix-range-tlv* [] 192 +--ro prefix-length? uint8 193 +--ro af? uint8 194 +--ro range-size? uint16 195 +--ro prefix? inet:ip-prefix 196 +--ro perfix-sid-sub-tlvs 197 | +--ro prefix-sid-sub-tlv* [] 198 | +--ro ospfv3-prefix-sid-flags 199 | | +--ro bits* identityref 200 | +--ro algorithm? uint8 201 | +--ro sid? uint32 202 +--ro unknown-tlvs 203 +--ro unknown-tlv* [] 204 +--ro type? uint16 205 +--ro length? uint16 206 +--ro value? yang:hex-string 207 augment /rt:routing/rt:control-plane-protocols 208 /rt:control-plane-protocol/ospf:ospf/ospf:database 209 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 210 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 211 /ospfv3-e-lsa:e-as-external: 212 +--ro ospfv3-extended-prefix-range-tlvs 213 +--ro extended-prefix-range-tlv* [] 214 +--ro prefix-length? uint8 215 +--ro af? uint8 216 +--ro range-size? uint16 217 +--ro prefix? inet:ip-prefix 218 +--ro perfix-sid-sub-tlvs 219 | +--ro prefix-sid-sub-tlv* [] 220 | +--ro ospfv3-prefix-sid-flags 221 | | +--ro bits* identityref 222 | +--ro algorithm? uint8 223 | +--ro sid? uint32 224 +--ro unknown-tlvs 225 +--ro unknown-tlv* [] 226 +--ro type? uint16 227 +--ro length? uint16 228 +--ro value? yang:hex-string 229 augment /rt:routing/rt:control-plane-protocols 230 /rt:control-plane-protocol/ospf:ospf/ospf:database 231 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 232 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 233 /ospfv3-e-lsa:e-nssa: 234 +--ro ospfv3-extended-prefix-range-tlvs 235 +--ro extended-prefix-range-tlv* [] 236 +--ro prefix-length? uint8 237 +--ro af? uint8 238 +--ro range-size? uint16 239 +--ro prefix? inet:ip-prefix 240 +--ro perfix-sid-sub-tlvs 241 | +--ro prefix-sid-sub-tlv* [] 242 | +--ro ospfv3-prefix-sid-flags 243 | | +--ro bits* identityref 244 | +--ro algorithm? uint8 245 | +--ro sid? uint32 246 +--ro unknown-tlvs 247 +--ro unknown-tlv* [] 248 +--ro type? uint16 249 +--ro length? uint16 250 +--ro value? yang:hex-string 251 augment /rt:routing/rt:control-plane-protocols 252 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 253 /ospf:interfaces/ospf:interface/ospf:database 254 /ospf:link-scope-lsa-type/ospf:link-scope-lsas 255 /ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 256 /ospf:body/ospfv3-e-lsa:e-link/ospfv3-e-lsa:e-link-tlvs 257 /ospfv3-e-lsa:intra-prefix-tlv: 258 +--ro perfix-sid-sub-tlvs 259 +--ro prefix-sid-sub-tlv* [] 260 +--ro ospfv3-prefix-sid-flags 261 | +--ro bits* identityref 262 +--ro algorithm? uint8 263 +--ro sid? uint32 264 augment /rt:routing/rt:control-plane-protocols 265 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 266 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 267 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 268 /ospf:body/ospfv3-e-lsa:e-intra-area-prefix 269 /ospfv3-e-lsa:e-intra-prefix-tlvs 270 /ospfv3-e-lsa:intra-prefix-tlv: 271 +--ro perfix-sid-sub-tlvs 272 +--ro prefix-sid-sub-tlv* [] 273 +--ro ospfv3-prefix-sid-flags 274 | +--ro bits* identityref 275 +--ro algorithm? uint8 276 +--ro sid? uint32 277 augment /rt:routing/rt:control-plane-protocols 278 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 279 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 280 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 281 /ospf:body/ospfv3-e-lsa:e-inter-area-prefix 282 /ospfv3-e-lsa:e-inter-prefix-tlvs 283 /ospfv3-e-lsa:inter-prefix-tlv: 284 +--ro perfix-sid-sub-tlvs 285 +--ro prefix-sid-sub-tlv* [] 286 +--ro ospfv3-prefix-sid-flags 287 | +--ro bits* identityref 288 +--ro algorithm? uint8 289 +--ro sid? uint32 290 augment /rt:routing/rt:control-plane-protocols 291 /rt:control-plane-protocol/ospf:ospf/ospf:database 292 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 293 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 294 /ospfv3-e-lsa:e-as-external/ospfv3-e-lsa:e-external-tlvs 295 /ospfv3-e-lsa:external-prefix-tlv: 296 +--ro perfix-sid-sub-tlvs 297 +--ro prefix-sid-sub-tlv* [] 298 +--ro ospfv3-prefix-sid-flags 299 | +--ro bits* identityref 300 +--ro algorithm? uint8 301 +--ro sid? uint32 302 augment /rt:routing/rt:control-plane-protocols 303 /rt:control-plane-protocol/ospf:ospf/ospf:database 304 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 305 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 306 /ospfv3-e-lsa:e-nssa/ospfv3-e-lsa:e-external-tlvs 307 /ospfv3-e-lsa:external-prefix-tlv: 308 +--ro perfix-sid-sub-tlvs 309 +--ro prefix-sid-sub-tlv* [] 310 +--ro ospfv3-prefix-sid-flags 311 | +--ro bits* identityref 312 +--ro algorithm? uint8 313 +--ro sid? uint32 314 augment /rt:routing/rt:control-plane-protocols 315 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 316 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 317 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 318 /ospf:body/ospfv3-e-lsa:e-router/ospfv3-e-lsa:e-router-tlvs 319 /ospfv3-e-lsa:link-tlv: 320 +--ro adj-sid-sub-tlvs 321 | +--ro adj-sid-sub-tlv* [] 322 | +--ro adj-sid-flags 323 | | +--ro bits* identityref 324 | +--ro weight? uint8 325 | +--ro sid? uint32 326 +--ro lan-adj-sid-sub-tlvs 327 +--ro lan-adj-sid-sub-tlv* [] 328 +--ro lan-adj-sid-flags 329 | +--ro bits* identityref 330 +--ro weight? uint8 331 +--ro neighbor-router-id? yang:dotted-quad 332 +--ro sid? uint32 334 file "ietf-ospfv3-sr@2021-10-18.yang" 335 module ietf-ospfv3-sr { 336 yang-version 1.1; 337 namespace "urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr"; 339 prefix ospfv3-sr; 341 import ietf-inet-types { 342 prefix "inet"; 343 } 345 import ietf-yang-types { 346 prefix "yang"; 347 } 349 import ietf-routing { 350 prefix "rt"; 351 } 353 import ietf-ospf { 354 prefix "ospf"; 355 } 357 import ietf-ospfv3-extended-lsa { 358 prefix "ospfv3-e-lsa"; 359 } 361 import ietf-ospf-sr { 362 prefix "ospf-sr"; 363 } 365 organization 366 "IETF LSR - Link State Routing Working Group"; 368 contact 369 "WG Web: 370 WG List: 372 Author: Yingzhen Qu 373 374 Author: Acee Lindem 375 "; 377 description 378 "This YANG module defines the operational state for OSPFv3 379 Segment Routing, which is common across all of the vendor 380 implementations. It is intended that the module will be 381 extended by vendors to define vendor-specific OSPFv3 382 Segment Routing configuration and operational parameters 383 and policies. 385 This YANG model conforms to the Network Management 386 Datastore Architecture (NMDA) as described in RFC 8342. 388 Copyright (c) 2021 IETF Trust and the persons identified as 389 authors of the code. All rights reserved. 391 Redistribution and use in source and binary forms, with or 392 without modification, is permitted pursuant to, and subject 393 to the license terms contained in, the Simplified BSD License 394 set forth in Section 4.c of the IETF Trust's Legal Provisions 395 Relating to IETF Documents 396 (http://trustee.ietf.org/license-info). 398 This version of this YANG module is part of RFC XXXX; 399 see the RFC itself for full legal notices. 401 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 402 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 403 'MAY', and 'OPTIONAL' in this document are to be interpreted as 404 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 405 they appear in all capitals, as shown here."; 407 reference "RFC XXXX"; 409 revision 2021-10-18 { 410 description 411 "Initial revision."; 412 reference 413 "RFC XXXX: A YANG Data Model for OSPFv3 Segment Routing."; 414 } 416 /* groupings */ 417 grouping ospfv3-prefix-sid-sub-tlvs { 418 description "Prefix Segment ID (SID) sub-TLVs."; 419 container perfix-sid-sub-tlvs{ 420 description "Prefix SID sub-TLV."; 421 list prefix-sid-sub-tlv { 422 description "Prefix SID sub-TLV."; 423 container ospfv3-prefix-sid-flags { 424 leaf-list bits { 425 type identityref { 426 base ospf-sr:prefix-sid-bit; 427 } 428 description 429 "Prefix SID Sub-TLV flag bits list."; 431 } 432 description "Segment Identifier (SID) Flags."; 433 } 434 leaf algorithm { 435 type uint8; 436 description 437 "The algorithm associated with the prefix-SID."; 438 } 439 leaf sid { 440 type uint32; 441 description "An index or label."; 442 } 443 } 444 } 445 } 447 grouping ospfv3-extended-prefix-range-tlvs { 448 description "Extended prefix range TLV grouping."; 450 container ospfv3-extended-prefix-range-tlvs { 451 description "The list of extended prefix range TLVs."; 452 list extended-prefix-range-tlv { 453 description "The range of prefixes."; 454 leaf prefix-length { 455 type uint8; 456 description "Length of prefix in bits."; 457 } 458 leaf af { 459 type uint8; 460 description "Address family for the prefix."; 461 } 462 leaf range-size { 463 type uint16; 464 description "The number of prefixes covered by the 465 advertisement."; 466 } 467 leaf prefix { 468 type inet:ip-prefix; 469 description "Address prefix."; 470 } 471 uses ospfv3-prefix-sid-sub-tlvs; 472 uses ospf:unknown-tlvs; 473 } 474 } 475 } 477 grouping ospfv3-adj-sid-sub-tlvs { 478 description "Adjacency SID sub TLV grouping."; 479 container adj-sid-sub-tlvs { 480 description "Adjacency SID optional sub-TLVs."; 481 list adj-sid-sub-tlv { 482 description "List of Adjacency SID sub-TLVs."; 483 container adj-sid-flags { 484 leaf-list bits { 485 type identityref { 486 base ospf-sr:adj-sid-bit; 487 } 488 description "Adj sid sub-tlv flags list."; 489 } 490 description "Adj-sid sub-tlv flags."; 491 } 492 leaf weight { 493 type uint8; 494 description "Weight used for load-balancing."; 495 } 496 leaf sid { 497 type uint32; 498 description "Segment Identifier (SID) index/label."; 499 } 500 } 501 } 502 } 504 grouping ospfv3-lan-adj-sid-sub-tlvs { 505 description "LAN adj-sid sub TLV grouping."; 506 container lan-adj-sid-sub-tlvs { 507 description "LAN Adjacency SID optional sub-TLVs."; 508 list lan-adj-sid-sub-tlv { 509 description "List of LAN adjacency SID sub-TLVs."; 510 container lan-adj-sid-flags { 511 leaf-list bits { 512 type identityref { 513 base ospf-sr:adj-sid-bit; 514 } 515 description "LAN adj sid sub-tlv flags list."; 516 } 517 description "LAN adj-sid sub-tlv flags."; 518 } 519 leaf weight { 520 type uint8; 521 description "Weight used for load-balancing."; 522 } 523 leaf neighbor-router-id { 524 type yang:dotted-quad; 525 description "Neighbor router ID."; 526 } 527 leaf sid { 528 type uint32; 529 description "Segment Identifier (SID) index/label."; 530 } 531 } 532 } 533 } 535 /* Database */ 536 /* Segment Routing Capabilities */ 537 augment "/rt:routing/" 538 + "rt:control-plane-protocols/rt:control-plane-protocol/" 539 + "ospf:ospf/ospf:database/" 540 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 541 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 542 + "ospf:ospfv3/ospf:body/ospf:router-information" { 543 when "../../../../../../../../" 544 + "rt:type = 'ospf:ospfv3'" { 545 description 546 "This augmentation is only valid for OSPFv3."; 547 } 548 description 549 "SR specific TLVs for OSPFv3 Router Information 550 opaque LSA."; 551 uses ospf-sr:sr-algorithm-tlv; 552 uses ospf-sr:sid-range-tlvs; 553 uses ospf-sr:local-block-tlvs; 554 uses ospf-sr:srms-preference-tlv; 555 } 557 augment "/rt:routing/" 558 + "rt:control-plane-protocols/rt:control-plane-protocol/" 559 + "ospf:ospf/ospf:areas/" 560 + "ospf:area/ospf:database/" 561 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 562 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 563 + "ospf:ospfv3/ospf:body/ospf:router-information" { 564 when "../../../../../../../../../../" 565 + "rt:type = 'ospf:ospfv3'" { 566 description 567 "This augmentation is only valid for OSPFv3."; 568 } 570 description 571 "SR specific TLVs for OSPFv3 Router Information LSA."; 573 uses ospf-sr:sr-algorithm-tlv; 574 uses ospf-sr:sid-range-tlvs; 575 uses ospf-sr:local-block-tlvs; 576 uses ospf-sr:srms-preference-tlv; 577 } 579 augment "/rt:routing/" 580 + "rt:control-plane-protocols/rt:control-plane-protocol/" 581 + "ospf:ospf/ospf:areas/ospf:area/" 582 + "ospf:interfaces/ospf:interface/ospf:database/" 583 + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" 584 + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/" 585 + "ospf:ospfv3/ospf:body/ospf:router-information" { 586 when "../../../../../../../../../../../../" 587 + "rt:type = 'ospf:ospfv3'" { 588 description 589 "This augmentation is only valid for OSPFv3."; 590 } 592 description 593 "SR specific TLVs for OSPFv3 Router Information LSA."; 595 uses ospf-sr:sr-algorithm-tlv; 596 uses ospf-sr:sid-range-tlvs; 597 uses ospf-sr:local-block-tlvs; 598 uses ospf-sr:srms-preference-tlv; 599 } 601 /* OSPFv3 Extended Prefix Range TLV */ 602 augment "/rt:routing/" 603 + "rt:control-plane-protocols/rt:control-plane-protocol/" 604 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 605 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 606 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 607 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-intra-area-prefix" { 608 when "../../../../../../../../../../" 609 + "rt:type = 'ospf:ospfv3'" { 610 description 611 "This augmentation is only valid for OSPFv3 612 E-Router LSAs"; 613 } 614 uses ospfv3-extended-prefix-range-tlvs; 615 description 616 "OSPFv3 Area-Scoped E-Intra-Area-Prefix LSA."; 617 } 619 augment "/rt:routing/" 620 + "rt:control-plane-protocols/rt:control-plane-protocol/" 621 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 622 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 623 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 624 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-inter-area-prefix" { 625 when "../../../../../../../../../../" 626 + "rt:type = 'ospf:ospfv3'" { 627 description 628 "This augmentation is only valid for OSPFv3 629 E-Router LSAs"; 630 } 631 uses ospfv3-extended-prefix-range-tlvs; 632 description 633 "OSPFv3 Area-Scoped E-Inter-Area-Prefix LSA."; 634 } 636 augment "/rt:routing/" 637 + "rt:control-plane-protocols/rt:control-plane-protocol/" 638 + "ospf:ospf/ospf:database/" 639 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 640 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 641 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-as-external" { 642 when "'ospf:../../../../../../../../../" 643 + "rt:type' = 'ospf:ospfv3'" { 644 description 645 "This augmentation is only valid for OSPFv3."; 646 } 647 uses ospfv3-extended-prefix-range-tlvs; 648 description 649 "OSPFv3 AS-Scoped E-AS-External LSA."; 650 } 652 augment "/rt:routing/" 653 + "rt:control-plane-protocols/rt:control-plane-protocol/" 654 + "ospf:ospf/ospf:database/" 655 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 656 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 657 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-nssa" { 658 when "'ospf:../../../../../../../../../" 659 + "rt:type' = 'ospf:ospfv3'" { 660 description 661 "This augmentation is only valid for OSPFv3."; 662 } 663 uses ospfv3-extended-prefix-range-tlvs; 664 description 665 "OSPFv3 AS-Scoped E-NSSA LSA."; 666 } 668 /* Prefix SID Sub-TLV in Intra-Area Prefix TLV */ 669 augment "/rt:routing/" 670 + "rt:control-plane-protocols/rt:control-plane-protocol/" 671 + "ospf:ospf/ospf:areas/ospf:area/ospf:interfaces/" 672 + "ospf:interface/" 673 + "ospf:database/ospf:link-scope-lsa-type/ospf:link-scope-lsas/" 674 + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3/" 675 + "ospf:body/ospfv3-e-lsa:e-link/" 676 + "ospfv3-e-lsa:e-link-tlvs/ospfv3-e-lsa:intra-prefix-tlv" { 677 when "../../../../../../../../../../../../../../" 678 + "rt:type = 'ospf:ospfv3'" { 679 description 680 "This augmentation is only valid for OSPFv3 681 E-Router LSAs"; 682 } 683 uses ospfv3-prefix-sid-sub-tlvs; 684 description 685 "OSPFv3 Link-Scoped Intra-Area Prefix TLV."; 686 } 688 augment "/rt:routing/" 689 + "rt:control-plane-protocols/rt:control-plane-protocol/" 690 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 691 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 692 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 693 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-intra-area-prefix/" 694 + "ospfv3-e-lsa:e-intra-prefix-tlvs/" 695 + "ospfv3-e-lsa:intra-prefix-tlv" { 696 when "../../../../../../../../../../../../" 697 + "rt:type = 'ospf:ospfv3'" { 698 description 699 "This augmentation is only valid for OSPFv3 700 E-Router LSAs"; 701 } 702 uses ospfv3-prefix-sid-sub-tlvs; 703 description 704 "OSPFv3 Area-Scoped Intra-Area Prefix TLV."; 705 } 707 /* Prefix SID Sub-TLV in Inter-Area Prefix TLV */ 708 augment "/rt:routing/" 709 + "rt:control-plane-protocols/rt:control-plane-protocol/" 710 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 711 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 712 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 713 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-inter-area-prefix/" 714 + "ospfv3-e-lsa:e-inter-prefix-tlvs/" 715 + "ospfv3-e-lsa:inter-prefix-tlv" { 716 when "../../../../../../../../../../../../" 717 + "rt:type = 'ospf:ospfv3'" { 718 description 719 "This augmentation is only valid for OSPFv3 720 E-Router LSAs"; 721 } 722 uses ospfv3-prefix-sid-sub-tlvs; 723 description 724 "OSPFv3 Area-Scoped Inter-Area Prefix TLV."; 725 } 727 /* Prefix SID Sub-TLV in External Prefix TLV */ 728 augment "/rt:routing/" 729 + "rt:control-plane-protocols/rt:control-plane-protocol/" 730 + "ospf:ospf/ospf:database/" 731 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 732 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 733 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-as-external/" 734 + "ospfv3-e-lsa:e-external-tlvs/" 735 + "ospfv3-e-lsa:external-prefix-tlv" { 736 when "'ospf:../../../../../../../../../" 737 + "rt:type' = 'ospf:ospfv3'" { 738 description 739 "This augmentation is only valid for OSPFv3."; 740 } 741 uses ospfv3-prefix-sid-sub-tlvs; 742 description 743 "OSPFv3 AS-Scoped External Prefix TLV."; 744 } 746 augment "/rt:routing/" 747 + "rt:control-plane-protocols/rt:control-plane-protocol/" 748 + "ospf:ospf/ospf:database/" 749 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 750 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 751 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-nssa/" 752 + "ospfv3-e-lsa:e-external-tlvs/" 753 + "ospfv3-e-lsa:external-prefix-tlv" { 754 when "'ospf:../../../../../../../../../" 755 + "rt:type' = 'ospf:ospfv3'" { 756 description 757 "This augmentation is only valid for OSPFv3."; 758 } 759 uses ospfv3-prefix-sid-sub-tlvs; 760 description 761 "OSPFv3 AS-Scoped External Prefix TLV."; 762 } 764 /* Adj-SID sub-TLV */ 765 augment "/rt:routing/" 766 + "rt:control-plane-protocols/rt:control-plane-protocol/" 767 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 768 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 769 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 770 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" 771 + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 772 when "../../../../../../../../../../../../" 773 + "rt:type = 'ospf:ospfv3'" { 774 description 775 "This augmentation is only valid for OSPFv3 776 E-Router LSAs"; 777 } 778 uses ospfv3-adj-sid-sub-tlvs; 779 uses ospfv3-lan-adj-sid-sub-tlvs; 780 description 781 "OSPFv3 Area-Scoped Adj-SID Sub-TLV."; 782 } 783 } 784 786 4. Security Considerations 788 The YANG modules specified in this document define a schema for data 789 that is designed to be accessed via network management protocols such 790 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 791 is the secure transport layer, and the mandatory-to-implement secure 792 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 793 is HTTPS, and the mandatory-to-implement secure transport is TLS 794 [RFC8446]. 796 The Network Configuration Access Control Model (NACM) [[RFC8341] 797 provides the means to restrict access for particular NETCONF or 798 RESTCONF users to a pre-configured subset of all available NETCONF or 799 RESTCONF protocol operations and content. 801 There are a number of data nodes defined in the modules that are 802 writable/creatable/deletable (i.e., config true, which is the 803 default). These data nodes may be considered sensitive or vulnerable 804 in some network environments. Write operations (e.g., edit-config) 805 to these data nodes without proper protection can have a negative 806 effect on network operations. 808 Some of the readable data nodes in the modules may be considered 809 sensitive or vulnerable in some network environments. It is thus 810 important to control read access (e.g., via get, get-config, or 811 notification) to these data nodes. The exposure of the Link State 812 Database (LSDB) will expose the detailed topology of the network. 813 This may be undesirable since both due to the fact that exposure may 814 facilitate other attacks. Additionally, network operators may 815 consider their topologies to be sensitive confidential data. 817 5. IANA Considerations 819 This document registers URIs in the IETF XML registry [RFC3688]. 820 Following the format in [RFC3688], the following registrations is 821 requested to be made: 823 URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr 824 Registrant Contact: The IESG. 825 XML: N/A, the requested URI is an XML namespace. 827 This document registers the YANG modules in the YANG Module Names 828 registry [RFC6020]. 830 name: ietf-ospfv3-sr 831 namespace: urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr 832 prefix: ospfv3-sr 833 reference: RFC XXXX 835 6. Acknowledgements 837 This document was produced using Marshall Rose's xml2rfc tool. 839 The YANG model was developed using the suite of YANG tools written 840 and maintained by numerous authors. 842 7. References 844 7.1. Normative References 846 [I-D.ietf-ospf-sr-yang] 847 Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem, 848 "YANG Data Model for OSPF Segment Routing", Work in 849 Progress, Internet-Draft, draft-ietf-ospf-sr-yang-17, 2 850 January 2022, . 853 [I-D.ietf-ospf-yang] 854 Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem, 855 "YANG Data Model for OSPF Protocol", Work in Progress, 856 Internet-Draft, draft-ietf-ospf-yang-29, 17 October 2019, 857 . 860 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 861 Requirement Levels", BCP 14, RFC 2119, 862 DOI 10.17487/RFC2119, March 1997, 863 . 865 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 866 DOI 10.17487/RFC3688, January 2004, 867 . 869 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 870 the Network Configuration Protocol (NETCONF)", RFC 6020, 871 DOI 10.17487/RFC6020, October 2010, 872 . 874 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 875 and A. Bierman, Ed., "Network Configuration Protocol 876 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 877 . 879 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 880 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 881 . 883 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 884 RFC 7950, DOI 10.17487/RFC7950, August 2016, 885 . 887 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 888 Management", RFC 8022, DOI 10.17487/RFC8022, November 889 2016, . 891 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 892 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 893 . 895 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 896 Access Control Model", STD 91, RFC 8341, 897 DOI 10.17487/RFC8341, March 2018, 898 . 900 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 901 Routing Management (NMDA Version)", RFC 8349, 902 DOI 10.17487/RFC8349, March 2018, 903 . 905 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 906 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 907 . 909 [RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions 910 for Segment Routing", RFC 8666, DOI 10.17487/RFC8666, 911 December 2019, . 913 7.2. Informative References 915 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 916 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 917 . 919 Authors' Addresses 921 Acee Lindem 922 Cisco Systems 923 301 Midenhall Way 924 Cary, NC 27513 925 Email: acee@cisco.com 927 Yingzhen Qu 928 Futurewei 929 2330 Central Expressway 930 Santa Clara, CA 95050 931 United States of America 932 Email: yingzhen.qu@futurewei.com