MBONED WG Zheng. Zhang Internet-Draft Cui. Wang Intended status: Standards Track ZTE Corporation Expires: April 30, 2017 October 27, 2016 Multicast Model draft-zhang-mboned-multicast-info-model-00 Abstract This document proposes a general and all-round multicast model, which provides explanations and guidelines for the deployment of multicast service in all kinds of multicast scenarios. The multicast technologies include BIER multicast, PIM multicast, MPLS multicast and so on. And also, there will define several possible RPCs about how to interact between multicast service model and multicast device model. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on April 30, 2017. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Zhang & Wang Expires April 30, 2017 [Page 1] Internet-Draft Multicast Model October 2016 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Design of the multicast model . . . . . . . . . . . . . . . . 2 2.1. Model Structure . . . . . . . . . . . . . . . . . . . . . 3 2.2. Multicast overlay layer . . . . . . . . . . . . . . . . . 4 2.3. Multicast transport layer . . . . . . . . . . . . . . . . 4 2.4. Multicast underlay layer . . . . . . . . . . . . . . . . 4 3. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Multicast Data Model . . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction This document intents to provide a general and all-round multicast model, and guides the deployment of multicast technology. Additionally, this model covers many existed multicast technologies. But this document does not define any specifical and detailed models for multicast protocols, such as PIM, MLD, and BIER and so on. Instead, this document stands on a high level to take advantage of them to implement multicast service. 2. Design of the multicast model This model includes multicast overlay, the transport layer and the possible underlay information. Multicast overlay defines the feature of multicast flow, such as (vpnid, multicast source and multicast group) information, (ingress- node,egress-nodes) nodes information. Additionally, BIER information including (Subdomain,ingress-node BFR-id,egress-nodes BFR-id) is also included to provide BIER multicast service. In data center network, for fine-grained to gather the nodes belonging to the same virtual network, there may need VNI-related information to assist. Multicast transport defines the transport technologies that may be used to forward multicast flow, including BIER forwarding, mpls forwarding or pim forwarding and so on. Multicast underlay defines the possible technologies that may be used to interaction the necessary information, such as OSPF, ISIS, and BGP and so on. Zhang & Wang Expires April 30, 2017 [Page 2] Internet-Draft Multicast Model October 2016 2.1. Model Structure module: ietf-multicast-information +--rw multicast-information +--rw multicast-overlay | +--rw pure-multicast | | +--rw vpn-id? uint32 | | +--rw source-address? inet:ip-address | | +--rw source-wildcard? uint8 | | +--rw group-address? inet:ip-address | | +--rw group-wildcard? uint8 | +--rw nvo3 | | +--rw vni-type? virtual-type | | +--rw vni-value? uint32 | +--rw nodes-information | | +--rw ingress-node? inet:ip-address | | +--rw egress-nodes* [number] | | +--rw number uint32 | | +--rw egress-node? inet:ip-address | +--rw bier-information | | +--rw sub-domain? sub-domain-id | | +--rw ingress-node? bfr-id | | +--rw egress-nodes* [number] | | +--rw number uint32 | | +--rw egress-node? bfr-id | +--rw overlay-technology | +--rw (overlay-tech-type)? | +--:(mld) | +--:(mvpn) +--rw multicast-transport | +--rw bier | | +--rw sub-domain? sub-domain-id | | +--rw (encap-type)? | | | +--:(mpls) | | +--rw bitstringlength? uint16 | | +--rw set-identifier? si | | +--rw ecmp? boolean | | +--rw frr? boolean | +--rw cisco-mode | | +--rw p-group? inet:ip-address | | +--rw graceful-restart? boolean | | +--rw bfd? boolean | +--rw mpls | | +--rw (mpls-tunnel-type)? | | +--:(mldp) | | | +--rw tunnel-id? uint32 | | | +--rw frr? boolean | | | +--rw backup-tunnel? boolean Zhang & Wang Expires April 30, 2017 [Page 3] Internet-Draft Multicast Model October 2016 | | +--:(p2mp-te) | | +--rw tunnel-id? uint32 | | +--rw frr? boolean | | +--rw backup-tunnel? boolean | +--rw pim | +--rw graceful-restart? boolean | +--rw bfd? boolean +--rw multicast-underlay +--rw underlay-requirement? boolean +--rw bgp +--rw ospf | +--rw topology-id? uint16 +--rw isis | +--rw topology-id? uint16 +--rw pim 2.2. Multicast overlay layer This layer defines the feature of multicast service, and the possible overlay protocol may be used. The feature of multicast includes the source and group information. And specific for nvo3, the feature of multicast service may be virtual network identifier. The ingress and egress nodes information include the IP address of nodes and PEs. In BIER scenario, the nodes information may be BFR- ids. The overlay technology, until now, MVPN and MLD are necessary. 2.3. Multicast transport layer BIER is the transport layer technology. MPLS and PIM also are transport layer technologies. The choice of transport layer protocol can be flexible. 2.4. Multicast underlay layer This layer has a tight connection with the underlay protocol. 3. Notifications TBD. 4. Multicast Data Model file "ietf-multicast-service.yang" module ietf-multicast-information { Zhang & Wang Expires April 30, 2017 [Page 4] Internet-Draft Multicast Model October 2016 namespace "urn:ietf:params:xml:ns:yang:ietf-multicast-information"; prefix multicast-info; import ietf-inet-types { prefix "inet"; } organization " IETF MBONED( MBONE Deployment ) Working Group"; contact "WG List: WG Chair: Greg Shepherd WG Chair: Leonard Giuliano Editor: Zheng Zhang Editor: Cui Wang "; description "This module contains a collection of YANG definitions for managing multicast information."; revision 2016-10-28 { description "Initial version."; reference "https://tools.ietf.org/html/draft-zhang-mboned-multicast-info-model"; } /*feature*/ grouping general-multicast { description "The general multicast address information."; leaf source-address { type inet:ip-address; description "The address of multicast source. The value set to zero means that the receiver interests in all source that relevant to one group."; } leaf source-wildcard { type uint8; description "The wildcard information of source."; } leaf group-address { type inet:ip-address; description "The address of multicast group."; } Zhang & Wang Expires April 30, 2017 [Page 5] Internet-Draft Multicast Model October 2016 leaf group-wildcard { type uint8; description "The wildcard information of group."; } } grouping m-addr { description "The vpn multicast information."; leaf vpn-id { type uint32; description "The vpn-id of the multicast flow. If there is global instance, the vpnid value should be zero."; } uses general-multicast; } typedef virtual-type { type enumeration { enum "vxlan" { description "The vxlan type."; } enum "virtual subnet" { description "The nvgre type"; } enum "vni" { description "The geneve type"; } } description "The collection of virtual network type."; } grouping multicast-nvo3 { description "The nvo3 multicast information."; leaf vni-type { type virtual-type; description "The type of virtual network identifier. Include the Vxlan NVGRE and Geneve."; } leaf vni-value { type uint32; description "The value of Vxlan network identifier, virtual subnet ID or virtual net identifier."; } } grouping multicast-feature { description "This group describe the different multicast information Zhang & Wang Expires April 30, 2017 [Page 6] Internet-Draft Multicast Model October 2016 in various deployments."; container pure-multicast { uses m-addr; description "The ordinary multicast information of source and group."; } container nvo3 { uses multicast-nvo3; description "The virtual network information"; } } grouping ip-node { description "The IP information of multicast nodes."; leaf ingress-node { type inet:ip-address; description "The ingress node of multicast flow. Or the ingress node of MVPN and BIER. In MVPN, this is the address of ingress PE; in BIER, this is the BFR-prefix of ingress nodes."; } list egress-nodes { key "number"; description "This ID information of one adjacency."; leaf number { type uint32; description "The number of egress nodes."; } leaf egress-node { type inet:ip-address; description "The egress multicast nodes of multicast flow. Or the egress node of MVPN and BIER. In MVPN, this is the address of egress PE; in BIER, this is the BFR-prefix of ingress nodes."; } } } /* should import from BIER yang */ typedef bfr-id { type uint16; description "The BFR id of nodes."; } typedef si { type uint16; description "The type for set identifier"; } Zhang & Wang Expires April 30, 2017 [Page 7] Internet-Draft Multicast Model October 2016 typedef sub-domain-id { type uint16; description "The type for sub-domain-id"; } typedef bit-string { type uint16; description "The bit mask of one bitstring."; } grouping bier-node { description "The BIER information of multicast nodes."; leaf sub-domain { type sub-domain-id; description "The sub-domain that this multicast flow belongs to."; } leaf ingress-node { type bfr-id; description "The ingress node of multicast flow. This is the BFR-id of ingress nodes."; } list egress-nodes { key "number"; description "This ID information of one adjacency."; leaf number { type uint32; description "The number of egress nodes."; } leaf egress-node { type bfr-id; description "The egress multicast nodes of multicast flow. This is the BFR-id of egress nodes."; } } } grouping overlay-tech { description "The possible overlay technologies for multicast service."; choice overlay-tech-type { case mld { description "MLD technology is used for multicast overlay"; } case mvpn { description "MVPN technology is used for multicast overlay"; } Zhang & Wang Expires April 30, 2017 [Page 8] Internet-Draft Multicast Model October 2016 description "The collection of multicast overlay technology"; } } grouping multicast-overlay { description "The node information that connect the ingress multicast flow, and the nodes information that connect the egress multicast flow."; uses multicast-feature; container nodes-information { description "The ingress and egress nodes information."; uses ip-node; } container bier-information { description "The ingress and egress BIER nodes information."; uses bier-node; } container overlay-technology { description "The possible overlay technologies for multicast service."; uses overlay-tech; } } /*transport*/ typedef bier-encap-type { type enumeration { enum "mpls" { description "The mpls forwarding function is used in BIER."; } } description "The encapsulation type of BIER transportion."; } grouping transport-bier { description "The BIER transport information."; leaf sub-domain { type sub-domain-id; description "The subdomain id that this multicast flow belongs to."; } choice encap-type { case mpls { description "The BIER forwarding depend on mpls."; } description "The encapsulation type in BIER."; } leaf bitstringlength { type uint16; Zhang & Wang Expires April 30, 2017 [Page 9] Internet-Draft Multicast Model October 2016 description "The bitstringlength used by BIER forwarding."; } leaf set-identifier { type si; description "The set identifier used by this multicast flow, especially in BIER TE."; } leaf ecmp { type boolean; description "The capability of ECMP."; } leaf frr { type boolean; description "The capability of fast re-route."; } } grouping transport-pim { description "The requirement information of pim transportion."; leaf graceful-restart { type boolean; description "If the graceful restart function should be supported."; } leaf bfd { type boolean; description "If the bfd function should be supported."; } } grouping tunnel-feature { description "The tunnel feature."; leaf tunnel-id { type uint32; description "The tunnel id that correspond this flow."; } leaf frr { type boolean; description "If the fast re-route function should be supported."; } leaf backup-tunnel { type boolean; description "If the backup tunnel function should be supported."; } } grouping transport-mpls { description "The mpls transportion information."; choice mpls-tunnel-type { case mldp { Zhang & Wang Expires April 30, 2017 [Page 10] Internet-Draft Multicast Model October 2016 uses tunnel-feature; description "The mldp tunnel."; } case p2mp-te { uses tunnel-feature; description "The p2mp te tunnel."; } description "The collection types of mpls tunnels"; } } grouping cisco-multicast { description "The Cisco MDT multicast information in RFC6037."; leaf p-group { type inet:ip-address; description "The address of p-group."; } } grouping transport-cisco-mode { description "The transport information of Cisco mode, RFC6037."; uses cisco-multicast; uses transport-pim; } grouping multicast-transport { description "The transport information of multicast service."; container bier { uses transport-bier; description "The transport technology is BIER."; } container cisco-mode { uses transport-cisco-mode; description "The transport technology is cisco-mode."; } container mpls { uses transport-mpls; description "The transport technology is mpls."; } container pim { uses transport-pim; description "The transport technology is PIM."; } } /*underlay*/ grouping underlay-bgp { description "Underlay information of BGP."; Zhang & Wang Expires April 30, 2017 [Page 11] Internet-Draft Multicast Model October 2016 } grouping underlay-ospf { description "Underlay information of OSPF."; leaf topology-id { type uint16; description "The topology id of ospf instance."; } } grouping underlay-isis { description "Underlay information of ISIS."; leaf topology-id { type uint16; description "The topology id of isis instance."; } } grouping underlay-pim { description "Underlay information of PIM."; /* If there are some necessary information should be defined? */ } grouping multicast-underlay { description "The underlay information relevant multicast service."; leaf underlay-requirement { type boolean; description "If the underlay technology should be required."; } container bgp { uses underlay-bgp; description "The underlay technology is BGP."; } container ospf { uses underlay-ospf; description "The underlay technology is OSPF."; } container isis { uses underlay-isis; description "The underlay technology is ISIS."; } container pim { uses underlay-pim; description "The underlay technology is PIM."; } } container multicast-information { Zhang & Wang Expires April 30, 2017 [Page 12] Internet-Draft Multicast Model October 2016 description "The model of multicast service. Include overlay, transport and underlay."; container multicast-overlay { description "The overlay information of multicast service."; uses multicast-overlay; } container multicast-transport { description "The transportion of multicast service."; uses multicast-transport; } container multicast-underlay { description "The underlay of multicast service."; uses multicast-underlay; } } } 5. Normative References [I-D.ietf-bier-architecture] Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and S. Aldrin, "Multicast using Bit Index Explicit Replication", draft-ietf-bier-architecture-04 (work in progress), July 2016. [I-D.ietf-bier-bier-yang] Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., and M. Sivakumar, "YANG Data Model for BIER Protocol", draft-ietf-bier-bier-yang-00 (work in progress), July 2016. [I-D.ietf-pim-yang] Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, Y., and f. hu, "A YANG data model for Protocol-Independent Multicast (PIM)", draft-ietf-pim-yang-03 (work in progress), October 2016. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6037] Rosen, E., Ed., Cai, Y., Ed., and IJ. Wijnands, "Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs", RFC 6037, DOI 10.17487/RFC6037, October 2010, . Zhang & Wang Expires April 30, 2017 [Page 13] Internet-Draft Multicast Model October 2016 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, January 2011, . [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 2012, . [RFC7223] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, . Authors' Addresses Zheng(Sandy) Zhang ZTE Corporation No. 50 Software Ave, Yuhuatai Distinct Nanjing China Email: zhang.zheng@zte.com.cn Cui(Linda) Wang ZTE Corporation No. 50 Software Ave, Yuhuatai Distinct Nanjing China Email: wang.cui1@zte.com.cn Zhang & Wang Expires April 30, 2017 [Page 14]