idnits 2.17.1 draft-zhang-mboned-multicast-info-model-02.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 60 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 == Line 220 has weird spacing: '...ss-node ine...' == Line 225 has weird spacing: '...ss-node bfr...' -- The document date (August 21, 2017) is 2441 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 772, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-bier-bier-yang' is defined on line 778, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-yang' is defined on line 784, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 790, but no explicit reference was found in the text == Unused Reference: 'RFC6037' is defined on line 795, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 800, but no explicit reference was found in the text == Unused Reference: 'RFC6513' is defined on line 804, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 808, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-07 == Outdated reference: A later version (-08) exists of draft-ietf-bier-bier-yang-02 == Outdated reference: A later version (-17) exists of draft-ietf-pim-yang-08 ** 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 (~~), 14 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: February 22, 2018 Ying. Cheng 6 China Unicom 7 August 21, 2017 9 Multicast Model 10 draft-zhang-mboned-multicast-info-model-02 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 February 22, 2018. 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 . . . . . . . . . . . . . . . . . . . . . . . . 17 65 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 66 8. Normative References . . . . . . . . . . . . . . . . . . . . 17 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 69 1. Introduction 71 Currently, there are many multicast YANG models, such as PIM, MLD, 72 and BIER and so on. But all these models are distributed in 73 different working groups as separate files and focus on the protocol 74 itself. Furthermore, they cannot describe a high-level multicast 75 service required by network operators. 77 This document intents to provide a general and all-round multicast 78 model, which tries to stand at a high level to take full advantages 79 of these aforementioned models to control the multicast network, and 80 guides the deployment of multicast service. 82 This multicast information model is mainly used by the management 83 tools run by the network operators in order to manage, monitor and 84 debug the network resources used to deliver multicast service, as 85 well as gathering some data from the network. 87 +------------------------+ 88 | Multicast Info | 89 +------------------------+ 90 | | | 91 | | | 92 | +---------+ +----------+ 93 | | EMS/NMS | |Controller| 94 | +---------+ +----------+ 95 | | | 96 | | | 97 +------------------------------------------------+ 98 | Network Element1.....N | 99 +------------------------------------------------+ 101 Figure 1: Example usage of Multicast Model 103 Detailly,in figure 1, there is an example of usage of this multicast 104 model. Network operators can input this model to a controller who is 105 responsible to translate the information and invoke the corresponding 106 protocol models into configurations to configure the network elements 107 through NETCONF/RESTCONF/CLI. Or network operators can input this 108 model to the EMS/NMS to manage the network elements or configure the 109 network elements directly. On the other hand, when the network 110 elements detect failure or some other changes, the network operators 111 can collect these kind of notifications through this model to assist 112 locating the exact failure and responsing immediatly. for example, 113 when the network element suffers a failure of one MVPN neighbor, it 114 can notify to the EMS/NMS or Controller or to other Multicast Model 115 management tool directly to let the network operator take actions 116 immediately. 118 Specifically, in section 3, it provides a human readability of the 119 whole multicast network through UML class diagram, which frames 120 different multicast components and correlates them in a readable 121 fashion. Then, based on this UML class diagram, there is 122 instantiated and detailed YANG model in Section 5. 124 In other words, this document does not define any specific protocol 125 model, instead, it depends on many existed multicast protocol models 126 and relates several multicast information together to fulfill 127 multicast service. 129 2. Design of the multicast model 131 This model includes three layers: the multicast overlay, the 132 transport layer and the multicast underlay information. 134 Multicast overlay defines the features of multicast flow, such 135 as(vpnid, multicast source and multicast group) information, and 136 (ingress-node,egress-nodes) nodes information. If the transport 137 layer is BIER, there may define BIER information including 138 (Subdomain, ingress-node BFR-id, egress-nodes BFR-id). In data 139 center network, for fine-grained to gather the nodes belonging to the 140 same virtual network, there may need VNI-related information to 141 assist. If no (ingress-node, egress-nodes) information are defined 142 directly, there may need overlay multicast signaling technology, such 143 as MLD or MVPN, to collect these nodes information. 145 Multicast transport layer defines the type of transport technologies 146 that can be used to forward multicast flow, including BIER forwarding 147 type, MPLS forwarding type, or PIM forwarding type and so on. One or 148 several transport technologies could be defined at the same time. As 149 for the detailed parameters for each transport technology, this 150 multicast information model can invoke the corresponding protocol 151 model to define them. 153 Multicast underlay defines the type of underlay technologies, such as 154 OSPF, ISIS, BGP, PIM or BABEL and so on. One or several underlay 155 technologies could be defined at the same time. As for the specific 156 parameters for each underlay technology, this multicast information 157 model can depend the corresponding protocol model to configure them 158 as well. 160 3. UML Class Diagram for Multicast Info Model 162 The following is a UML diagram for Multicast Info Model. 164 +----------------+ 165 | Multicast Info | 166 +----------------+ 167 | | |Contain 168 +---------------------------+ | +---------------------------+ 169 | | | 170 +-------------------+ +---------------------+ +--------------------+ 171 | Multicast Overlay | | Multicast Transport | | Multicast Underlay | 172 +-------------------+ +---------------------+ +--------------------+ 173 | | |Contain | | | | | invoke | | | | | invoke 174 +--------+ | +-------+ +----+ | | | +----+ +----+ | | | +----+ 175 | | | | | | | | | | | | | 176 +--------------+ | +--------------+ +-----+ | | | +------+ +------+ | | | +------+ 177 | Multi-Info | | | Ing/Eg Nodes | | PIM | | | | | MPLS | | OSPF | | | | | PIM | 178 +--------------+ | +--------------+ +-----+ | | | +------+ +------+ | | | +------+ 179 |Group Address | | |Ingress Nodes | +----+ | +-----+ +----+ | +-----+ 180 +--------------+ | +--------------+ | | | | | | 181 |Source Address| | |Egress Nodes | +----------+ | +--------+ +-----+ | +------+ 182 +--------------+ | +--------------+ |Cisco Mode| | |BIER-TE | |BABEL| | | BGP | 183 |VPN Info | | | relate +----------+ | +--------+ +-----+ | +------+ 184 +--------------+ | \|/ +----+ +----+ 185 |VNI Info | | +----------------+ | | 186 +--------------+ | | BIER Nodes Info| +------+ +------+ 187 | +----------------+ | BIER | | ISIS | 188 +--------+ | BFR-ID | +------+ +------+ 189 | +----------------+ 190 +--------------+ 191 | Overlay Tech | 192 +--------------+ 193 | MLD | 194 +--------------+ 195 | MVPN | 196 +--------------+ 197 | BGP | 198 +--------------+ 199 | MLD-Snooping | 200 +--------------+ 202 Figure 2: UML Class Diagram for Multicast Info Model 204 4. Model Structure 206 module: ietf-multicast-information 207 +--rw multicast-information 208 +--rw multicast-info* [vpn-id source-address source-wildcard group-address group-wildcard vni-type vni-value] 209 +--rw vpn-id uint32 210 +--rw source-address inet:ip-address 211 +--rw source-wildcard uint8 212 +--rw group-address inet:ip-address 213 +--rw group-wildcard uint8 214 +--rw vni-type virtual-type 215 +--rw vni-value uint32 216 +--rw multicast-overlay 217 | +--rw nodes-information 218 | | +--rw ingress-node? inet:ip-address 219 | | +--rw egress-nodes* [egress-node] 220 | | +--rw egress-node inet:ip-address 221 | +--rw bier-information 222 | | +--rw sub-domain? sub-domain-id 223 | | +--rw ingress-node? bfr-id 224 | | +--rw egress-nodes* [egress-node] 225 | | +--rw egress-node bfr-id 226 | +--rw overlay-technology 227 | +--rw (overlay-tech-type)? 228 | +--:(mld) 229 | +--:(mvpn) 230 | +--:(bgp) 231 | +--:(mld-snooping) 232 +--rw multicast-transport 233 | +--rw bier 234 | | +--rw sub-domain? sub-domain-id 235 | | +--rw (encap-type)? 236 | | | +--:(mpls) 237 | | | +--:(non-mpls) 238 | | | +--:(ipv6) 239 | | +--rw bitstringlength? uint16 240 | | +--rw set-identifier? si 241 | | +--rw ecmp? boolean 242 | | +--rw frr? boolean 243 | +--rw bier-te 244 | | +--rw sub-domain? sub-domain-id 245 | | +--rw (encap-type)? 246 | | | +--:(mpls) 247 | | | +--:(non-mpls) 248 | | +--rw bitstringlength? uint16 249 | | +--rw set-identifier? si 250 | | +--rw ecmp? boolean 251 | | +--rw frr? boolean 252 | +--rw cisco-mode 253 | | +--rw p-group? inet:ip-address 254 | | +--rw graceful-restart? boolean 255 | | +--rw bfd? boolean 256 | +--rw mpls 257 | | +--rw (mpls-tunnel-type)? 258 | | +--:(mldp) 259 | | | +--rw mldp-tunnel-id? uint32 260 | | | +--rw mldp-frr? boolean 261 | | | +--rw mldp-backup-tunnel? boolean 262 | | +--:(p2mp-te) 263 | | +--rw te-tunnel-id? uint32 264 | | +--rw te-frr? boolean 265 | | +--rw te-backup-tunnel? boolean 266 | +--rw pim 267 | +--rw graceful-restart? boolean 268 | +--rw bfd? boolean 269 +--rw multicast-underlay 270 +--rw underlay-requirement? boolean 271 +--rw bgp 272 +--rw ospf 273 | +--rw topology-id? uint16 274 +--rw isis 275 | +--rw topology-id? uint16 276 +--rw babel 277 +--rw pim 279 5. Multicast Information Model 281 file "ietf-multicast-information.yang" 282 module ietf-multicast-information { 284 namespace "urn:ietf:params:xml:ns:yang:ietf-multicast-information"; 286 prefix multicast-info; 288 import ietf-inet-types { 289 prefix "inet"; 290 } 292 organization " IETF MBONED( MBONE Deployment ) Working Group"; 293 contact 294 "WG List: 295 WG Chair: Greg Shepherd 296 297 WG Chair: Leonard Giuliano 298 300 Editor: Zheng Zhang 301 302 Editor: Cui Wang 303 304 Editor: Ying Cheng 305 306 "; 308 description 309 "This module contains a collection of YANG definitions for 310 managing multicast information."; 312 revision 2017-08-20 { 313 description 314 "Add BGP and MLD-snooping overlay and BIER-TE transport."; 315 reference "https://tools.ietf.org/html/draft-zhang-mboned-multicast-info-model"; 316 } 318 revision 2016-12-08 { 319 description 320 "Initial version."; 321 reference "https://tools.ietf.org/html/draft-zhang-mboned-multicast-info-model"; 322 } 323 /*feature*/ 324 grouping general-multicast { 325 description "The general multicast address information."; 326 leaf source-address { 327 type inet:ip-address; 328 description "The address of multicast source. The value set to zero 329 means that the receiver interests in all source that relevant to 330 one group."; 331 } 332 leaf source-wildcard { 333 type uint8; 334 description "The wildcard information of source."; 335 } 336 leaf group-address { 337 type inet:ip-address; 338 description "The address of multicast group."; 339 } 340 leaf group-wildcard { 341 type uint8; 342 description "The wildcard information of group."; 343 } 344 } 346 grouping m-addr { 347 description "The vpn multicast information."; 348 leaf vpn-id { 349 type uint32; 350 description "The vpn-id of the multicast flow. 351 If there is global instance, the vpnid value should be zero."; 352 } 353 uses general-multicast; 354 } 355 typedef virtual-type { 356 type enumeration { 357 enum "vxlan" { 358 description "The vxlan type."; 359 } 360 enum "virtual subnet" { 361 description "The nvgre type"; 362 } 363 enum "vni" { 364 description "The geneve type"; 365 } 366 } 367 description "The collection of virtual network type."; 368 } 370 grouping multicast-nvo3 { 371 description "The nvo3 multicast information."; 372 leaf vni-type { 373 type virtual-type; 374 description "The type of virtual network identifier. Include the Vxlan 375 NVGRE and Geneve."; 376 } 377 leaf vni-value { 378 type uint32; 379 description "The value of Vxlan network identifier, virtual subnet ID 380 or virtual net identifier."; 381 } 382 } 384 grouping multicast-feature { 385 description 386 "This group describe the different multicast information 387 in various deployments."; 388 uses m-addr; 389 uses multicast-nvo3; 390 } 392 grouping ip-node { 393 description "The IP information of multicast nodes."; 394 leaf ingress-node { 395 type inet:ip-address; 396 description "The ingress node of multicast flow. Or the ingress 397 node of MVPN and BIER. In MVPN, this is the address of ingress 398 PE; in BIER, this is the BFR-prefix of ingress nodes."; 399 } 401 list egress-nodes { 402 key "egress-node"; 403 description "This ID information of one adjacency."; 405 leaf egress-node { 406 type inet:ip-address; 407 description 408 "The egress multicast nodes of multicast flow. 409 Or the egress node of MVPN and BIER. In MVPN, this is the 410 address of egress PE; in BIER, this is the BFR-prefix of 411 ingress nodes."; 412 } 413 } 414 } 415 /* should import from BIER yang */ 416 typedef bfr-id { 417 type uint16; 418 description "The BFR id of nodes."; 419 } 421 typedef si { 422 type uint16; 423 description 424 "The type for set identifier"; 425 } 427 typedef sub-domain-id { 428 type uint16; 429 description 430 "The type for sub-domain-id"; 431 } 433 typedef bit-string { 434 type uint16; 435 description 436 "The bit mask of one bitstring."; 437 } 439 grouping bier-node { 440 description "The BIER information of multicast nodes."; 441 leaf sub-domain { 442 type sub-domain-id; 443 description "The sub-domain that this multicast flow belongs to."; 444 } 445 leaf ingress-node { 446 type bfr-id; 447 description "The ingress node of multicast flow. This is the 448 BFR-id of ingress nodes."; 449 } 450 list egress-nodes { 451 key "egress-node"; 452 description "This ID information of one adjacency."; 454 leaf egress-node { 455 type bfr-id; 456 description 457 "The egress multicast nodes of multicast flow. 458 This is the BFR-id of egress nodes."; 459 } 460 } 461 } 463 grouping overlay-tech { 464 description "The possible overlay technologies for multicast service."; 465 choice overlay-tech-type { 466 case mld { 467 description "MLD technology is used for multicast overlay"; 468 } 469 case mvpn { 470 description "MVPN technology is used for multicast overlay"; 471 } 472 case bgp { 473 description "BGP technology is used for multicast overlay"; 474 } 475 case mld-snooping { 476 description "MLD snooping technology is used for multicast overlay"; 477 } 478 description "The collection of multicast overlay technology"; 479 } 480 } 482 grouping multicast-overlay { 483 description "The node information that connect the ingress multicast 484 flow, and the nodes information that connect the egress multicast 485 flow."; 486 /*uses multicast-feature;*/ 487 container nodes-information { 488 description "The ingress and egress nodes information."; 489 uses ip-node; 490 } 491 container bier-information { 492 description "The ingress and egress BIER nodes information."; 493 uses bier-node; 494 } 495 container overlay-technology { 496 description "The possible overlay technologies for multicast service."; 497 uses overlay-tech; 498 } 500 } 502 /*transport*/ 504 grouping transport-bier { 505 description "The BIER transport information."; 506 leaf sub-domain { 507 type sub-domain-id; 508 description "The subdomain id that this multicast flow belongs to."; 509 } 510 choice encap-type { 511 case mpls { 512 description "The BIER forwarding depend on mpls."; 513 } 514 case non-mpls { 515 description "The BIER forwarding depend on non-mpls."; 516 } 517 case ipv6 { 518 description "The BIER forwarding depend on IPv6."; 519 } 520 description "The encapsulation type in BIER."; 521 } 522 leaf bitstringlength { 523 type uint16; 524 description "The bitstringlength used by BIER forwarding."; 525 } 526 leaf set-identifier { 527 type si; 528 description "The set identifier used by this multicast flow."; 529 } 530 leaf ecmp { 531 type boolean; 532 description "The capability of ECMP."; 533 } 534 leaf frr { 535 type boolean; 536 description "The capability of fast re-route."; 537 } 538 } 540 grouping transport-bier-te { 541 description "The BIER-TE transport information."; 542 leaf sub-domain { 543 type sub-domain-id; 544 description "The subdomain id that this multicast flow belongs to."; 545 } 546 choice encap-type { 547 case mpls { 548 description "The BIER-TE forwarding depend on mpls."; 549 } 550 case non-mpls { 551 description "The BIER-TE forwarding depend on non-mpls."; 552 } 553 description "The encapsulation type in BIER-TE."; 554 } 555 leaf bitstringlength { 556 type uint16; 557 description "The bitstringlength used by BIER-TE forwarding."; 558 } 559 leaf set-identifier { 560 type si; 561 description "The set identifier used by this multicast flow, especially in BIER TE."; 562 } 563 leaf ecmp { 564 type boolean; 565 description "The capability of ECMP."; 566 } 567 leaf frr { 568 type boolean; 569 description "The capability of fast re-route."; 570 } 571 } 573 grouping transport-pim { 574 description "The requirement information of pim transportion."; 575 leaf graceful-restart { 576 type boolean; 577 description "If the graceful restart function should be supported."; 578 } 579 leaf bfd { 580 type boolean; 581 description "If the bfd function should be supported."; 582 } 583 } 585 grouping mldp-tunnel-feature { 586 description "The tunnel feature."; 587 leaf mldp-tunnel-id { 588 type uint32; 589 description "The tunnel id that correspond this flow."; 590 } 591 leaf mldp-frr { 592 type boolean; 593 description "If the fast re-route function should be supported."; 594 } 595 leaf mldp-backup-tunnel { 596 type boolean; 597 description "If the backup tunnel function should be supported."; 598 } 599 } 601 grouping p2mp-te-tunnel-feature { 602 description "The tunnel feature."; 603 leaf te-tunnel-id { 604 type uint32; 605 description "The tunnel id that correspond this flow."; 606 } 607 leaf te-frr { 608 type boolean; 609 description "If the fast re-route function should be supported."; 610 } 611 leaf te-backup-tunnel { 612 type boolean; 613 description "If the backup tunnel function should be supported."; 614 } 615 } 617 /*typedef sub-domain-id { 618 type uint16; 619 description 620 "The type for sub-domain-id"; 621 }*/ 623 grouping transport-mpls { 624 description "The mpls transportion information."; 625 choice mpls-tunnel-type { 626 case mldp { 627 uses mldp-tunnel-feature; 628 description "The mldp tunnel."; 629 } 630 case p2mp-te { 631 uses p2mp-te-tunnel-feature; 632 description "The p2mp te tunnel."; 633 } 634 description "The collection types of mpls tunnels"; 635 } 636 } 638 grouping cisco-multicast { 639 description "The Cisco MDT multicast information in RFC6037."; 640 leaf p-group { 641 type inet:ip-address; 642 description "The address of p-group."; 644 } 645 } 647 grouping transport-cisco-mode { 648 description "The transport information of Cisco mode, RFC6037."; 649 uses cisco-multicast; 650 uses transport-pim; 651 } 653 grouping multicast-transport { 654 description "The transport information of multicast service."; 655 container bier { 656 uses transport-bier; 657 description "The transport technology is BIER."; 658 } 659 container bier-te { 660 uses transport-bier-te; 661 description "The transport technology is BIER-TE."; 662 } 663 container cisco-mode { 664 uses transport-cisco-mode; 665 description "The transport technology is cisco-mode."; 666 } 667 container mpls { 668 uses transport-mpls; 669 description "The transport technology is mpls."; 670 } 671 container pim { 672 uses transport-pim; 673 description "The transport technology is PIM."; 674 } 675 } 677 /*underlay*/ 678 grouping underlay-bgp { 679 description "Underlay information of BGP."; 680 } 682 grouping underlay-ospf { 683 description "Underlay information of OSPF."; 684 leaf topology-id { 685 type uint16; 686 description "The topology id of ospf instance."; 687 } 688 } 690 grouping underlay-isis { 691 description "Underlay information of ISIS."; 692 leaf topology-id { 693 type uint16; 694 description "The topology id of isis instance."; 695 } 696 } 698 grouping underlay-babel { 699 description "Underlay information of Babel."; 700 /* If there are some necessary information should be defined? */ 701 } 703 grouping underlay-pim { 704 description "Underlay information of PIM."; 705 /* If there are some necessary information should be defined? */ 706 } 708 grouping multicast-underlay { 709 description "The underlay information relevant multicast service."; 710 leaf underlay-requirement { 711 type boolean; 712 description "If the underlay technology should be required."; 713 } 714 container bgp { 715 uses underlay-bgp; 716 description "The underlay technology is BGP."; 717 } 718 container ospf { 719 uses underlay-ospf; 720 description "The underlay technology is OSPF."; 721 } 722 container isis { 723 uses underlay-isis; 724 description "The underlay technology is ISIS."; 725 } 726 container babel { 727 uses underlay-babel; 728 description "The underlay technology is Babel."; 729 } 730 container pim { 731 uses underlay-pim; 732 description "The underlay technology is PIM."; 733 } 734 } 736 container multicast-information { 737 description "The model of multicast service. Include overlay, transport and underlay."; 739 list multicast-info{ 740 key "vpn-id source-address source-wildcard group-address group-wildcard vni-type vni-value"; 741 uses multicast-feature; 742 description "The detail multicast information."; 744 container multicast-overlay { 745 description "The overlay information of multicast service."; 746 uses multicast-overlay; 747 } 748 container multicast-transport { 749 description "The transportion of multicast service."; 750 uses multicast-transport; 751 } 752 container multicast-underlay { 753 description "The underlay of multicast service."; 754 uses multicast-underlay; 755 } 756 } 757 } 758 } 759 761 6. Notifications 763 TBD. 765 7. Acknowledgements 767 The authors would like to thank Stig Venaas, Jake Holland for their 768 valuable comments and suggestions. 770 8. Normative References 772 [I-D.ietf-bier-architecture] 773 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 774 S. Aldrin, "Multicast using Bit Index Explicit 775 Replication", draft-ietf-bier-architecture-07 (work in 776 progress), June 2017. 778 [I-D.ietf-bier-bier-yang] 779 Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., 780 and M. Sivakumar, "YANG Data Model for BIER Protocol", 781 draft-ietf-bier-bier-yang-02 (work in progress), August 782 2017. 784 [I-D.ietf-pim-yang] 785 Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, 786 Y., and f. hu, "A YANG data model for Protocol-Independent 787 Multicast (PIM)", draft-ietf-pim-yang-08 (work in 788 progress), April 2017. 790 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 791 the Network Configuration Protocol (NETCONF)", RFC 6020, 792 DOI 10.17487/RFC6020, October 2010, . 795 [RFC6037] Rosen, E., Ed., Cai, Y., Ed., and IJ. Wijnands, "Cisco 796 Systems' Solution for Multicast in BGP/MPLS IP VPNs", 797 RFC 6037, DOI 10.17487/RFC6037, October 2010, 798 . 800 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 801 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 802 January 2011, . 804 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 805 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 806 2012, . 808 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 809 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 810 . 812 Authors' Addresses 814 Zheng Zhang 815 ZTE Corporation 816 No. 50 Software Ave, Yuhuatai Distinct 817 Nanjing 818 China 820 Email: zhang.zheng@zte.com.cn 822 Cui(Linda) Wang 823 ZTE Corporation 824 No. 50 Software Ave, Yuhuatai Distinct 825 Nanjing 826 China 828 Email: lindawangjoy@gmail.com 829 Ying Cheng 830 China Unicom 831 Beijing 832 China 834 Email: chengying10@chinaunicom.cn