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