idnits 2.17.1 draft-acee-lsr-ospfv3-sr-yang-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 29, 2021) is 1086 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-30) exists of draft-ietf-ospf-sr-yang-14 ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349) Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet A. Lindem 3 Internet-Draft Cisco Systems 4 Intended status: Informational Y. Qu 5 Expires: October 31, 2021 Futurewei 6 April 29, 2021 8 YANG Data Model for OSPFv3 Segment Routing 9 draft-acee-lsr-ospfv3-sr-yang-04 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 October 31, 2021. 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 . . . . . . . . . . . . 2 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 17 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 58 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 59 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 60 7.1. Normative References . . . . . . . . . . . . . . . . . . 18 61 7.2. Informative References . . . . . . . . . . . . . . . . . 19 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 64 1. Overview 66 YANG [RFC6020] [RFC7950] is a data definition language used to define 67 the contents of a conceptual data store that allows networked devices 68 to be managed using NETCONF [RFC6241]. YANG is proving relevant 69 beyond its initial confines, as bindings to other interfaces (e.g., 70 ReST) 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 [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 This document uses the graphical representation of data models 91 defined in [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. [RFC8022] and [RFC8349] are not referenced in the document 98 text but within the YANG module itself. 100 module: ietf-ospfv3-sr 101 augment /rt:routing/rt:control-plane-protocols 102 /rt:control-plane-protocol/ospf:ospf/ospf:database 103 /ospf:as-scope-lsa-type/ospf:as-scope-lsas/ospf:as-scope-lsa 104 /ospf:version/ospf:ospfv3/ospf:ospfv3/ospf:body 105 /ospf:router-information: 106 +--ro sr-algorithm-tlv 107 | +--ro sr-algorithm* uint8 108 +--ro sid-range-tlvs 109 | +--ro sid-range-tlv* [] 110 | +--ro range-size? uint24 111 | +--ro sid-sub-tlv 112 | +--ro sid? uint32 113 +--ro local-block-tlvs 114 | +--ro local-block-tlv* [] 115 | +--ro range-size? uint24 116 | +--ro sid-sub-tlv 117 | +--ro sid? uint32 118 +--ro srms-preference-tlv 119 +--ro preference? uint8 120 augment /rt:routing/rt:control-plane-protocols 121 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 122 /ospf:database/ospf:area-scope-lsa-type/ospf:area-scope-lsas 123 /ospf:area-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 124 /ospf:body/ospf:router-information: 125 +--ro sr-algorithm-tlv 126 | +--ro sr-algorithm* uint8 127 +--ro sid-range-tlvs 128 | +--ro sid-range-tlv* [] 129 | +--ro range-size? uint24 130 | +--ro sid-sub-tlv 131 | +--ro sid? uint32 132 +--ro local-block-tlvs 133 | +--ro local-block-tlv* [] 134 | +--ro range-size? uint24 135 | +--ro sid-sub-tlv 136 | +--ro sid? uint32 137 +--ro srms-preference-tlv 138 +--ro preference? uint8 139 augment /rt:routing/rt:control-plane-protocols 140 /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area 141 /ospf:interfaces/ospf:interface/ospf:database 142 /ospf:link-scope-lsa-type/ospf:link-scope-lsas 143 /ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3 144 /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-04-29.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; 337 import ietf-inet-types { 338 prefix "inet"; 339 } 341 import ietf-yang-types { 342 prefix "yang"; 343 } 345 import ietf-routing { 346 prefix "rt"; 347 } 349 import ietf-ospf { 350 prefix "ospf"; 351 } 353 import ietf-ospfv3-extended-lsa { 354 prefix "ospfv3-e-lsa"; 355 } 357 import ietf-ospf-sr { 358 prefix "ospf-sr"; 359 } 361 organization 362 "IETF LSR - Link State Routing Working Group"; 364 contact 365 "WG Web: 366 WG List: 368 Author: Yingzhen Qu 369 370 Author: Acee Lindem 371 "; 373 description 374 "This YANG module defines the operational state for OSPFv3 375 Segment Routing, which is common across all of the vendor 376 implementations. It is intended that the module will be 377 extended by vendors to define vendor-specific OSPFv3 378 Segment Routing configuration and operational parameters 379 and policies. 381 This YANG model conforms to the Network Management 382 Datastore Architecture (NMDA) as described in RFC 8242. 384 Copyright (c) 2020 IETF Trust and the persons identified as 385 authors of the code. All rights reserved. 387 Redistribution and use in source and binary forms, with or 388 without modification, is permitted pursuant to, and subject 389 to the license terms contained in, the Simplified BSD License 390 set forth in Section 4.c of the IETF Trust's Legal Provisions 391 Relating to IETF Documents 392 (http://trustee.ietf.org/license-info). 394 This version of this YANG module is part of RFC XXXX; 395 see the RFC itself for full legal notices. 397 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL 398 NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 399 'MAY', and 'OPTIONAL' in this document are to be interpreted as 400 described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, 401 they appear in all capitals, as shown here."; 403 reference "RFC XXXX"; 405 revision 2021-04-29 { 406 description 407 "Initial revision."; 408 reference 409 "RFC XXXX: A YANG Data Model for OSPFv3 Segment Routing."; 410 } 412 /* groupings */ 413 grouping ospfv3-prefix-sid-sub-tlvs { 414 description "Prefix Segment ID (SID) sub-TLVs."; 415 container perfix-sid-sub-tlvs{ 416 description "Prefix SID sub-TLV."; 417 list prefix-sid-sub-tlv { 418 description "Prefix SID sub-TLV."; 419 container ospfv3-prefix-sid-flags { 420 leaf-list bits { 421 type identityref { 422 base ospf-sr:prefix-sid-bit; 423 } 424 description 425 "Prefix SID Sub-TLV flag bits list."; 426 } 427 description "Segment Identifier (SID) Flags."; 428 } 429 leaf algorithm { 430 type uint8; 431 description 432 "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 range of prefixes."; 448 list extended-prefix-range-tlv { //type=2? 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."; 526 } 527 } 528 } 529 } 530 /* Database */ 531 /* Segment Routing Capabilities */ 532 augment "/rt:routing/" 533 + "rt:control-plane-protocols/rt:control-plane-protocol/" 534 + "ospf:ospf/ospf:database/" 535 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 536 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 537 + "ospf:ospfv3/ospf:body/ospf:router-information" { 538 when "../../../../../../../../" 539 + "rt:type = 'ospf:ospfv3'" { 540 description 541 "This augmentation is only valid for OSPFv3."; 542 } 543 description 544 "SR specific TLVs for OSPFv3 Router Information 545 opaque LSA."; 546 uses ospf-sr:sr-algorithm-tlv; 547 uses ospf-sr:sid-range-tlvs; 548 uses ospf-sr:local-block-tlvs; 549 uses ospf-sr:srms-preference-tlv; 550 } 552 augment "/rt:routing/" 553 + "rt:control-plane-protocols/rt:control-plane-protocol/" 554 + "ospf:ospf/ospf:areas/" 555 + "ospf:area/ospf:database/" 556 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 557 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 558 + "ospf:ospfv3/ospf:body/ospf:router-information" { 559 when "../../../../../../../../../../" 560 + "rt:type = 'ospf:ospfv3'" { 561 description 562 "This augmentation is only valid for OSPFv3."; 563 } 565 description 566 "SR specific TLVs for OSPFv3 Router Information LSA."; 568 uses ospf-sr:sr-algorithm-tlv; 569 uses ospf-sr:sid-range-tlvs; 570 uses ospf-sr:local-block-tlvs; 571 uses ospf-sr:srms-preference-tlv; 572 } 574 augment "/rt:routing/" 575 + "rt:control-plane-protocols/rt:control-plane-protocol/" 576 + "ospf:ospf/ospf:areas/ospf:area/" 577 + "ospf:interfaces/ospf:interface/ospf:database/" 578 + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" 579 + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/" 580 + "ospf:ospfv3/ospf:body/ospf:router-information" { 581 when "../../../../../../../../../../../../" 582 + "rt:type = 'ospf:ospfv3'" { 583 description 584 "This augmentation is only valid for OSPFv3."; 585 } 587 description 588 "SR specific TLVs for OSPFv3 Router Information LSA."; 590 uses ospf-sr:sr-algorithm-tlv; 591 uses ospf-sr:sid-range-tlvs; 592 uses ospf-sr:local-block-tlvs; 593 uses ospf-sr:srms-preference-tlv; 594 } 596 /* OSPFv3 Extended Prefix Range TLV */ 597 augment "/rt:routing/" 598 + "rt:control-plane-protocols/rt:control-plane-protocol/" 599 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 600 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 601 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 602 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-intra-area-prefix" { 603 when "../../../../../../../../../../" 604 + "rt:type = 'ospf:ospfv3'" { 605 description 606 "This augmentation is only valid for OSPFv3 607 E-Router LSAs"; 608 } 609 uses ospfv3-extended-prefix-range-tlvs; 610 description 611 "OSPFv3 Area-Scoped E-Intra-Area-Prefix LSA."; 612 } 614 augment "/rt:routing/" 615 + "rt:control-plane-protocols/rt:control-plane-protocol/" 616 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 617 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 618 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 619 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-inter-area-prefix" { 620 when "../../../../../../../../../../" 621 + "rt:type = 'ospf:ospfv3'" { 622 description 623 "This augmentation is only valid for OSPFv3 624 E-Router LSAs"; 625 } 626 uses ospfv3-extended-prefix-range-tlvs; 627 description 628 "OSPFv3 Area-Scoped E-Inter-Area-Prefix LSA."; 629 } 631 augment "/rt:routing/" 632 + "rt:control-plane-protocols/rt:control-plane-protocol/" 633 + "ospf:ospf/ospf:database/" 634 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 635 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 636 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-as-external" { 637 when "'ospf:../../../../../../../../../" 638 + "rt:type' = 'ospf:ospfv3'" { 639 description 640 "This augmentation is only valid for OSPFv3."; 641 } 642 uses ospfv3-extended-prefix-range-tlvs; 643 description 644 "OSPFv3 AS-Scoped E-AS-External LSA."; 645 } 647 augment "/rt:routing/" 648 + "rt:control-plane-protocols/rt:control-plane-protocol/" 649 + "ospf:ospf/ospf:database/" 650 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 651 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 652 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-nssa" { 653 when "'ospf:../../../../../../../../../" 654 + "rt:type' = 'ospf:ospfv3'" { 655 description 656 "This augmentation is only valid for OSPFv3."; 657 } 658 uses ospfv3-extended-prefix-range-tlvs; 659 description 660 "OSPFv3 AS-Scoped E-NSSA LSA."; 661 } 663 /* Prefix SID Sub-TLV in Intra-Area Prefix TLV */ 664 augment "/rt:routing/" 665 + "rt:control-plane-protocols/rt:control-plane-protocol/" 666 + "ospf:ospf/ospf:areas/ospf:area/ospf:interfaces/" 667 + "ospf:interface/" 668 + "ospf:database/ospf:link-scope-lsa-type/ospf:link-scope-lsas/" 669 + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/ospf:ospfv3/" 670 + "ospf:body/ospfv3-e-lsa:e-link/" 671 + "ospfv3-e-lsa:e-link-tlvs/ospfv3-e-lsa:intra-prefix-tlv" { 672 when "../../../../../../../../../../../../../../" 673 + "rt:type = 'ospf:ospfv3'" { 674 description 675 "This augmentation is only valid for OSPFv3 676 E-Router LSAs"; 677 } 678 uses ospfv3-prefix-sid-sub-tlvs; 679 description 680 "OSPFv3 Link-Scoped Intra-Area Prefix TLV."; 681 } 683 augment "/rt:routing/" 684 + "rt:control-plane-protocols/rt:control-plane-protocol/" 685 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 686 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 687 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 688 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-intra-area-prefix/" 689 + "ospfv3-e-lsa:e-intra-prefix-tlvs/" 690 + "ospfv3-e-lsa:intra-prefix-tlv" { 691 when "../../../../../../../../../../../../" 692 + "rt:type = 'ospf:ospfv3'" { 693 description 694 "This augmentation is only valid for OSPFv3 695 E-Router LSAs"; 696 } 697 uses ospfv3-prefix-sid-sub-tlvs; 698 description 699 "OSPFv3 Area-Scoped Intra-Area Prefix TLV."; 700 } 702 /* Prefix SID Sub-TLV in Inter-Area Prefix TLV */ 703 augment "/rt:routing/" 704 + "rt:control-plane-protocols/rt:control-plane-protocol/" 705 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 706 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 707 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 708 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-inter-area-prefix/" 709 + "ospfv3-e-lsa:e-inter-prefix-tlvs/" 710 + "ospfv3-e-lsa:inter-prefix-tlv" { 711 when "../../../../../../../../../../../../" 712 + "rt:type = 'ospf:ospfv3'" { 713 description 714 "This augmentation is only valid for OSPFv3 715 E-Router LSAs"; 716 } 717 uses ospfv3-prefix-sid-sub-tlvs; 718 description 719 "OSPFv3 Area-Scoped Inter-Area Prefix TLV."; 720 } 721 /* Prefix SID Sub-TLV in External Prefix TLV */ 722 augment "/rt:routing/" 723 + "rt:control-plane-protocols/rt:control-plane-protocol/" 724 + "ospf:ospf/ospf:database/" 725 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 726 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 727 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-as-external/" 728 + "ospfv3-e-lsa:e-external-tlvs/" 729 + "ospfv3-e-lsa:external-prefix-tlv" { 730 when "'ospf:../../../../../../../../../" 731 + "rt:type' = 'ospf:ospfv3'" { 732 description 733 "This augmentation is only valid for OSPFv3."; 734 } 735 uses ospfv3-prefix-sid-sub-tlvs; 736 description 737 "OSPFv3 AS-Scoped External Prefix TLV."; 738 } 740 augment "/rt:routing/" 741 + "rt:control-plane-protocols/rt:control-plane-protocol/" 742 + "ospf:ospf/ospf:database/" 743 + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" 744 + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" 745 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-nssa/" 746 + "ospfv3-e-lsa:e-external-tlvs/" 747 + "ospfv3-e-lsa:external-prefix-tlv" { 748 when "'ospf:../../../../../../../../../" 749 + "rt:type' = 'ospf:ospfv3'" { 750 description 751 "This augmentation is only valid for OSPFv3."; 752 } 753 uses ospfv3-prefix-sid-sub-tlvs; 754 description 755 "OSPFv3 AS-Scoped External Prefix TLV."; 756 } 758 /* Adj-SID sub-TLV */ 759 augment "/rt:routing/" 760 + "rt:control-plane-protocols/rt:control-plane-protocol/" 761 + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" 762 + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" 763 + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" 764 + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" 765 + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { 766 when "../../../../../../../../../../../../" 767 + "rt:type = 'ospf:ospfv3'" { 768 description 769 "This augmentation is only valid for OSPFv3 770 E-Router LSAs"; 771 } 772 uses ospfv3-adj-sid-sub-tlvs; 773 uses ospfv3-lan-adj-sid-sub-tlvs; 774 description 775 "OSPFv3 Area-Scoped Adj-SID Sub-TLV."; 776 } 777 } 778 780 4. Security Considerations 782 The YANG modules specified in this document define a schema for data 783 that is designed to be accessed via network management protocols such 784 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 785 is the secure transport layer, and the mandatory-to-implement secure 786 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 787 is HTTPS, and the mandatory-to-implement secure transport is TLS 788 [RFC5246]. 790 The NETCONF access control model [RFC6536] provides the means to 791 restrict access for particular NETCONF or RESTCONF users to a pre- 792 configured subset of all available NETCONF or RESTCONF protocol 793 operations and content. 795 There are a number of data nodes defined in the modules that are 796 writable/creatable/deletable (i.e., config true, which is the 797 default). These data nodes may be considered sensitive or vulnerable 798 in some network environments. Write operations (e.g., edit-config) 799 to these data nodes without proper protection can have a negative 800 effect on network operations. 802 Some of the readable data nodes in the modules may be considered 803 sensitive or vulnerable in some network environments. It is thus 804 important to control read access (e.g., via get, get-config, or 805 notification) to these data nodes. The exposure of the Link State 806 Database (LSDB) will expose the detailed topology of the network. 807 This may be undesirable since both due to the fact that exposure may 808 facilitate other attacks. Additionally, network operators may 809 consider their topologies to be sensitive confidential data. 811 5. IANA Considerations 813 This document registers URIs in the IETF XML registry [RFC3688]. 814 Following the format in [RFC3688], the following registrations is 815 requested to be made: 817 URI: urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr 818 Registrant Contact: The IESG. 819 XML: N/A, the requested URI is an XML namespace. 821 This document registers the YANG modules in the YANG Module Names 822 registry [RFC6020]. 824 name: ietf-ospfv3-sr 825 namespace: urn:ietf:params:xml:ns:yang:ietf-ospfv3-sr 826 prefix: ospfv3-sr 827 reference: RFC XXXX 829 6. Acknowledgements 831 This document was produced using Marshall Rose's xml2rfc tool. 833 The YANG model was developed using the suite of YANG tools written 834 and maintained by numerous authors. 836 7. References 838 7.1. Normative References 840 [I-D.ietf-ospf-sr-yang] 841 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 842 "YANG Data Model for OSPF SR (Segment Routing) Protocol", 843 draft-ietf-ospf-sr-yang-14 (work in progress), February 844 2021. 846 [I-D.ietf-ospf-yang] 847 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 848 "YANG Data Model for OSPF Protocol", draft-ietf-ospf- 849 yang-29 (work in progress), October 2019. 851 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 852 Requirement Levels", BCP 14, RFC 2119, 853 DOI 10.17487/RFC2119, March 1997, 854 . 856 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 857 DOI 10.17487/RFC3688, January 2004, 858 . 860 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 861 (TLS) Protocol Version 1.2", RFC 5246, 862 DOI 10.17487/RFC5246, August 2008, 863 . 865 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 866 the Network Configuration Protocol (NETCONF)", RFC 6020, 867 DOI 10.17487/RFC6020, October 2010, 868 . 870 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 871 and A. Bierman, Ed., "Network Configuration Protocol 872 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 873 . 875 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 876 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 877 . 879 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 880 Protocol (NETCONF) Access Control Model", RFC 6536, 881 DOI 10.17487/RFC6536, March 2012, 882 . 884 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 885 RFC 7950, DOI 10.17487/RFC7950, August 2016, 886 . 888 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 889 Management", RFC 8022, DOI 10.17487/RFC8022, November 890 2016, . 892 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 893 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 894 . 896 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 897 Routing Management (NMDA Version)", RFC 8349, 898 DOI 10.17487/RFC8349, March 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