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