idnits 2.17.1 draft-zhao-pim-igmp-mld-snooping-yang-l2vpn-ext-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 17 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 09, 2022) is 690 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) ** Downref: Normative reference to an Informational RFC: RFC 4541 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 PIM Working Group H. Zhao 2 Internet Draft Ericsson 3 Intended status: Standards Track X. Liu 4 Expires: November 08, 2022 IBM Corporation 5 Y. Liu 6 China Mobile 7 M. Sivakumar 8 Juniper 9 A. Peter 10 Individual 12 May 09, 2022 14 IGMP and MLD Snooping Yang Module Extension for L2VPN 15 draft-zhao-pim-igmp-mld-snooping-yang-l2vpn-ext-01.txt 17 Abstract 19 Internet Group Management Protocol (IGMP) and Multicast Listener 20 Discovery (MLD) Snooping could be used in both BRIGDE service and L2VPN 21 service. The old ietf-igmp-mld-snooping yang module just describes the 22 BRIGDE service. In this document we extend the existing ietf-igmp-mld- 23 snooping yang module and make it could be used in L2VPN service. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html 45 This Internet-Draft will expire on November 08, 2022. 47 Copyright Notice 49 Copyright (c) 2022 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction...................................................3 65 1.1. Terminology...............................................3 66 1.2. Tree Diagrams.............................................3 67 1.3. Prefixes in Data Node Names...............................4 68 2. Design of Data Model...........................................4 69 3. Module Structure...............................................5 70 3.1. Mrouter interface for L2VPN...............................5 71 3.2. Outgoing interface for L2VPN..............................6 72 3.3. Using IGMP and MLD Snooping Instances in L2VPN service....7 73 4. IGMP and MLD Snooping Yang Module Extension....................7 74 5. Security Considerations.......................................12 75 6. IANA Considerations...........................................14 76 6.1. XML Registry.............................................14 77 6.2. YANG Module Names Registry...............................14 78 7. References....................................................14 79 7.1. Normative References.....................................14 80 7.2. Informative References...................................16 81 Appendix A. Data Tree Example...................................17 82 L2VPN service.................................................17 83 Authors' Addresses...............................................21 85 1. Introduction 87 The Internet Group Management Protocol (IGMP) and Multicast Listener 88 Discovery (MLD) Snooping [RFC4541] could be used in both BRIGE and 89 L2VPN. This document extends the existing ietf-igmp-mld-snooping yang 90 module and introduces l2vpn as a new l2-service-type [draft-ietf-pim- 91 igmp-mld-snooping-yang]. The YANG module in this document conforms to 92 the Network Management Datastore Architecture defined in [RFC8342]. 94 1.1. Terminology 96 The terminology for describing YANG data models is found in [RFC6020] 98 and [RFC7950], including: 100 * augment 102 * data model 104 * data node 106 * identity 108 * module 110 The following terminologies are used in this document: 112 * mrouter: The multicast router, which is a router that has multicast 113 routing enabled [RFC4286]. 115 * mrouter interface: The snooping switch ports where multicast 116 routers are attached [RFC4541]. Either Attachment Circuit (AC) or Pseudo 117 Wire (PW) could be mrouter interface in L2VPN. 119 The following abbreviations are used in this document and defined model: 121 IGMP: Internet Group Management Protocol [RFC3376]. 123 MLD: Multicast Listener Discovery [RFC3810]. 125 AC: Attachment Circuit [RFC3916]. 127 PW: Pseudo Wire [RFC3916]. 129 1.2. Tree Diagrams 131 Tree diagrams used in this document follow the notation defined in 133 [RFC8340]. 135 1.3. Prefixes in Data Node Names 137 In this document, names of data nodes, actions, and other data model 138 objects are often used without a prefix, as long as it is clear from the 139 context in which YANG module each name is defined. Otherwise, names are 140 prefixed using the standard prefix associated with the corresponding 141 YANG module, as shown in Table 1. 143 +-------+-----------------------+----------------------------------------+ 144 | Prefix| YANG module | Reference | 145 +=======+=======================+========================================+ 146 | if | ietf-interfaces | [RFC8343] | 147 +-------+-----------------------+----------------------------------------+ 148 | rt | ietf-routing | [RFC8349] | 149 +-------+-----------------------+----------------------------------------+ 150 | ni | ietf-network-instance | [RFC8529] | 151 +-------+-----------------------+----------------------------------------+ 152 | pw | ietf-pseudowires | [draft-ietf-bess-l2vpn-yang] | 153 +-------+-----------------------+----------------------------------------+ 154 | l2vpn | ietf-l2vpn | [draft-ietf-bess-l2vpn-yang] | 155 +-------+-----------------------+----------------------------------------+ 156 | ims | ietf-igmp-mld-snooping| [draft-ietf-pim-igmp-mld-snooping-yang]| 157 +-------+-----------------------+----------------------------------------+ 158 Table 1: Prefixes and Corresponding YANG Modules 160 2. Design of Data Model 162 Besides BRIDGE, IGMP & MLD snooping also provides a way to constrain 163 multicast traffic for L2VPN. By monitoring the IGMP & MLD membership 164 reports sent by hosts within the L2VPN domain, IGMP & MLD snooping can 165 set up Layer 2 multicast forwarding tables to deliver traffic only to 166 ports with at least one interested member within the L2VPN domain. 167 Thereby significantly reduce the volume of multicast traffic that would 168 otherwise flood an entire L2VPN domain. The IGMP & MLD snooping 169 operation applies to both access circuits and pseudowires within a L2VPN 170 domain. A network-instance [RFC8529] whose type is vpls-instance-type 171 [draft-ietf-bess-l2vpn-yang] could be treated as a L2VPN domain. 173 The YANG module in this document includes all the common building blocks 174 for IGMP & MLD snooping used in L2VPN. It defines a new L2 service type 175 which is L2VPN [draft-ietf-bess-l2vpn-yang]. When value of l2-service- 176 type is l2vpn, the IGMP & MLD Snooping instance will be used in the 177 L2VPN service. One instance corresponds to one L2VPN [draft-ietf-bess- 178 l2vpn-yang] instance. It also defines mrouter interface and outgoing 179 interface including statically configured and dynamically learned. 181 3. Module Structure 183 This module augments ietf-igmp-mld-snooping data model specified in 184 [draft-ietf-pim-igmp-mld-snooping-yang]. It adds mrouter interface, 185 outgoing AC and outgoing PW which could be used in both igmp-snooping- 186 instance and mld-snooping-instance. 188 This module also defines how to use the igmp-snooping-instance and mld- 189 snooping-instance in L2VPN service. 191 This module conforms to the Network Management Datastore Architecture 192 (NMDA) [RFC8342]. The operational state data is combined with the 193 associated configuration data in the same hierarchy [RFC8407]. 195 3.1. Mrouter interface for L2VPN 197 This module augments /rt:routing/rt:control-plane-protocols/rt:control- 198 plane-protocol/ims:igmp-snooping-instance to add mrouter interface for 199 L2VPN in IGMP Snooping. 201 The static-l2vpn-mrouter-interface-ac and static-l2vpn-mrouter- 202 interface-pw represent mrouter interfaces which are manually configured. 204 The l2vpn-mrouter-interface-ac and l2vpn-mrouter-interface-pw represent 205 mrouter interfaces learned by the snooping device dynamically. 207 augment /rt:routing/rt:control-plane-protocols 208 /rt:control-plane-protocol/ims:igmp-snooping-instance: 209 +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref 210 +--rw static-l2vpn-mrouter-interface-pw* pw:pseudowire-ref 211 +--ro l2vpn-mrouter-interface-ac* if:interface-ref 212 +--ro l2vpn-mrouter-interface-pw* pw:pseudowire-ref 214 Similarly this module also augments /rt:routing/rt:control-plane- 215 protocols/rt:control-plane-protocol/ims:mld-snooping-instance to add 216 mrouter interface for L2VPN in MLD Snooping. 218 augment /rt:routing/rt:control-plane-protocols 219 /rt:control-plane-protocol/ims:mld-snooping-instance: 220 +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref 221 +--rw static-l2vpn-mrouter-interface-pw* pw:pseudowire-ref 222 +--ro l2vpn-mrouter-interface-ac* if:interface-ref 223 +--ro l2vpn-mrouter-interface-pw* pw:pseudowire-ref 225 3.2. Outgoing interface for L2VPN 227 IGMP & MLD snooping can set up Layer 2 multicast forwarding tables to 228 deliver multicast traffic, so each packet should have at least one 229 corresponding outgoing interface. The outgoing interfaces might be 230 Attachment Circuit (AC) or Pseudo Wire (PW) in L2VPN. They could be 231 manually configured or dynamically learned by the snooping device. 233 This module augments /rt:routing/rt:control-plane-protocols/rt:control- 234 plane-protocol/ims:igmp-snooping-instance/ims:static-l2-multicast-group 235 to add l2vpn-outgoing-ac and l2vpn-outgoing-pw for L2VPN in IGMP 236 Snooping. They should be configured manually. 238 augment /rt:routing/rt:control-plane-protocols 239 /rt:control-plane-protocol/ims:igmp-snooping-instance 240 /ims:static-l2-multicast-group: 241 +--rw l2vpn-outgoing-ac* if:interface-ref 242 +--rw l2vpn-outgoing-pw* pw:pseudowire-ref 244 Similarly it also augments /rt:routing/rt:control-plane- 245 protocols/rt:control-plane-protocol/ims:mld-snooping- 246 instance/ims:static-l2-multicast-group to add l2vpn-outgoing-ac and 247 l2vpn-outgoing-pw for L2VPN in MLD Snooping. They should be configured 248 manually. 250 augment /rt:routing/rt:control-plane-protocols 251 /rt:control-plane-protocol/ims:mld-snooping-instance 252 /ims:static-l2-multicast-group: 253 +--rw l2vpn-outgoing-ac* if:interface-ref 254 +--rw l2vpn-outgoing-pw* pw:pseudowire-ref 256 This module augments /rt:routing/rt:control-plane-protocols/rt:control- 257 plane-protocol/ims:igmp-snooping-instance/ims:group/ims:source to add 258 l2vpn-outgoing-ac and l2vpn-outgoing-pw for L2VPN in IGMP Snooping. They 259 are read only and should be filled dynamically. 261 augment /rt:routing/rt:control-plane-protocols 262 /rt:control-plane-protocol/ims:igmp-snooping-instance 263 /ims:group/ims:source: 264 +--ro l2vpn-outgoing-ac* if:interface-ref 265 +--ro l2vpn-outgoing-pw* pw:pseudowire-ref 267 Similarly it also augments /rt:routing/rt:control-plane- 268 protocols/rt:control-plane-protocol/ims:mld-snooping- 269 instance/ims:group/ims:source to add l2vpn-outgoing-ac and l2vpn- 270 outgoing-pw for L2VPN in MLD Snooping. They are read only and should be 271 filled dynamically. 273 augment /rt:routing/rt:control-plane-protocols 274 /rt:control-plane-protocol/ims:mld-snooping-instance 275 /ims:group/ims:source: 276 +--ro l2vpn-outgoing-ac* if:interface-ref 277 +--ro l2vpn-outgoing-pw* pw:pseudowire-ref 279 3.3. Using IGMP and MLD Snooping Instances in L2VPN service 281 This module augments /ni:network-instances/ni:network-instance/ni:ni- 282 type/l2vpn:l2vpn [RFC8529] to use igmp-snooping-instance. It means IGMP 283 Snooping is enabled in the specified L2VPN instance. 285 augment /ni:network-instances/ni:network-instance/ni:ni-type 286 /l2vpn:l2vpn: 287 +--rw igmp-snooping-instance? 288 | ims:igmp-mld-snooping-instance-ref 289 +--rw mld-snooping-instance? 290 ims:igmp-mld-snooping-instance-ref 292 The mld-snooping-instance could be used in concurrence with igmp- 293 snooping-instance to configure the MLD Snooping. 295 4. IGMP and MLD Snooping Yang Module Extension 297 This module references [RFC1112],[RFC2236],[RFC2710],[RFC3376], 298 [RFC3810],[RFC4541],[RFC5790],[RFC6991],[RFC7761],[RFC8343],[RFC8529],[d 299 raft-ietf-pim-igmp-mld-snooping-yang] and [draft-ietf-bess-l2vpn-yang]. 301 file ietf-igmp-mld-snooping-l2vpn@2021-10-25.yang 302 module ietf-igmp-mld-snooping-l2vpn { 303 yang-version 1.1; 304 namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping-l2vpn"; 306 prefix ims-l2vpn; 308 import ietf-interfaces { 309 prefix "if"; 310 reference 311 "RFC 8343: A YANG Data Model for Interface Management"; 312 } 314 import ietf-routing { 315 prefix "rt"; 316 reference 317 "RFC 8349: A YANG Data Model for Routing Management (NMDA 318 Version)"; 319 } 321 import ietf-network-instance { 322 prefix "ni"; 323 reference 324 "RFC 8529: YANG Data Model for Network Instances"; 326 } 328 import ietf-l2vpn { 329 prefix "l2vpn"; 330 reference 331 "draft-ietf-bess-l2vpn-yang: YANG Data Model for MPLS-based 332 L2VPN"; 333 } 335 import ietf-pseudowires { 336 prefix "pw"; 337 reference 338 "draft-ietf-bess-l2vpn-yang: YANG Data Model for MPLS-based 339 L2VPN"; 340 } 342 import ietf-igmp-mld-snooping { 343 prefix "ims"; 344 reference 345 "draft-ietf-pim-igmp-mld-snooping-yang: A Yang Data Model for IGMP 346 and MLD Snooping"; 347 } 349 organization 350 "IETF PIM Working Group"; 352 contact 353 "WG Web: 354 WG List: 356 Editors: Hongji Zhao 357 359 Xufeng Liu 360 362 Yisong Liu 363 365 Anish Peter 366 368 Mahesh Sivakumar 369 371 "; 373 description 374 "The module contains a collection of YANG definitions of 375 IGMP & MLD Snooping in L2VPN service. 377 Copyright (c) 2021 IETF Trust and the persons identified as 378 authors of the code. All rights reserved. 380 Redistribution and use in source and binary forms, with or 381 without modification, is permitted pursuant to, and subject to 382 the license terms contained in, the Simplified BSD License set 383 forth in Section 4.c of the IETF Trust's Legal Provisions 384 Relating to IETF Documents 385 (http://trustee.ietf.org/license-info). 387 This version of this YANG module is part of RFC XXXX; see the 388 RFC itself for full legal notices."; 390 revision 2021-10-25 { 391 description 392 "Initial revision."; 393 reference 394 "RFC XXXX: IGMP and MLD Snooping Yang Module Extension in L2VPN 395 service"; 396 } 398 /* identities */ 400 identity l2vpn { 401 base ims:l2-service-type; 402 description 403 "This identity represents L2VPN service."; 404 } 406 /* 407 * Groupings 408 */ 410 grouping static-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping { 411 description 412 "The static mrouter interface in L2VPN service."; 414 leaf-list static-l2vpn-mrouter-interface-ac { 415 when 'derived-from-or-self(../l2-service-type,"ims:l2vpn")'; 416 type if:interface-ref; 417 description 418 "The static mrouter interface whose type is interface 419 in L2VPN service."; 420 } 422 leaf-list static-l2vpn-mrouter-interface-pw { 423 when 'derived-from-or-self(../l2-service-type,"ims:l2vpn")'; 424 type pw:pseudowire-ref; 425 description 426 "The static mrouter interface whose type is PW 427 in L2VPN service."; 428 } 429 } 430 grouping dynamic-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping { 432 description 433 "The dynamic mrouter interface in L2VPN service."; 435 leaf-list l2vpn-mrouter-interface-ac { 436 when 'derived-from-or-self(../l2-service-type,"ims:l2vpn")'; 437 type if:interface-ref; 438 config false; 439 description 440 "The mrouter interface whose type is interface in L2VPN 441 service. When switch receives IGMP/MLD queries from 442 multicast router on an interface, this interface will 443 become mrouter interface for IGMP/MLD snooping."; 444 } 446 leaf-list l2vpn-mrouter-interface-pw { 447 when 'derived-from-or-self(../l2-service-type,"ims:l2vpn")'; 448 type pw:pseudowire-ref; 449 config false; 450 description 451 "The mrouter interface whose type is PW in L2VPN service. 452 When switch receives IGMP/MLD queries from multicast router 453 on a PW, this PW will become mrouter interface for IGMP/MLD 454 snooping."; 455 } 456 } 458 grouping l2vpn-outgoing-ac-pw-igmp-mld-snooping { 459 description 460 "Outgoing Attachment Circuit (AC) or Pseudo Wire (PW) in L2VPN."; 462 leaf-list l2vpn-outgoing-ac { 463 when 'derived-from-or-self(../../../l2-service-type,"ims:l2vpn")'; 464 type if:interface-ref; 465 description "Outgoing Attachment Circuit (AC) in L2VPN"; 466 } 468 leaf-list l2vpn-outgoing-pw { 469 when 'derived-from-or-self(../../../l2-service-type,"ims:l2vpn")'; 470 type pw:pseudowire-ref; 471 description "Outgoing Pseudo Wire (PW) in L2VPN"; 472 } 473 } 475 /* 476 * The mrouter interface in L2VPN service. 477 */ 479 augment "/rt:routing/rt:control-plane-protocols"+ 480 "/rt:control-plane-protocol/ims:igmp-snooping-instance" { 482 description 483 "The mrouter interface in L2VPN service for IGMP Snooping."; 485 uses static-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping; 487 uses dynamic-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping; 489 } 491 augment "/rt:routing/rt:control-plane-protocols"+ 492 "/rt:control-plane-protocol/ims:mld-snooping-instance" { 493 description 494 "The mrouter interface in L2VPN service for MLD Snooping."; 496 uses static-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping; 498 uses dynamic-l2vpn-mrouter-interface-ac-pw-igmp-mld-snooping; 500 } 502 /* 503 * Static Outgoing AC or PW in L2VPN service 504 */ 506 augment "/rt:routing/rt:control-plane-protocols"+ 507 "/rt:control-plane-protocol"+ 508 "/ims:igmp-snooping-instance/ims:static-l2-multicast-group" { 510 description 511 "Static Outgoing AC or PW in L2VPN service for IGMP snooping."; 513 uses l2vpn-outgoing-ac-pw-igmp-mld-snooping; 515 } 517 augment "/rt:routing/rt:control-plane-protocols"+ 518 "/rt:control-plane-protocol"+ 519 "/ims:mld-snooping-instance/ims:static-l2-multicast-group" { 521 description 522 "Static Outgoing AC or PW in L2VPN service for MLD snooping."; 524 uses l2vpn-outgoing-ac-pw-igmp-mld-snooping; 526 } 528 /* 529 * Dynamic Outgoing AC or PW in L2VPN service 530 */ 532 augment "/rt:routing/rt:control-plane-protocols"+ 533 "/rt:control-plane-protocol"+ 534 "/ims:igmp-snooping-instance/ims:group/ims:source" { 536 description 537 "Dynamic Outgoing AC or PW in L2VPN service for IGMP snooping."; 539 uses l2vpn-outgoing-ac-pw-igmp-mld-snooping; 541 } 543 augment "/rt:routing/rt:control-plane-protocols"+ 544 "/rt:control-plane-protocol"+ 545 "/ims:mld-snooping-instance/ims:group/ims:source" { 547 description 548 "Dynamic Outgoing AC or PW in L2VPN service for MLD snooping."; 550 uses l2vpn-outgoing-ac-pw-igmp-mld-snooping; 552 } 554 /* 555 * Use IGMP & MLD snooping instance in L2VPN 556 */ 558 augment "/ni:network-instances/ni:network-instance"+ 559 "/ni:ni-type/l2vpn:l2vpn" { 561 description 562 "Use IGMP & MLD snooping instance in L2VPN."; 564 leaf igmp-snooping-instance { 565 type ims:igmp-mld-snooping-instance-ref; 566 description 567 "Configure IGMP snooping instance in L2VPN."; 568 } 570 leaf mld-snooping-instance { 571 type ims:igmp-mld-snooping-instance-ref; 572 description 573 "Configure MLD snooping instance in L2VPN."; 574 } 575 } 576 } 577 579 5. Security Considerations 581 The YANG module specified in this document defines a schema for data 582 that is designed to be accessed via network management protocols such as 583 NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the 584 secure transport layer, and the mandatory-to-implement secure transport 585 is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and 586 the mandatory-to-implement secure transport is TLS [RFC8446]. 588 The Network Configuration Access Control Model (NACM) [RFC8341] provides 589 the means to restrict access for particular NETCONF or RESTCONF users to 590 a preconfigured subset of all available NETCONF or RESTCONF protocol 591 operations and content. 593 There are a number of data nodes defined in this YANG module that are 594 writable/creatable/deletable (i.e., config true, which is the default). 595 These data nodes may be considered sensitive or vulnerable in some 596 network environments. Write operations (e.g., edit-config) to these data 597 nodes without proper protection can have a negative effect on network 598 operations. These are the subtrees and data nodes and their 599 sensitivity/vulnerability, and they are all under 600 /rt:routing/rt:control-plane-protocols/rt:control-plane- 601 protocol:/ims:igmp-snooping-instance or /rt:routing/rt:control-plane- 602 protocols/rt:control-plane-protocol:/ims:mld-snooping-instance : 604 /igmp-mld-snooping-extension:static-l2vpn-mrouter-interface-ac 606 /igmp-mld-snooping-extension:static-l2vpn-mrouter-interface-pw 608 /ims:static-l2-multicast-group/igmp-mld-snooping-extension:l2vpn-outgoing-ac 610 /ims:static-l2-multicast-group/igmp-mld-snooping-extension:l2vpn-outgoing-pw 612 The subtrees under /ni:network-instances/ni:network-instance/ni:ni- 613 type/l2vpn:l2vpn 615 ims:igmp-snooping-instance 617 ims:mld-snooping-instance 619 Unauthorized access to any data node of these subtrees can adversely 620 affect the IGMP & MLD Snooping subsystem of both the local device and 621 the network. This may lead to network malfunctions, delivery of packets 622 to inappropriate destinations, and other problems. 624 Some of the readable data nodes in this YANG module may be considered 625 sensitive or vulnerable in some network environments. It is thus 626 important to control read access (e.g., via get, get-config, or 627 notification) to these data nodes. These are the subtrees and data nodes 628 and their sensitivity/vulnerability, and they are all under 629 /rt:routing/rt:control-plane-protocols/rt:control-plane- 630 protocol:/ims:igmp-snooping-instance or /rt:routing/rt:control-plane- 631 protocols/rt:control-plane-protocol:/ims:mld-snooping-instance: 633 /igmp-mld-snooping-extension:l2vpn-mrouter-interface-ac 635 /igmp-mld-snooping-extension:l2vpn-mrouter-interface-pw 636 /ims:group/ims:source/igmp-mld-snooping-extension:l2vpn-outgoing-ac 638 /ims:group/ims:source/igmp-mld-snooping-extension:l2vpn-outgoing-pw 640 Unauthorized access to any data node of these subtrees can disclose the 641 operational state information of IGMP & MLD Snooping on this device. The 642 devices that use this YANG module should heed the Security 643 Considerations in [RFC4541]. 645 6. IANA Considerations 647 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 648 actual RFC number (and remove this note). 650 6.1. XML Registry 652 This document registers the following namespace URIs in the IETF XML 654 registry [RFC3688]: 656 -------------------------------------------------------------------- 657 URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping-l2vpn 658 Registrant Contact: The IETF. 659 XML: N/A, the requested URI is an XML namespace. 660 -------------------------------------------------------------------- 662 6.2. YANG Module Names Registry 664 This document registers the following YANG modules in the YANG Module 665 Names registry [RFC7950]: 666 -------------------------------------------------------------------- 667 name: ietf-igmp-mld-snooping-l2vpn 668 namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping-l2vpn 669 prefix: ims-l2vpn 670 reference: RFC XXXX 671 -------------------------------------------------------------------- 672 7. References 674 7.1. Normative References 676 [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, 677 RFC 1112, August 1989. 679 [RFC2236] W. Fenner, "Internet Group Management Protocol, Version 2", 680 RFC 2236, November 1997. 682 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 683 Listener Discovery (MLD) for IPv6", RFC 2710, October 1999. 685 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 686 Thyagarajan, "Internet Group Management Protocol, Version 687 3", RFC 3376, October 2002. 689 [RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January 690 2004. 692 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 693 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 695 [RFC4286] B. Haberman and J. Martin, "Multicast Router Discovery", 696 RFC 4286, December 2005. 698 [RFC4541] M. Christensen, K. Kimball, F. Solensky, "Considerations 699 for Internet Group Management Protocol (IGMP) and Multicast 700 Listener Discovery (MLD) Snooping Switches", RFC 4541, May 701 2006. 703 [RFC5790] H. Liu, W. Cao, H. Asaeda, "Lightweight Internet Group 704 Management Protocol Version 3 (IGMPv3) and Multicast 705 Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790, 706 February 2010. 708 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 709 the Network Configuration Protocol (NETCONF)", RFC 6020, 710 October 2010. 712 [RFC6241] R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder, Ed., A. 713 Bierman, Ed., "Network Configuration Protocol (NETCONF)", 714 RFC 6241, June 2011. 716 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 717 Shell (SSH)", RFC 6242, June 2011. 719 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, 720 July 2013. 722 [RFC7761] B. Fenner, M. Handley, H. Holbrook, I. Kouvelas, R. Parekh, 723 Z. Zhang, L. Zheng, "Protocol Independent Multicast - 724 Sparse Mode (PIM-SM): Protocol Specification (Revised)", 725 RFC 7761, March 2016. 727 [RFC7950] M. Bjorklund, Ed., "The YANG 1.1 Data Modeling Language", 728 RFC 7950, August 2016. 730 [RFC8040] A. Bierman, M. Bjorklund, K. Watsen, "RESTCONF Protocol", 731 RFC 8040, January 2017. 733 [RFC8340] M. Bjorklund, and L. Berger, Ed., "YANG Tree Diagrams", RFC 734 8340, March 2018. 736 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access 737 Control Model", RFC 8341, March 2018. 739 [RFC8342] M. Bjorklund and J. Schoenwaelder, "Network Management 740 Datastore Architecture (NMDA)", RFC 8342, March 2018. 742 [RFC8343] M. Bjorklund, "A YANG Data Model for Interface Management", 743 RFC 8343, March 2018. 745 [RFC8349] L. Lhotka, A. Lindem, Y. Qu, "A YANG Data Model for Routing 746 Management (NMDA Version)", RFC 8349, March 2018. 748 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 749 Version 1.3", RFC 8446, August 2018. 751 [RFC8529] L. Berger, C. Hopps, A. Lindem, D. Bogdanovic, X. Liu, 752 "YANG Data Model for Network Instances", RFC 8529, March 753 2019. 755 [draft-ietf-bess-l2vpn-yang] Shah, H., Brissette, P., Chen, I., 756 Hussain, I., Wen, B., and K. Tiruveedhula, "YANG Data Model 757 for MPLS-basedL2VPN", draft-ietf-bess-l2vpn-yang-10 (work 758 in progress), July 2019. 760 7.2. Informative References 762 [RFC3916] X. Xiao, Ed., D. McPherson, Ed., P. Pate, Ed., 763 "Requirements for Pseudo-Wire Emulation Edge-to-Edge 764 (PWE3)", RFC 3916, September 2004. 766 [RFC7951] L. Lhotka, "JSON Encoding of Data Modeled with YANG", RFC 767 7951, August 2016. 769 [RFC8407] A. Bierman, "Guidelines for Authors and Reviewers of 770 Documents Containing YANG Data Models", RFC 8407, October 771 2018. 773 Appendix A. Data Tree Example 775 L2VPN service 777 This section contains an example for L2VPN service in the JSON encoding 778 [RFC7951], containing both configuration and state data. 780 +-----------+ 781 + Source + 782 +-----+-----+ 783 | 784 -----------------+---------------------------- 785 |eth1/1 786 +---+---+ 787 + R1 + 788 +-+---+-+ 789 eth1/2 | \ eth1/3 790 | \ 791 | \ 792 | \ 793 | \ 794 eth2/1 | \ eth3/1 795 +---+---+ +-+---+ 796 + R2 +---+ R3 + 797 +---+---+ +-+---+ 798 eth2/2 | | eth3/2 799 | | 800 ---------------+----------+------------------- 801 | | 802 | | 803 +--------+--+ +---+--------+ 804 + Receiver1 + + Receiver2 + 805 +-----------+ +------------+ 807 The configuration data for R1 in the above figure could be as follows: 808 { 809 "ietf-interfaces:interfaces":{ 810 "interface":[ 811 { 812 "name":"eth1/1", 813 "type":"iana-if-type:ethernetCsmacd" 814 } 815 ] 816 }, 817 "ietf-pseudowires:pseudowires": { 818 "pseudowire": [ 819 { 820 "name": "pw2" 821 }, 822 { 823 "name": "pw3" 824 } 825 ] 826 }, 827 "ietf-network-instance:network-instances": { 828 "network-instance": [ 829 { 830 "name": "vpls1", 831 "ietf-igmp-mld-snooping:igmp-snooping-instance": "vis1", 832 "ietf-l2vpn:type": "ietf-l2vpn:vpls-instance-type", 833 "ietf-l2vpn:signaling-type": "ietf-l2vpn:ldp-signaling", 834 "ietf-l2vpn:endpoint": [ 835 { 836 "name": "acs", 837 "ac": [ 838 { 839 "name": "eth1/1" 840 } 841 ] 842 }, 843 { 844 "name": "pws", 845 "pw": [ 846 { 847 "name": "pw2" 848 }, 849 { 850 "name": "pw3" 851 } 852 ] 853 } 854 ] 855 } 856 ] 857 }, 858 "ietf-routing:routing": { 859 "control-plane-protocols": { 860 "control-plane-protocol": [ 861 { 862 "type": "ietf-igmp-mld-snooping:igmp-snooping", 863 "name": "vis1", 864 "ietf-igmp-mld-snooping:igmp-snooping-instance": { 865 "l2-service-type": "ims-l2vpn:l2vpn", 866 "enable": true 867 } 868 } 869 ] 870 } 871 } 872 } 873 The corresponding operational state data for R1 could be as follows: 875 { 876 "ietf-interfaces:interfaces":{ 877 "interface":[ 878 { 879 "name":"eth1/1", 880 "type":"iana-if-type:ethernetCsmacd", 881 "oper-status": "up", 882 "statistics": { 883 "discontinuity-time": "2018-05-23T12:34:56-05:00" 884 } 885 } 886 ] 887 }, 888 "ietf-pseudowires:pseudowires": { 889 "pseudowire": [ 890 { 891 "name": "pw2" 892 }, 893 { 894 "name": "pw3" 895 } 896 ] 897 }, 898 "ietf-network-instance:network-instances": { 899 "network-instance": [ 900 { 901 "name": "vpls1", 902 "ietf-igmp-mld-snooping:igmp-snooping-instance": "vis1", 903 "ietf-l2vpn:type": "ietf-l2vpn:vpls-instance-type", 904 "ietf-l2vpn:signaling-type": "ietf-l2vpn:ldp-signaling", 905 "ietf-l2vpn:endpoint": [ 906 { 907 "name": "acs", 908 "ac": [ 909 { 910 "name": "eth1/1" 911 } 912 ] 913 }, 914 { 915 "name": "pws", 916 "pw": [ 917 { 918 "name": "pw2" 919 }, 920 { 921 "name": "pw3" 922 } 924 ] 925 } 926 ] 927 } 928 ] 929 }, 930 "ietf-routing:routing": { 931 "control-plane-protocols": { 932 "control-plane-protocol": [ 933 { 934 "type": "ietf-igmp-mld-snooping:igmp-snooping", 935 "name": "vis1", 936 "ietf-igmp-mld-snooping:igmp-snooping-instance": { 937 "l2-service-type": "ims-l2vpn:l2vpn", 938 "enable": true 939 } 940 } 941 ] 942 } 943 } 944 } 945 Authors' Addresses 947 Hongji Zhao 948 Ericsson (China) Communications Company Ltd. 949 Ericsson Tower, No. 5 Lize East Street, 950 Chaoyang District Beijing 100102, China 952 Email: hongji.zhao@ericsson.com 954 Xufeng Liu 955 IBM Corporation 956 2300 Dulles Station Blvd. 957 Herndon, VA 20171 958 United States of America 960 EMail: xufeng.liu.ietf@gmail.com 962 Yisong Liu 963 China Mobile 964 China 966 Email: liuyisong@chinamobile.com 968 Anish Peter 969 Individual 971 EMail: anish.ietf@gmail.com 973 Mahesh Sivakumar 974 Juniper Networks 975 1133 Innovation Way 976 Sunnyvale, California 977 USA 979 EMail: sivakumar.mahesh@gmail.com