idnits 2.17.00 (12 Aug 2021) /tmp/idnits53930/draft-raza-bess-srv6-services-yang-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 50 instances of too long lines in the document, the longest one being 72 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 194 has weird spacing: '...path-id uin...' == Line 197 has weird spacing: '...ved-sid srv...' == Line 199 has weird spacing: '...cal-sid srv...' == Line 207 has weird spacing: '...path-id uin...' == Line 210 has weird spacing: '...ved-sid srv...' == (7 more instances...) -- The document date (July 13, 2020) is 670 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) == Outdated reference: A later version (-13) exists of draft-ietf-idr-bgp-model-09 == Outdated reference: A later version (-06) exists of draft-raza-spring-srv6-yang-05 == Outdated reference: draft-ietf-spring-srv6-network-programming has been published as RFC 8986 Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 BESS Working Group K. Raza 2 Internet-Draft Cisco Systems 3 Intended status: Standards Track 4 Expires: January 14, 2021 B. Decraene 5 Orange 7 Z. Jiang 8 Alibaba 10 S. Matsushima 11 Softbank 13 K. Majumdar 14 Ruckus Networks 16 July 13, 2020 18 Yang Data Model for SRv6 based Services 19 draft-raza-bess-srv6-services-yang-01 21 Abstract 23 This document defines a YANG data model that can be used to configure 24 and manage SRv6 based services in BGP. 26 The YANG module in this document conforms to the Network Management 27 Datastore Architecture (NMDA). 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on January 14, 2021. 46 Copyright Notice 48 Copyright (c) 2020 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Specification of Requirements . . . . . . . . . . . . . . . . 3 65 3. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 3 66 4. Configuration and State . . . . . . . . . . . . . . . . . . . 3 67 4.1. Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 5. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 6 69 6. Executables (Actions) . . . . . . . . . . . . . . . . . . . . 6 70 7. Yang Module . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 72 9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 73 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 74 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 75 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 76 12.1. Normative References . . . . . . . . . . . . . . . . . . 15 77 12.2. Informative References . . . . . . . . . . . . . . . . . 16 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 80 1. Introduction 82 YANG [RFC6020] [RFC7950] is a data definition language that was 83 introduced to define the contents of a conceptual data store that 84 allows network devices to be managed using NETCONF [RFC6241]. 86 Segment Routing (SR), as defined in [RFC8402], is source routing 87 paradigm where a node steers a packet through an ordered list of 88 instructions, called segments. A segment is idenfied using its SID 89 (Segment Identifier) and may represent a topological path, a service 90 endpoint, a virtual network function, etc. The IPv6 dataplane 91 instantiation of SR is called SRv6 as specified in 92 [I-D.ietf-spring-srv6-network-programming] 94 BGP overlay service endpoints can be identified using SRv6 service 95 SIDs. These services include L3VPN, EVPN, and Internet services. 96 The procedures and messages for BGP overlay services using SRv6 SID 97 are specified in [I-D.dawra-bess-srv6-services] 99 This document defines the YANG model for managing these SRv6 based 100 services in BGP. 102 2. Specification of Requirements 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 106 "OPTIONAL" in this document are to be interpreted as described in BCP 107 14 [RFC2119] [RFC8174] when, and only when, they appear in all 108 capitals, as shown here. 110 3. Model Overview 112 The modeling in this document complies with the Network Management 113 Datastore Architecture (NMDA) [RFC8342]. The operational state data 114 is combined with the associated configuration data in the same 115 hierarchy [RFC8407]. When protocol states are retrieved from the 116 NMDA operational state datastore, the returned states cover all 117 "config true" (rw) and "config false" (ro) nodes defined in the 118 schema. 120 The scope of data modeling is for the following management 121 constructs: 123 o Configuration 125 o Operational State 127 o Notifications 129 o Executables (Actions) 131 The Yang extensions proposed in this model augment the base BGP model 132 defined in [I-D.ietf-idr-bgp-model]. The common data types for SRv6 133 are imported from [I-D.raza-spring-srv6-yang]. 135 TBD: The base BGP model [I-D.ietf-idr-bgp-model] in its current form 136 is not scoped within the context of a Network Instance. Therefore, 137 the context of a VRF is not fully realized. The extensions done in 138 this model should fall within the scope of a VRF, once the top BGP 139 container is linked under Network Instance. 141 4. Configuration and State 143 Current revision of this document defines the following areas: 145 o Configuration: Enable Segment-routing SRv6 based service 147 o Configuration: Designate SRv6 locator for SID allocation 149 o Configuration: Specify SID allocation mode (per-vrf, per-ce) 150 o State: Info related to Remote SRv6 SID learnt in a service route 152 The BGP service here refers to overlay for global (Internet) as well 153 L3VPN service for IPv4 and IPv6. 155 [Ed Note: TODO EVPN] 157 4.1. Tree 159 module: ietf-bgp-srv6-services 160 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global: 161 +--rw segment-routing 162 +--rw srv6 163 +--rw locator? -> /rt:routing/srv6:srv6/locators/locator/name 165 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast: 166 +--rw segment-routing 167 +--rw srv6 168 +--rw locator? -> /rt:routing/srv6:srv6/locators/locator/name 169 +--rw sid-alloc-mode? enumeration 171 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast: 172 +--rw segment-routing 173 +--rw srv6 174 +--rw locator? -> /rt:routing/srv6:srv6/locators/locator/name 175 +--rw sid-alloc-mode? enumeration 177 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv4-unicast: 178 +--rw segment-routing 179 +--rw srv6 180 +--rw locator? -> /rt:routing/srv6:srv6/locators/locator/name 181 +--rw sid-alloc-mode? enumeration 183 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv6-unicast: 184 +--rw segment-routing 185 +--rw srv6 186 +--rw locator? -> /rt:routing/srv6:srv6/locators/locator/name 187 +--rw sid-alloc-mode? enumeration 189 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast: 190 +--ro routes 191 +--ro route* [prefix neighbor add-path-id] 192 +--ro prefix union 193 +--ro neighbor inet:ip-address 194 +--ro add-path-id uint32 195 +--ro srv6 196 +--ro received-sids* [received-sid] 197 | +--ro received-sid srv6-types:srv6-sid 198 +--ro local-sids* [local-sid] 199 +--ro local-sid srv6-types:srv6-sid 200 +--ro locator? -> /rt:routing/srv6:srv6/locators/locator/name 202 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast: 203 +--ro routes 204 +--ro route* [prefix neighbor add-path-id] 205 +--ro prefix union 206 +--ro neighbor inet:ip-address 207 +--ro add-path-id uint32 208 +--ro srv6 209 +--ro received-sids* [received-sid] 210 | +--ro received-sid srv6-types:srv6-sid 211 +--ro local-sids* [local-sid] 212 +--ro local-sid srv6-types:srv6-sid 213 +--ro locator? -> /rt:routing/srv6:srv6/locators/locator/name 215 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv4-unicast: 216 +--ro routes 217 +--ro route* [rd prefix neighbor add-path-id] 218 +--ro rd rt-types:route-distinguisher 219 +--ro prefix union 220 +--ro neighbor inet:ip-address 221 +--ro add-path-id uint32 222 +--ro srv6 223 +--ro received-sids* [received-sid] 224 | +--ro received-sid srv6-types:srv6-sid 225 +--ro local-sids* [local-sid] 226 +--ro local-sid srv6-types:srv6-sid 227 +--ro locator? -> /rt:routing/srv6:srv6/locators/locator/name 229 augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv6-unicast: 230 +--ro routes 231 +--ro route* [rd prefix neighbor add-path-id] 232 +--ro rd rt-types:route-distinguisher 233 +--ro prefix union 234 +--ro neighbor inet:ip-address 235 +--ro add-path-id uint32 236 +--ro srv6 237 +--ro received-sids* [received-sid] 238 | +--ro received-sid srv6-types:srv6-sid 239 +--ro local-sids* [local-sid] 240 +--ro local-sid srv6-types:srv6-sid 241 +--ro locator? -> /rt:routing/srv6:srv6/locators/locator/name 243 5. Notifications 245 TBD 247 6. Executables (Actions) 249 TBD 251 7. Yang Module 253 file "ietf-bgp-srv6-services@2019-07-08.yang" 255 module ietf-bgp-srv6-services { 256 yang-version 1.1; 257 namespace "urn:ietf:params:xml:ns:yang:ietf-bgp-srv6-services"; 258 // replace with IANA namespace when assigned 259 prefix bgp-srv6-svc ; 261 import ietf-inet-types { 262 prefix "inet"; 263 reference "RFC 6991: Common YANG Data Types"; 264 } 266 import ietf-routing-types { 267 prefix "rt-types"; 268 reference 269 "RFC 8294: Common YANG Data Types for the Routing Area"; 270 } 272 import ietf-routing { 273 prefix "rt"; 274 reference 275 "RFC 8349: A YANG Data Model for Routing Management (NMDA 276 version)"; 277 } 279 import ietf-srv6-types { 280 prefix srv6-types; 281 reference "RFC XXXX: YANG Data Model for SRv6"; 282 // RFC Editor: replace XXXX with actual RFC number and remove 283 // this note 284 } 286 import ietf-srv6-base { 287 prefix srv6; 289 } 291 import ietf-bgp { 292 prefix bgp; 293 } 295 organization 296 "IETF BESS Working Group"; 298 contact 299 "BESS working group - bess@ietf.org"; 301 description 302 "This YANG module defines a data model to configure and 303 manage SRv6 extensions in BGP. 305 Terms and Acronyms 307 AF : Address Family 309 BGP (bgp) : Border Gateway Protocol 311 EVPN: Ethernet VPN 313 SR : Segment Routing 315 SID : Segment Identifier 317 SRv6 : Segment Routing with IPv6 Data plane 319 VPN : Virtual Private Network 321 VRF : Virtual Routing and Forwarding 323 "; 325 revision 2019-07-08 { 326 description 327 "Initial revision" ; 328 reference ""; 329 } 331 // Sid type union 332 typedef sid-type { 333 type union { 334 type rt-types:mpls-label; 335 type srv6-types:srv6-sid; 336 } 337 description "Type definition for Segment Identifier. This is 338 a union type which can be either a SR MPLS SID in the 339 form of a label, or a SRv6 SID in the form of 340 an IPv6 address."; 341 reference "TBD"; 342 } 344 grouping route-key-leafs { 345 description "Grouping for key leafs identifying a route"; 346 leaf prefix { 347 type union { 348 type inet:ip-prefix; 349 type string; 350 } 351 description "BGP Prefix. This is a temp definition to 352 cover ip-prefix and other NLRI formats. 353 Import the type once defined in base 354 BGP RIB model"; 355 } 356 leaf neighbor { 357 type inet:ip-address; 358 description "BGP Neighbor"; 359 } 360 leaf add-path-id { 361 type uint32; 362 description "Add-path ID"; 363 } 364 } 366 grouping common-bgp-route-grouping { 367 description "BGP route list" ; 368 container routes { 369 config false; 370 description "BGP Route in local RIB"; 371 list route { 372 key "prefix neighbor add-path-id"; 373 description "BGP route list"; 374 uses route-key-leafs; 375 } 376 } 377 } 379 grouping common-bgp-vpn-route-grouping { 380 description "BGP route list" ; 381 container routes { 382 config false; 383 description "BGP VPN Route in local RIB"; 384 list route { 385 key "rd prefix neighbor add-path-id"; 386 description "Route List"; 388 leaf rd { 389 type rt-types:route-distinguisher; 390 description "Route Distinguisher"; 391 } 392 uses route-key-leafs; 393 } 394 } 395 } 397 // 398 // SRv6 extensions related Groupings 399 // 401 grouping srv6-grouping { 402 description "SRv6 container"; 404 container segment-routing { 405 description "Segment-routing parameters"; 407 container srv6 { 408 description "Segment-routing with IPv6 dataplane (SRv6) parameters"; 409 } 410 } 411 } 413 grouping srv6-locator-grouping { 414 description "SRv6 locator ref"; 415 leaf locator { 416 type leafref { 417 path "/rt:routing/srv6:srv6/srv6:locators/srv6:locator/srv6:name"; 418 } 419 description "Reference to an SRv6 Locator"; 420 } 421 } 423 grouping segment-routing-srv6-locator-grouping { 424 description 425 "An absolute reference to an SRv6 locator"; 427 container segment-routing { 428 description "Segment-routing parameters"; 430 container srv6 { 431 description "Segment-routing with IPv6 dataplane (SRv6) parameters"; 432 uses srv6-locator-grouping; 433 } 434 } 435 } 437 // SRv6 VPN Sid allocation mode 438 grouping srv6-sid-mode { 439 description "SRv6 VPN SID allocation mode"; 440 leaf sid-alloc-mode { 441 type enumeration { 442 enum per-ce { 443 description "Allocate SRv6 SID per CE"; 444 } 445 enum per-route { 446 description "Allocate SRv6 SID per prefix"; 447 } 448 enum per-vpn { 449 description "Allocate SRv6 SID per VPN"; 450 } 451 } 452 description "BGP SRv6 SID allocation model"; 453 } 454 } 456 grouping srv6-attr-sid-info { 457 description "SRv6 SID info per route"; 458 container srv6 { 459 description "Per Route SRv6 parameters"; 460 list received-sids { 461 key "received-sid"; 462 description "List of received SRv6 SIDs"; 463 leaf received-sid { 464 type srv6-types:srv6-sid; 465 description "Received SID"; 466 } 467 } 468 list local-sids { 469 key "local-sid"; 470 description "List of local SRv6 SIDs"; 471 leaf local-sid { 472 type srv6-types:srv6-sid; 473 description "Local SID"; 474 } 476 uses srv6-locator-grouping; 477 } 478 } 479 } 480 // 481 // BGP Specific Paramters 482 // 484 // SRv6 Loc designation 485 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 486 "bgp:bgp/bgp:global" { 487 description 488 "Augment BGP global"; 489 uses segment-routing-srv6-locator-grouping; 490 } 492 // Augment AF with route list 493 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 494 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast" { 495 description 496 "Augment BGP SAFI route"; 497 uses common-bgp-route-grouping; 498 } 499 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 500 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast" { 501 description 502 "Augment BGP SAFI route"; 503 uses common-bgp-route-grouping; 504 } 505 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 506 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv4-unicast" { 507 description 508 "Augment BGP SAFI route"; 509 uses common-bgp-vpn-route-grouping; 510 } 511 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 512 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv6-unicast" { 513 description 514 "Augment BGP SAFI route"; 515 uses common-bgp-vpn-route-grouping; 516 } 517 /* TODO 518 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 519 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l2vpn-evpn" { 520 description 521 "Augment BGP SAFI route"; 522 uses common-bgp-vpn-route-grouping; 523 } 524 */ 526 // SRv6 VPN SID allocation mode configuration. 527 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 528 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast" { 529 description 530 "Augment BGP global IPv4 unicast AF mode 531 to add SR specific parameters"; 532 container segment-routing { 533 description "Segment Routing specific parameters"; 534 container srv6 { 535 description "SRv6 specific parameters"; 536 uses srv6-locator-grouping; 537 uses srv6-sid-mode; 538 } 539 } 540 } 542 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 543 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast" { 544 description 545 "Augment BGP global IPv6 unicast AF mode 546 to add SR specific parameters"; 547 container segment-routing { 548 description "Segment Routing specific parameters"; 549 container srv6 { 550 description "SRv6 specific parameters"; 551 uses srv6-locator-grouping; 552 uses srv6-sid-mode; 553 } 554 } 555 } 557 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 558 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv4-unicast" { 559 description 560 "Augment BGP L3VPN IPv4 unicast AF mode 561 to add SR specific parameters"; 562 container segment-routing { 563 description "Segment Routing specific parameters"; 564 container srv6 { 565 description "SRv6 specific parameters"; 566 uses srv6-locator-grouping; 567 uses srv6-sid-mode; 568 } 569 } 570 } 572 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 573 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv6-unicast" { 574 description 575 "Augment BGP L3VPN IPv6 unicast AF mode 576 to add SR specific parameters"; 577 container segment-routing { 578 description "Segment Routing specific parameters"; 579 container srv6 { 580 description "SRv6 specific parameters"; 581 uses srv6-locator-grouping; 582 uses srv6-sid-mode; 583 } 584 } 585 } 587 // SRv6 local and remote sids per route. 588 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 589 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast/" + 590 "bgp-srv6-svc:routes/bgp-srv6-svc:route" { 591 description 592 "Augment AF route with SRv6 SID info"; 593 uses srv6-attr-sid-info; 594 } 595 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 596 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv6-unicast/" + 597 "bgp-srv6-svc:routes/bgp-srv6-svc:route" { 598 description 599 "Augment AF route with SRv6 SID info"; 600 uses srv6-attr-sid-info; 601 } 603 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 604 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv4-unicast/" + 605 "bgp-srv6-svc:routes/bgp-srv6-svc:route" { 606 description 607 "Augment AF route with SRv6 SID info"; 608 uses srv6-attr-sid-info; 609 } 611 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 612 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l3vpn-ipv6-unicast/" + 613 "bgp-srv6-svc:routes/bgp-srv6-svc:route" { 614 description 615 "Augment AF route with SRv6 SID info"; 616 uses srv6-attr-sid-info; 617 } 619 /* TODO 620 augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + 621 "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:l2vpn-evpn/" + 622 "bgp-srv6-svc:routes/bgp-srv6-svc:route" { 623 description 624 "Augment AF route with SRv6 SID info"; 625 uses srv6-attr-sid-info; 626 } 627 */ 629 } 631 633 8. IANA Considerations 635 This document requests the registration of the following URI in the 636 IETF "XML registry" [RFC3688]: 638 +------------------------------------------------+------------+-----+ 639 | URI | Registrant | XML | 640 +------------------------------------------------+------------+-----+ 641 | urn:ietf:params:xml:ns:yang:ietf-bgp- | The IESG | N/A | 642 | srv6-services | | | 643 +------------------------------------------------+------------+-----+ 645 This document requests the registration of the following YANG module 646 in the "YANG Module Names" registry [RFC6020]: 648 +--------------+------------------------------+------------+--------+ 649 | Name | Namespace | Prefix | Refere | 650 | | | | nce | 651 +--------------+------------------------------+------------+--------+ 652 | ietf-bgp-srv | urn:ietf:params:xml:ns:yang | bgp-srv6-s | This d | 653 | 6-services | :ietf-bgp-srv6-services | ervices | ocumen | 654 | | | | t | 655 +--------------+------------------------------+------------+--------+ 657 -- RFC Editor: Replace "This document" with the document RFC number 658 at time of publication, and remove this note. 660 9. Security Considerations 662 The transport protocol used for sending the BGP Segment Routing data 663 MUST support authentication and SHOULD support encryption. The data- 664 model by itself does not create any security implications. 666 This draft does not change any underlying security issues inherent in 667 [I-D.ietf-idr-bgp-model]. 669 10. Acknowledgements 671 TBD. 673 11. Contributors 675 Dhanendra Jain 676 Email: dhanendra.ietf@gmail.com 678 Zafar Ali 679 Cisco Systems 680 Email: zali@cisco.com 682 Sharmila Palani 683 Cisco Systems 684 Email: spalani@cisco.com 686 12. References 688 12.1. Normative References 690 [I-D.dawra-bess-srv6-services] 691 Dawra, G., Filsfils, C., Brissette, P., Agrawal, S., 692 Leddy, J., daniel.voyer@bell.ca, d., 693 daniel.bernier@bell.ca, d., Steinberg, D., Raszuk, R., 694 Decraene, B., Matsushima, S., Zhuang, S., and J. Rabadan, 695 "SRv6 BGP based Overlay services", draft-dawra-bess- 696 srv6-services-02 (work in progress), July 2019. 698 [I-D.ietf-idr-bgp-model] 699 Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP 700 YANG Model for Service Provider Networks", draft-ietf-idr- 701 bgp-model-09 (work in progress), June 2020. 703 [I-D.raza-spring-srv6-yang] 704 Raza, K., Agarwal, S., Liu, X., Hu, Z., Hussain, I., Shah, 705 H., Voyer, D., Elmalky, H., Matsushima, S., Horiba, K., 706 Abdelsalam, A., and J. Rajamanickam, "YANG Data Model for 707 SRv6 Base and Static", draft-raza-spring-srv6-yang-05 708 (work in progress), October 2019. 710 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 711 Requirement Levels", BCP 14, RFC 2119, 712 DOI 10.17487/RFC2119, March 1997, 713 . 715 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 716 DOI 10.17487/RFC3688, January 2004, 717 . 719 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 720 the Network Configuration Protocol (NETCONF)", RFC 6020, 721 DOI 10.17487/RFC6020, October 2010, 722 . 724 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 725 and A. Bierman, Ed., "Network Configuration Protocol 726 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 727 . 729 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 730 RFC 7950, DOI 10.17487/RFC7950, August 2016, 731 . 733 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 734 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 735 May 2017, . 737 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 738 and R. Wilton, "Network Management Datastore Architecture 739 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 740 . 742 [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of 743 Documents Containing YANG Data Models", BCP 216, RFC 8407, 744 DOI 10.17487/RFC8407, October 2018, 745 . 747 12.2. Informative References 749 [I-D.ietf-spring-srv6-network-programming] 750 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 751 Matsushima, S., and Z. Li, "SRv6 Network Programming", 752 draft-ietf-spring-srv6-network-programming-16 (work in 753 progress), June 2020. 755 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 756 Decraene, B., Litkowski, S., and R. Shakir, "Segment 757 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 758 July 2018, . 760 Authors' Addresses 762 Kamran Raza 763 Cisco Systems 764 Email: skraza@cisco.com 766 Kausik Majumdar 767 Ruckus Networks 768 Email: kmajumda7@gmail.com 770 Bruno Decraene 771 Orange 772 Email: bruno.decraene@orange.com 774 Zhichun Jiang 775 Alibaba 776 Email: zhichun.jzc@alibaba-inc.com 778 Satoru Matsushima 779 Softbank 780 Email: satoru.matsushima@g.softbank.co.jp