idnits 2.17.1 draft-zhang-mboned-multicast-info-model-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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 49 instances of too long lines in the document, the longest one being 44 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 (February 23, 2017) is 2619 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-bier-architecture' is defined on line 696, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-bier-bier-yang' is defined on line 702, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-yang' is defined on line 708, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 714, but no explicit reference was found in the text == Unused Reference: 'RFC6037' is defined on line 719, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 724, but no explicit reference was found in the text == Unused Reference: 'RFC6513' is defined on line 728, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 732, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-05 == Outdated reference: A later version (-08) exists of draft-ietf-bier-bier-yang-01 == Outdated reference: A later version (-17) exists of draft-ietf-pim-yang-05 ** Downref: Normative reference to an Historic RFC: RFC 6037 ** Obsolete normative reference: RFC 6087 (Obsoleted by RFC 8407) ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 6 errors (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MBONED WG Zheng. Zhang 3 Internet-Draft Cui. Wang 4 Intended status: Standards Track ZTE Corporation 5 Expires: August 27, 2017 Stig. Venaas 6 Cisco Systems, Inc. 7 February 23, 2017 9 Multicast Model 10 draft-zhang-mboned-multicast-info-model-01 12 Abstract 14 This document intents to provide a general and all-round multicast 15 model, which tries to stand at a high level to take full advantages 16 of existed multicast protocol models to control the multicast 17 network, and guides the deployment of multicast service. And also, 18 there will define several possible RPCs about how to interact between 19 multicast info model and multicast protocol models. This multicast 20 information model is mainly used by the management tools run by the 21 network operators in order to manage, monitor and debug the network 22 resources used to deliver multicast service, as well as gathering 23 some data from the network. 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). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 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 This Internet-Draft will expire on August 27, 2017. 42 Copyright Notice 44 Copyright (c) 2017 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Design of the multicast model . . . . . . . . . . . . . . . . 3 61 3. UML Class Diagram for Multicast Info Model . . . . . . . . . 4 62 4. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 5 63 5. Multicast Information Model . . . . . . . . . . . . . . . . . 7 64 6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 16 65 7. Normative References . . . . . . . . . . . . . . . . . . . . 16 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 68 1. Introduction 70 Currently, there are many multicast YANG models, such as PIM, MLD, 71 and BIER and so on. But all these models are distributed in 72 different working groups as separate files and focus on the protocol 73 itself. Furthermore, they cannot describe a high-level multicast 74 service required by network operators. 76 This document intents to provide a general and all-round multicast 77 model, which tries to stand at a high level to take full advantages 78 of these aforementioned models to control the multicast network, and 79 guides the deployment of multicast service. 81 This multicast information model is mainly used by the management 82 tools run by the network operators in order to manage, monitor and 83 debug the network resources used to deliver multicast service, as 84 well as gathering some data from the network. 86 +------------------------+ 87 | Multicast Info | 88 +------------------------+ 89 | | | 90 | | | 91 | +---------+ +----------+ 92 | | EMS/NMS | |Controller| 93 | +---------+ +----------+ 94 | | | 95 | | | 96 +------------------------------------------------+ 97 | Network Element1.....N | 98 +------------------------------------------------+ 100 Figure 1: Example usage of Multicast Model 102 Detailly,in figure 1, there is an example of usage of this multicast 103 model. Network operators can input this model to a controller who is 104 responsible to translate the information and invoke the corresponding 105 protocol models into configurations to configure the network elements 106 through NETCONF/RESTCONF/CLI. Or network operators can input this 107 model to the EMS/NMS to manage the network elements or configure the 108 network elements directly. On the other hand, when the network 109 elements detect failure or some other changes, the network operators 110 can collect these kind of notifications through this model to assist 111 locating the exact failure and responsing immediatly. for example, 112 when the network element suffers a failure of one MVPN neighbor, it 113 can notify to the EMS/NMS or Controller or to other Multicast Model 114 management tool directly to let the network operator take actions 115 immediately. 117 Specifically, in section 3, it provides a human readability of the 118 whole multicast network through UML class diagram, which frames 119 different multicast components and correlates them in a readable 120 fashion. Then, based on this UML class diagram, there is 121 instantiated and detailed YANG model in Section 5. 123 In other words, this document does not define any specific protocol 124 model, instead, it depends on many existed multicast protocol models 125 and relates several multicast information together to fulfill 126 multicast service. 128 2. Design of the multicast model 130 This model includes three layers: the multicast overlay, the 131 transport layer and the multicast underlay information. 133 Multicast overlay defines the features of multicast flow, such 134 as(vpnid, multicast source and multicast group) information, and 135 (ingress-node,egress-nodes) nodes information. If the transport 136 layer is BIER, there may define BIER information including 137 (Subdomain, ingress-node BFR-id, egress-nodes BFR-id). In data 138 center network, for fine-grained to gather the nodes belonging to the 139 same virtual network, there may need VNI-related information to 140 assist. If no (ingress-node, egress-nodes) information are defined 141 directly, there may need overlay multicast signaling technology, such 142 as MLD or MVPN, to collect these nodes information. 144 Multicast transport layer defines the type of transport technologies 145 that can be used to forward multicast flow, including BIER forwarding 146 type, MPLS forwarding type, or PIM forwarding type and so on. One or 147 several transport technologies could be defined at the same time. As 148 for the detailed parameters for each transport technology, this 149 multicast information model can invoke the corresponding protocol 150 model to define them. 152 Multicast underlay defines the type of underlay technologies, such as 153 OSPF, ISIS, BGP, PIM or BABEL and so on. One or several underlay 154 technologies could be defined at the same time. As for the specific 155 parameters for each underlay technology, this multicast information 156 model can depend the corresponding protocol model to configure them 157 as well. 159 3. UML Class Diagram for Multicast Info Model 161 The following is a UML diagram for Multicast Info Model. 163 +----------------+ 164 | Multicast Info | 165 +----------------+ 166 | | |Contain 167 +---------------------------+ | +---------------------------+ 168 | | | 169 +-------------------+ +---------------------+ +--------------------+ 170 | Multicast Overlay | | Multicast Transport | | Multicast Underlay | 171 +-------------------+ +---------------------+ +--------------------+ 172 | |Contain | | | | invoke | | | | invoke 173 +--------+ +-------+ +----+ | | +----+ +----+ | | +----+ 174 | | | | | | | | | | 175 +--------------+ +--------------+ +-----+ | | +------+ +------+ | | +------+ 176 | Multi-Info | | Ing/Eg Nodes | | PIM | | | | MPLS | | OSPF | | | | PIM | 177 +--------------+ +--------------+ +-----+ | | +------+ +------+ | | +------+ 178 |Group Address | |Ingress Nodes | | | | | 179 +--------------+ +--------------+ +----+ +-----+ +----+ +-----+ 180 |Source Address| |Egress Nodes | | | | | 181 +--------------+ +--------------+ +----------+ +------+ +------+ +------+ 182 |VPN Info | | relate |Cisco Mode| | BIER | | ISIS | | BGP | 183 +--------------+ \|/ +----------+ +------+ +------+ +------+ 184 |VNI Info | +----------------+ 185 +--------------+ | BIER Nodes Info| 186 +----------------+ 187 | BFR-ID | 188 +----------------+ 190 Figure 2: UML Class Diagram for Multicast Info Model 192 4. Model Structure 194 module: ietf-multicast-information 195 +--rw multicast-information 196 +--rw multicast-info* [vpn-id source-address source-wildcard group-address group-wildcard vni-type vni-value] 197 +--rw vpn-id uint32 198 +--rw source-address inet:ip-address 199 +--rw source-wildcard uint8 200 +--rw group-address inet:ip-address 201 +--rw group-wildcard uint8 202 +--rw vni-type virtual-type 203 +--rw vni-value uint32 204 +--rw multicast-overlay 205 | +--rw nodes-information 206 | | +--rw ingress-node? inet:ip-address 207 | | +--rw egress-nodes* [number] 208 | | +--rw number uint32 209 | | +--rw egress-node? inet:ip-address 210 | +--rw bier-information 211 | | +--rw sub-domain? sub-domain-id 212 | | +--rw ingress-node? bfr-id 213 | | +--rw egress-nodes* [number] 214 | | +--rw number uint32 215 | | +--rw egress-node? bfr-id 216 | +--rw overlay-technology 217 | +--rw (overlay-tech-type)? 218 | +--:(mld) 219 | +--:(mvpn) 220 +--rw multicast-transport 221 | +--rw bier 222 | | +--rw sub-domain? sub-domain-id 223 | | +--rw (encap-type)? 224 | | | +--:(mpls) 225 | | | +--:(non-mpls) 226 | | | +--:(ipv6) 227 | | +--rw bitstringlength? uint16 228 | | +--rw set-identifier? si 229 | | +--rw ecmp? boolean 230 | | +--rw frr? boolean 231 | +--rw cisco-mode 232 | | +--rw p-group? inet:ip-address 233 | | +--rw graceful-restart? boolean 234 | | +--rw bfd? boolean 235 | +--rw mpls 236 | | +--rw (mpls-tunnel-type)? 237 | | +--:(mldp) 238 | | | +--rw mldp-tunnel-id? uint32 239 | | | +--rw mldp-frr? boolean 240 | | | +--rw mldp-backup-tunnel? boolean 241 | | +--:(p2mp-te) 242 | | +--rw te-tunnel-id? uint32 243 | | +--rw te-frr? boolean 244 | | +--rw te-backup-tunnel? boolean 245 | +--rw pim 246 | +--rw graceful-restart? boolean 247 | +--rw bfd? boolean 248 +--rw multicast-underlay 249 +--rw underlay-requirement? boolean 250 +--rw bgp 251 +--rw ospf 252 | +--rw topology-id? uint16 253 +--rw isis 254 | +--rw topology-id? uint16 255 +--rw babel 256 +--rw pim 258 5. Multicast Information Model 260 file "ietf-multicast-information.yang" 261 module ietf-multicast-information { 263 namespace "urn:ietf:params:xml:ns:yang:ietf-multicast-information"; 265 prefix multicast-info; 267 import ietf-inet-types { 268 prefix "inet"; 269 } 271 organization " IETF MBONED( MBONE Deployment ) Working Group"; 272 contact 273 "WG List: 274 WG Chair: Greg Shepherd 275 276 WG Chair: Leonard Giuliano 277 279 Editor: Zheng Zhang 280 281 Editor: Cui Wang 282 283 Editor: Stig Venaas 284 285 "; 287 description 288 "This module contains a collection of YANG definitions for 289 managing multicast information."; 291 revision 2016-12-08 { 292 description 293 "Initial version."; 294 reference "https://tools.ietf.org/html/draft-zhang-mboned-multicast-info-model"; 295 } 296 /*feature*/ 297 grouping general-multicast { 298 description "The general multicast address information."; 299 leaf source-address { 300 type inet:ip-address; 301 description "The address of multicast source. The value set to zero 302 means that the receiver interests in all source that relevant to 303 one group."; 304 } 305 leaf source-wildcard { 306 type uint8; 307 description "The wildcard information of source."; 308 } 309 leaf group-address { 310 type inet:ip-address; 311 description "The address of multicast group."; 312 } 313 leaf group-wildcard { 314 type uint8; 315 description "The wildcard information of group."; 316 } 317 } 319 grouping m-addr { 320 description "The vpn multicast information."; 321 leaf vpn-id { 322 type uint32; 323 description "The vpn-id of the multicast flow. 324 If there is global instance, the vpnid value should be zero."; 325 } 326 uses general-multicast; 327 } 329 typedef virtual-type { 330 type enumeration { 331 enum "vxlan" { 332 description "The vxlan type."; 333 } 334 enum "virtual subnet" { 335 description "The nvgre type"; 336 } 337 enum "vni" { 338 description "The geneve type"; 339 } 340 } 341 description "The collection of virtual network type."; 342 } 344 grouping multicast-nvo3 { 345 description "The nvo3 multicast information."; 346 leaf vni-type { 347 type virtual-type; 348 description "The type of virtual network identifier. Include the Vxlan 349 NVGRE and Geneve."; 350 } 351 leaf vni-value { 352 type uint32; 353 description "The value of Vxlan network identifier, virtual subnet ID 354 or virtual net identifier."; 355 } 356 } 358 grouping multicast-feature { 359 description 360 "This group describe the different multicast information 361 in various deployments."; 362 uses m-addr; 363 uses multicast-nvo3; 364 } 366 grouping ip-node { 367 description "The IP information of multicast nodes."; 368 leaf ingress-node { 369 type inet:ip-address; 370 description "The ingress node of multicast flow. Or the ingress 371 node of MVPN and BIER. In MVPN, this is the address of ingress 372 PE; in BIER, this is the BFR-prefix of ingress nodes."; 373 } 375 list egress-nodes { 376 key "number"; 377 description "This ID information of one adjacency."; 378 leaf number { 379 type uint32; 380 description "The number of egress nodes."; 381 } 382 leaf egress-node { 383 type inet:ip-address; 384 description 385 "The egress multicast nodes of multicast flow. 386 Or the egress node of MVPN and BIER. In MVPN, this is the 387 address of egress PE; in BIER, this is the BFR-prefix of 388 ingress nodes."; 389 } 390 } 391 } 392 /* should import from BIER yang */ 393 typedef bfr-id { 394 type uint16; 395 description "The BFR id of nodes."; 396 } 398 typedef si { 399 type uint16; 400 description 401 "The type for set identifier"; 403 } 405 typedef sub-domain-id { 406 type uint16; 407 description 408 "The type for sub-domain-id"; 409 } 411 typedef bit-string { 412 type uint16; 413 description 414 "The bit mask of one bitstring."; 415 } 417 grouping bier-node { 418 description "The BIER information of multicast nodes."; 419 leaf sub-domain { 420 type sub-domain-id; 421 description "The sub-domain that this multicast flow belongs to."; 422 } 423 leaf ingress-node { 424 type bfr-id; 425 description "The ingress node of multicast flow. This is the 426 BFR-id of ingress nodes."; 427 } 428 list egress-nodes { 429 key "number"; 430 description "This ID information of one adjacency."; 431 leaf number { 432 type uint32; 433 description "The number of egress nodes."; 434 } 435 leaf egress-node { 436 type bfr-id; 437 description 438 "The egress multicast nodes of multicast flow. 439 This is the BFR-id of egress nodes."; 440 } 441 } 442 } 444 grouping overlay-tech { 445 description "The possible overlay technologies for multicast service."; 446 choice overlay-tech-type { 447 case mld { 448 description "MLD technology is used for multicast overlay"; 449 } 450 case mvpn { 451 description "MVPN technology is used for multicast overlay"; 452 } 453 description "The collection of multicast overlay technology"; 454 } 455 } 457 grouping multicast-overlay { 458 description "The node information that connect the ingress multicast 459 flow, and the nodes information that connect the egress multicast 460 flow."; 462 container nodes-information { 463 description "The ingress and egress nodes information."; 464 uses ip-node; 465 } 466 container bier-information { 467 description "The ingress and egress BIER nodes information."; 468 uses bier-node; 469 } 470 container overlay-technology { 471 description "The possible overlay technologies for multicast service."; 472 uses overlay-tech; 473 } 474 } 476 /*transport*/ 478 grouping transport-bier { 479 description "The BIER transport information."; 480 leaf sub-domain { 481 type sub-domain-id; 482 description "The subdomain id that this multicast flow belongs to."; 483 } 484 choice encap-type { 485 case mpls { 486 description "The BIER forwarding depend on mpls."; 487 } 488 case non-mpls { 489 description "The BIER forwarding depend on non-mpls."; 490 } 491 case ipv6 { 492 description "The BIER forwarding depend on IPv6."; 493 } 494 description "The encapsulation type in BIER."; 495 } 496 leaf bitstringlength { 497 type uint16; 498 description "The bitstringlength used by BIER forwarding."; 499 } 500 leaf set-identifier { 501 type si; 502 description "The set identifier used by this multicast flow, especially in BIER TE."; 503 } 504 leaf ecmp { 505 type boolean; 506 description "The capability of ECMP."; 507 } 508 leaf frr { 509 type boolean; 510 description "The capability of fast re-route."; 511 } 512 } 514 grouping transport-pim { 515 description "The requirement information of pim transportion."; 516 leaf graceful-restart { 517 type boolean; 518 description "If the graceful restart function should be supported."; 519 } 520 leaf bfd { 521 type boolean; 522 description "If the bfd function should be supported."; 523 } 524 } 526 grouping mldp-tunnel-feature { 527 description "The tunnel feature."; 528 leaf mldp-tunnel-id { 529 type uint32; 530 description "The tunnel id that correspond this flow."; 531 } 532 leaf mldp-frr { 533 type boolean; 534 description "If the fast re-route function should be supported."; 535 } 536 leaf mldp-backup-tunnel { 537 type boolean; 538 description "If the backup tunnel function should be supported."; 539 } 540 } 542 grouping p2mp-te-tunnel-feature { 543 description "The tunnel feature."; 544 leaf te-tunnel-id { 545 type uint32; 546 description "The tunnel id that correspond this flow."; 547 } 548 leaf te-frr { 549 type boolean; 550 description "If the fast re-route function should be supported."; 551 } 552 leaf te-backup-tunnel { 553 type boolean; 554 description "If the backup tunnel function should be supported."; 555 } 556 } 558 grouping transport-mpls { 559 description "The mpls transportion information."; 560 choice mpls-tunnel-type { 561 case mldp { 562 uses mldp-tunnel-feature; 563 description "The mldp tunnel."; 564 } 565 case p2mp-te { 566 uses p2mp-te-tunnel-feature; 567 description "The p2mp te tunnel."; 568 } 569 description "The collection types of mpls tunnels"; 570 } 571 } 573 grouping cisco-multicast { 574 description "The Cisco MDT multicast information in RFC6037."; 575 leaf p-group { 576 type inet:ip-address; 577 description "The address of p-group."; 578 } 579 } 581 grouping transport-cisco-mode { 582 description "The transport information of Cisco mode, RFC6037."; 583 uses cisco-multicast; 584 uses transport-pim; 585 } 587 grouping multicast-transport { 588 description "The transport information of multicast service."; 589 container bier { 590 uses transport-bier; 591 description "The transport technology is BIER."; 592 } 593 container cisco-mode { 594 uses transport-cisco-mode; 595 description "The transport technology is cisco-mode."; 596 } 597 container mpls { 598 uses transport-mpls; 599 description "The transport technology is mpls."; 600 } 601 container pim { 602 uses transport-pim; 603 description "The transport technology is PIM."; 604 } 605 } 607 /*underlay*/ 608 grouping underlay-bgp { 609 description "Underlay information of BGP."; 610 } 612 grouping underlay-ospf { 613 description "Underlay information of OSPF."; 614 leaf topology-id { 615 type uint16; 616 description "The topology id of ospf instance."; 617 } 618 } 620 grouping underlay-isis { 621 description "Underlay information of ISIS."; 622 leaf topology-id { 623 type uint16; 624 description "The topology id of isis instance."; 625 } 626 } 628 grouping underlay-babel { 629 description "Underlay information of Babel."; 630 /* If there are some necessary information should be defined? */ 631 } 633 grouping underlay-pim { 634 description "Underlay information of PIM."; 635 /* If there are some necessary information should be defined? */ 636 } 638 grouping multicast-underlay { 639 description "The underlay information relevant multicast service."; 640 leaf underlay-requirement { 641 type boolean; 642 description "If the underlay technology should be required."; 643 } 644 container bgp { 645 uses underlay-bgp; 646 description "The underlay technology is BGP."; 647 } 648 container ospf { 649 uses underlay-ospf; 650 description "The underlay technology is OSPF."; 651 } 652 container isis { 653 uses underlay-isis; 654 description "The underlay technology is ISIS."; 655 } 656 container babel { 657 uses underlay-babel; 658 description "The underlay technology is Babel."; 659 } 660 container pim { 661 uses underlay-pim; 662 description "The underlay technology is PIM."; 663 } 664 } 666 container multicast-information { 667 description "The model of multicast service. Include overlay, transport and underlay."; 669 list multicast-info{ 670 key "vpn-id source-address source-wildcard group-address group-wildcard vni-type vni-value"; 671 uses multicast-feature; 672 description "The detail multicast information."; 674 container multicast-overlay { 675 description "The overlay information of multicast service."; 676 uses multicast-overlay; 677 } 678 container multicast-transport { 679 description "The transportion of multicast service."; 680 uses multicast-transport; 681 } 682 container multicast-underlay { 683 description "The underlay of multicast service."; 684 uses multicast-underlay; 685 } 686 } 687 } 688 } 689 690 6. Notifications 692 TBD. 694 7. Normative References 696 [I-D.ietf-bier-architecture] 697 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 698 S. Aldrin, "Multicast using Bit Index Explicit 699 Replication", draft-ietf-bier-architecture-05 (work in 700 progress), October 2016. 702 [I-D.ietf-bier-bier-yang] 703 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 704 and M. Sivakumar, "YANG Data Model for BIER Protocol", 705 draft-ietf-bier-bier-yang-01 (work in progress), January 706 2017. 708 [I-D.ietf-pim-yang] 709 Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, 710 Y., and f. hu, "A YANG data model for Protocol-Independent 711 Multicast (PIM)", draft-ietf-pim-yang-05 (work in 712 progress), February 2017. 714 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 715 the Network Configuration Protocol (NETCONF)", RFC 6020, 716 DOI 10.17487/RFC6020, October 2010, 717 . 719 [RFC6037] Rosen, E., Ed., Cai, Y., Ed., and IJ. Wijnands, "Cisco 720 Systems' Solution for Multicast in BGP/MPLS IP VPNs", 721 RFC 6037, DOI 10.17487/RFC6037, October 2010, 722 . 724 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 725 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 726 January 2011, . 728 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 729 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 730 2012, . 732 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 733 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 734 . 736 Authors' Addresses 738 Zheng Zhang 739 ZTE Corporation 740 No. 50 Software Ave, Yuhuatai Distinct 741 Nanjing 742 China 744 Email: zhang.zheng@zte.com.cn 746 Cui(Linda) Wang 747 ZTE Corporation 748 No. 50 Software Ave, Yuhuatai Distinct 749 Nanjing 750 China 752 Email: lindawangjoy@gmail.com 754 Stig Venaas 755 Cisco Systems, Inc. 756 Tasman Drive 757 San Jose CA 95134 758 USA 760 Email: stig@cisco.com