draft-ietf-mboned-multicast-yang-model-01.txt   draft-ietf-mboned-multicast-yang-model-02.txt 
MBONED WG Zheng. Zhang MBONED WG Zheng. Zhang
Internet-Draft Cui. Wang Internet-Draft Cui. Wang
Intended status: Standards Track ZTE Corporation Intended status: Standards Track ZTE Corporation
Expires: August 31, 2019 Ying. Cheng Expires: March 15, 2020 Ying. Cheng
China Unicom China Unicom
Xufeng. Liu Xufeng. Liu
Volta Networks Volta Networks
Mahesh. Sivakumar Mahesh. Sivakumar
Juniper networks Juniper networks
February 27, 2019 September 12, 2019
Multicast YANG Data Model Multicast YANG Data Model
draft-ietf-mboned-multicast-yang-model-01 draft-ietf-mboned-multicast-yang-model-02
Abstract Abstract
This document intents to provide a general and all-round multicast 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 YANG data model, which tries to stand at a high level to take full
advantages of existed multicast protocol models to control the advantages of existed multicast protocol models to control the
multicast network, and guides the deployment of multicast service. multicast network, and guides the deployment of multicast service.
And also, there will define several possible RPCs about how to And also, there will define several possible RPCs about how to
interact between multicast YANG data model and multicast protocol interact between multicast YANG data model and multicast protocol
models. This multicast YANG data model is mainly used by the models. This multicast YANG data model is mainly used by the
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 51 skipping to change at page 5, line 51
+--rw source-address ip-multicast-source-address +--rw source-address ip-multicast-source-address
+--rw group-address rt-types:ip-multicast-group-address +--rw group-address rt-types:ip-multicast-group-address
+--rw vni-type virtual-type +--rw vni-type virtual-type
+--rw vni-value uint32 +--rw vni-value uint32
+--rw multicast-overlay +--rw multicast-overlay
| +--rw ingress-egress | +--rw ingress-egress
| | +--rw ingress-node? inet:ip-address | | +--rw ingress-node? inet:ip-address
| | +--rw egress-nodes* [egress-node] | | +--rw egress-nodes* [egress-node]
| | +--rw egress-node inet:ip-address | | +--rw egress-node inet:ip-address
| +--rw bier-ids | +--rw bier-ids
| | +--rw sub-domain? bier:sub-domain-id | | +--rw sub-domain? uint16
| | +--rw ingress-node? bier:bfr-id | | +--rw ingress-node? uint16
| | +--rw egress-nodes* [egress-node] | | +--rw egress-nodes* [egress-node]
| | +--rw egress-node bier:bfr-id | | +--rw egress-node uint16
| +--rw overlay-tech-type? enumeration | +--rw overlay-tech-type? enumeration
+--rw multicast-transport +--rw multicast-transport
| +--rw bier | +--rw bier
| | +--rw sub-domain? bier:sub-domain-id | | +--rw sub-domain? uint16
| | +--rw (encap-type)? | | +--rw (encap-type)?
| | | +--:(mpls) | | | +--:(mpls)
| | | +--:(eth) | | | +--:(eth)
| | | +--:(ipv6) | | | +--:(ipv6)
| | +--rw bitstringlength? bier:bsl | | +--rw bitstringlength? uint16
| | +--rw set-identifier? bier:si | | +--rw set-identifier? uint16
| | +--rw ecmp? boolean | | +--rw ecmp? boolean
| | +--rw frr? boolean | | +--rw frr? boolean
| +--rw bier-te | +--rw bier-te
| | +--rw sub-domain? bier:sub-domain-id | | +--rw sub-domain? uint16
| | +--rw (encap-type)? | | +--rw (encap-type)?
| | | +--:(mpls) | | | +--:(mpls)
| | | +--:(non-mpls) | | | +--:(non-mpls)
| | +--rw bitstringlength? bier:bsl | | +--rw bitstringlength? uint16
| | +--rw set-identifier? bier:si | | +--rw set-identifier? uint16
| | +--rw ecmp? boolean | | +--rw ecmp? boolean
| | +--rw frr? boolean | | +--rw frr? boolean
| +--rw cisco-mode | +--rw cisco-mode
| | +--rw p-group? rt-types:ip-multicast-group-address | | +--rw p-group? rt-types:ip-multicast-group-address
| | +--rw graceful-restart? boolean | | +--rw graceful-restart? boolean
| | +--rw bfd? boolean | | +--rw bfd? boolean
| +--rw mpls | +--rw mpls
| | +--rw (mpls-tunnel-type)? | | +--rw (mpls-tunnel-type)?
| | +--:(mldp) | | +--:(mldp)
| | | +--rw mldp-tunnel-id? uint32 | | | +--rw mldp-tunnel-id? uint32
skipping to change at page 7, line 38 skipping to change at page 7, line 38
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC6991"; reference "RFC6991";
} }
import ietf-routing-types { import ietf-routing-types {
prefix rt-types; prefix rt-types;
reference "RFC8294"; reference "RFC8294";
} }
import ietf-bier {
prefix bier;
}
organization " IETF MBONED( MBONE Deployment ) Working Group"; organization " IETF MBONED( MBONE Deployment ) Working Group";
contact contact
"WG List: <mailto:mboned@ietf.org> "WG List: <mailto:mboned@ietf.org>
Editor: Zheng Zhang Editor: Zheng Zhang
<mailto:zzhang_ietf@hotmail.com> <mailto:zzhang_ietf@hotmail.com>
Editor: Cui Wang Editor: Cui Wang
<mailto:lindawangjoy@gmail.com> <mailto:lindawangjoy@gmail.com>
Editor: Ying Cheng Editor: Ying Cheng
<mailto:chengying10@chinaunicom.cn> <mailto:chengying10@chinaunicom.cn>
skipping to change at page 11, line 33 skipping to change at page 11, line 30
See more details in RFC6513."; See more details in RFC6513.";
} }
} }
} }
container bier-ids { container bier-ids {
description description
"The BFR-ids of ingress and egress BIER nodes for "The BFR-ids of ingress and egress BIER nodes for
one or more multicast flows."; one or more multicast flows.";
leaf sub-domain { leaf sub-domain {
type bier:sub-domain-id; type uint16;
description description
"The sub-domain that this multicast flow belongs "The sub-domain that this multicast flow belongs
to. See more details in RFC8279."; to. See more details in RFC8279.";
} }
leaf ingress-node { leaf ingress-node {
type bier:bfr-id; type uint16;
description description
"The ingress node of multicast flow. This is the "The ingress node of multicast flow. This is the
BFR-id of ingress nodes. See more details in RFC8279."; BFR-id of ingress nodes. See more details in RFC8279.";
} }
list egress-nodes { list egress-nodes {
key "egress-node"; key "egress-node";
description description
"This ID information of one adjacency. See more "This ID information of one adjacency. See more
details in RFC8279."; details in RFC8279.";
leaf egress-node { leaf egress-node {
type bier:bfr-id; type uint16;
description description
"The BFR-ids of egress multicast BIER nodes. "The BFR-ids of egress multicast BIER nodes.
See more details in RFC8279."; See more details in RFC8279.";
} }
} }
} }
uses overlay-technology; uses overlay-technology;
} }
/*transport*/ /*transport*/
grouping transport-pim { grouping transport-pim {
skipping to change at page 12, line 39 skipping to change at page 12, line 37
} }
grouping multicast-transport { grouping multicast-transport {
description "The transport information of multicast service."; description "The transport information of multicast service.";
container bier { container bier {
description description
"The transport technology is BIER. The BIER technology "The transport technology is BIER. The BIER technology
is introduced in RFC8279. The parameter is consistent is introduced in RFC8279. The parameter is consistent
with the definition in [ietf-bier-bier-yang]."; with the definition in [ietf-bier-bier-yang].";
leaf sub-domain { leaf sub-domain {
type bier:sub-domain-id; type uint16;
description description
"The subdomain id that the multicast flow belongs "The subdomain id that the multicast flow belongs
to. See more details in RFC8279."; to. See more details in RFC8279.";
} }
choice encap-type { choice encap-type {
case mpls { case mpls {
description "The BIER forwarding depends on mpls. description "The BIER forwarding depends on mpls.
See more details in RFC8296."; See more details in RFC8296.";
} }
case eth { case eth {
skipping to change at page 13, line 4 skipping to change at page 12, line 49
"The subdomain id that the multicast flow belongs "The subdomain id that the multicast flow belongs
to. See more details in RFC8279."; to. See more details in RFC8279.";
} }
choice encap-type { choice encap-type {
case mpls { case mpls {
description "The BIER forwarding depends on mpls. description "The BIER forwarding depends on mpls.
See more details in RFC8296."; See more details in RFC8296.";
} }
case eth { case eth {
description "The BIER forwarding depends on ethernet. description "The BIER forwarding depends on ethernet.
See more details in RFC8296."; See more details in RFC8296.";
} }
case ipv6 { case ipv6 {
description "The BIER forwarding depends on IPv6."; description "The BIER forwarding depends on IPv6.";
} }
description "The encapsulation type in BIER."; description "The encapsulation type in BIER.";
} }
leaf bitstringlength { leaf bitstringlength {
type bier:bsl; type uint16;
description "The bitstringlength used by BIER forwarding. description "The bitstringlength used by BIER forwarding.
See more details in RFC8279."; See more details in RFC8279.";
} }
leaf set-identifier { leaf set-identifier {
type bier:si; type uint16;
description "The set identifier used by the multicast flow. description "The set identifier used by the multicast flow.
See more details in RFC8279."; See more details in RFC8279.";
} }
leaf ecmp { leaf ecmp {
type boolean; type boolean;
description description
"The capability of ECMP. If this value is set to true, "The capability of ECMP. If this value is set to true,
ecmp mechanism should be enabled. See more details in RFC8279."; ecmp mechanism should be enabled. See more details in RFC8279.";
} }
leaf frr { leaf frr {
skipping to change at page 13, line 41 skipping to change at page 13, line 37
"The capability of fast re-route. If this value is "The capability of fast re-route. If this value is
set to true, fast re-route mechanism should be set to true, fast re-route mechanism should be
enabled. See more details in RFC8279."; enabled. See more details in RFC8279.";
} }
} }
container bier-te { container bier-te {
description description
"The transport technology is BIER-TE. BIER-TE technology "The transport technology is BIER-TE. BIER-TE technology
is introduced in [ietf-bier-te-arch]."; is introduced in [ietf-bier-te-arch].";
leaf sub-domain { leaf sub-domain {
type bier:sub-domain-id; type uint16;
description description
"The subdomain id that the multicast flow belongs to. "The subdomain id that the multicast flow belongs to.
See more details in [ietf-bier-te-arch]."; See more details in [ietf-bier-te-arch].";
} }
choice encap-type { choice encap-type {
case mpls { case mpls {
description description
"The BIER-TE forwarding depends on mpls. See more "The BIER-TE forwarding depends on mpls. See more
details in [ietf-bier-te-arch]."; details in [ietf-bier-te-arch].";
} }
skipping to change at page 14, line 7 skipping to change at page 14, line 4
choice encap-type { choice encap-type {
case mpls { case mpls {
description description
"The BIER-TE forwarding depends on mpls. See more "The BIER-TE forwarding depends on mpls. See more
details in [ietf-bier-te-arch]."; details in [ietf-bier-te-arch].";
} }
case non-mpls { case non-mpls {
description description
"The BIER-TE forwarding depends on non-mpls. See "The BIER-TE forwarding depends on non-mpls. See
more details in [ietf-bier-te-arch]."; more details in [ietf-bier-te-arch].";
} }
description "The encapsulation type in BIER-TE."; description "The encapsulation type in BIER-TE.";
} }
leaf bitstringlength { leaf bitstringlength {
type bier:bsl; type uint16;
description "The bitstringlength used by BIER-TE forwarding. description "The bitstringlength used by BIER-TE forwarding.
See more details in [ietf-bier-te-arch]."; See more details in [ietf-bier-te-arch].";
} }
leaf set-identifier { leaf set-identifier {
type bier:si; type uint16;
description description
"The set identifier used by the multicast flow, "The set identifier used by the multicast flow,
especially in BIER TE. See more details in especially in BIER TE. See more details in
[ietf-bier-te-arch]."; [ietf-bier-te-arch].";
} }
leaf ecmp { leaf ecmp {
type boolean; type boolean;
description description
"The capability of ECMP. If this value is set to "The capability of ECMP. If this value is set to
true, ecmp mechanism should be enabled. true, ecmp mechanism should be enabled.
skipping to change at page 20, line 41 skipping to change at page 20, line 37
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Stig Venaas, Jake Holland, Min Gu for The authors would like to thank Stig Venaas, Jake Holland, Min Gu for
their valuable comments and suggestions. their valuable comments and suggestions.
8. Normative References 8. Normative References
[I-D.ietf-bier-bier-yang] [I-D.ietf-bier-bier-yang]
Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d., Chen, R., hu, f., Zhang, Z., dai.xianxian@zte.com.cn, d.,
and M. Sivakumar, "YANG Data Model for BIER Protocol", and M. Sivakumar, "YANG Data Model for BIER Protocol",
draft-ietf-bier-bier-yang-04 (work in progress), September draft-ietf-bier-bier-yang-05 (work in progress), May 2019.
2018.
[I-D.ietf-bier-te-arch] [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)", Engineering for Bit Index Explicit Replication (BIER-TE)",
draft-ietf-bier-te-arch-01 (work in progress), October draft-ietf-bier-te-arch-03 (work in progress), July 2019.
2018.
[I-D.ietf-pim-yang] [I-D.ietf-pim-yang]
Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
Y., and f. hu, "A YANG Data Model for Protocol Independent Y., and f. hu, "A YANG Data Model for Protocol Independent
Multicast (PIM)", draft-ietf-pim-yang-17 (work in Multicast (PIM)", draft-ietf-pim-yang-17 (work in
progress), May 2018. progress), May 2018.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
 End of changes. 26 change blocks. 
32 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/