--- 1/draft-ietf-mboned-multicast-yang-model-01.txt 2019-09-12 00:13:14.335660093 -0700 +++ 2/draft-ietf-mboned-multicast-yang-model-02.txt 2019-09-12 00:13:14.387661407 -0700 @@ -1,24 +1,24 @@ MBONED WG Zheng. Zhang Internet-Draft Cui. Wang Intended status: Standards Track ZTE Corporation -Expires: August 31, 2019 Ying. Cheng +Expires: March 15, 2020 Ying. Cheng China Unicom Xufeng. Liu Volta Networks Mahesh. Sivakumar Juniper networks - February 27, 2019 + September 12, 2019 Multicast YANG Data Model - draft-ietf-mboned-multicast-yang-model-01 + draft-ietf-mboned-multicast-yang-model-02 Abstract This document intents to provide a general and all-round multicast YANG data model, which tries to stand at a high level to take full advantages of existed multicast protocol models to control the multicast network, and guides the deployment of multicast service. And also, there will define several possible RPCs about how to interact between multicast YANG data model and multicast protocol models. This multicast YANG data model is mainly used by the @@ -34,21 +34,21 @@ 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 https://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 August 31, 2019. + This Internet-Draft will expire on March 15, 2020. Copyright Notice Copyright (c) 2019 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -216,43 +216,43 @@ +--rw source-address ip-multicast-source-address +--rw group-address rt-types:ip-multicast-group-address +--rw vni-type virtual-type +--rw vni-value uint32 +--rw multicast-overlay | +--rw ingress-egress | | +--rw ingress-node? inet:ip-address | | +--rw egress-nodes* [egress-node] | | +--rw egress-node inet:ip-address | +--rw bier-ids - | | +--rw sub-domain? bier:sub-domain-id - | | +--rw ingress-node? bier:bfr-id + | | +--rw sub-domain? uint16 + | | +--rw ingress-node? uint16 | | +--rw egress-nodes* [egress-node] - | | +--rw egress-node bier:bfr-id + | | +--rw egress-node uint16 | +--rw overlay-tech-type? enumeration +--rw multicast-transport | +--rw bier - | | +--rw sub-domain? bier:sub-domain-id + | | +--rw sub-domain? uint16 | | +--rw (encap-type)? | | | +--:(mpls) | | | +--:(eth) | | | +--:(ipv6) - | | +--rw bitstringlength? bier:bsl - | | +--rw set-identifier? bier:si + | | +--rw bitstringlength? uint16 + | | +--rw set-identifier? uint16 | | +--rw ecmp? boolean | | +--rw frr? boolean | +--rw bier-te - | | +--rw sub-domain? bier:sub-domain-id + | | +--rw sub-domain? uint16 | | +--rw (encap-type)? | | | +--:(mpls) | | | +--:(non-mpls) - | | +--rw bitstringlength? bier:bsl - | | +--rw set-identifier? bier:si + | | +--rw bitstringlength? uint16 + | | +--rw set-identifier? uint16 | | +--rw ecmp? boolean | | +--rw frr? boolean | +--rw cisco-mode | | +--rw p-group? rt-types:ip-multicast-group-address | | +--rw graceful-restart? boolean | | +--rw bfd? boolean | +--rw mpls | | +--rw (mpls-tunnel-type)? | | +--:(mldp) | | | +--rw mldp-tunnel-id? uint32 @@ -300,24 +300,20 @@ import ietf-inet-types { prefix "inet"; reference "RFC6991"; } import ietf-routing-types { prefix rt-types; reference "RFC8294"; } - import ietf-bier { - prefix bier; - } - organization " IETF MBONED( MBONE Deployment ) Working Group"; contact "WG List: Editor: Zheng Zhang Editor: Cui Wang Editor: Ying Cheng @@ -488,42 +486,43 @@ See more details in RFC6513."; } } } container bier-ids { description "The BFR-ids of ingress and egress BIER nodes for one or more multicast flows."; leaf sub-domain { - type bier:sub-domain-id; + type uint16; description "The sub-domain that this multicast flow belongs to. See more details in RFC8279."; } leaf ingress-node { - type bier:bfr-id; + type uint16; description "The ingress node of multicast flow. This is the BFR-id of ingress nodes. See more details in RFC8279."; } list egress-nodes { key "egress-node"; description "This ID information of one adjacency. See more details in RFC8279."; leaf egress-node { - type bier:bfr-id; + type uint16; description "The BFR-ids of egress multicast BIER nodes. See more details in RFC8279."; + } } } uses overlay-technology; } /*transport*/ grouping transport-pim { @@ -542,21 +541,21 @@ } grouping multicast-transport { description "The transport information of multicast service."; container bier { description "The transport technology is BIER. The BIER technology is introduced in RFC8279. The parameter is consistent with the definition in [ietf-bier-bier-yang]."; leaf sub-domain { - type bier:sub-domain-id; + type uint16; description "The subdomain id that the multicast flow belongs to. See more details in RFC8279."; } choice encap-type { case mpls { description "The BIER forwarding depends on mpls. See more details in RFC8296."; } case eth { @@ -554,35 +553,34 @@ "The subdomain id that the multicast flow belongs to. See more details in RFC8279."; } choice encap-type { case mpls { description "The BIER forwarding depends on mpls. See more details in RFC8296."; } case eth { description "The BIER forwarding depends on ethernet. - See more details in RFC8296."; } case ipv6 { description "The BIER forwarding depends on IPv6."; } description "The encapsulation type in BIER."; } leaf bitstringlength { - type bier:bsl; + type uint16; description "The bitstringlength used by BIER forwarding. See more details in RFC8279."; } leaf set-identifier { - type bier:si; + type uint16; description "The set identifier used by the multicast flow. See more details in RFC8279."; } leaf ecmp { type boolean; description "The capability of ECMP. If this value is set to true, ecmp mechanism should be enabled. See more details in RFC8279."; } leaf frr { @@ -591,21 +589,21 @@ "The capability of fast re-route. If this value is set to true, fast re-route mechanism should be enabled. See more details in RFC8279."; } } container bier-te { description "The transport technology is BIER-TE. BIER-TE technology is introduced in [ietf-bier-te-arch]."; leaf sub-domain { - type bier:sub-domain-id; + type uint16; description "The subdomain id that the multicast flow belongs to. See more details in [ietf-bier-te-arch]."; } choice encap-type { case mpls { description "The BIER-TE forwarding depends on mpls. See more details in [ietf-bier-te-arch]."; } @@ -606,30 +604,31 @@ choice encap-type { case mpls { description "The BIER-TE forwarding depends on mpls. See more details in [ietf-bier-te-arch]."; } case non-mpls { description "The BIER-TE forwarding depends on non-mpls. See more details in [ietf-bier-te-arch]."; + } description "The encapsulation type in BIER-TE."; } leaf bitstringlength { - type bier:bsl; + type uint16; description "The bitstringlength used by BIER-TE forwarding. See more details in [ietf-bier-te-arch]."; } leaf set-identifier { - type bier:si; + type uint16; description "The set identifier used by the multicast flow, especially in BIER TE. See more details in [ietf-bier-te-arch]."; } leaf ecmp { type boolean; description "The capability of ECMP. If this value is set to true, ecmp mechanism should be enabled. @@ -929,28 +927,26 @@ 7. Acknowledgements The authors would like to thank Stig Venaas, Jake Holland, Min Gu for their valuable comments and suggestions. 8. Normative References [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-04 (work in progress), September - 2018. + draft-ietf-bier-bier-yang-05 (work in progress), May 2019. [I-D.ietf-bier-te-arch] - Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic + Eckert, T., Cauchie, G., and M. Menth, "Traffic Engineering for Bit Index Explicit Replication (BIER-TE)", - draft-ietf-bier-te-arch-01 (work in progress), October - 2018. + draft-ietf-bier-te-arch-03 (work in progress), July 2019. [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-17 (work in progress), May 2018. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010,