draft-ietf-mboned-multicast-yang-model-03.txt   draft-ietf-mboned-multicast-yang-model-04.txt 
MBONED WG Z. Zhang MBONED WG Z. Zhang
Internet-Draft ZTE Corporation Internet-Draft ZTE Corporation
Intended status: Standards Track C. Wang Intended status: Standards Track C. Wang
Expires: September 8, 2020 Individual Expires: May 2, 2021 Individual
Y. Cheng Y. Cheng
China Unicom China Unicom
X. Liu X. Liu
Volta Networks Volta Networks
M. Sivakumar M. Sivakumar
Juniper networks Juniper networks
March 7, 2020 October 29, 2020
Multicast YANG Data Model Multicast YANG Data Model
draft-ietf-mboned-multicast-yang-model-03 draft-ietf-mboned-multicast-yang-model-04
Abstract Abstract
This document provides a general multicast YANG data model, which This document provides a general multicast YANG data model, which
takes full advantages of existed multicast protocol models to control takes full advantages of existed multicast protocol models to control
the multicast network, and guides the deployment of multicast the multicast network, and guides the deployment of multicast
service. service.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 September 8, 2020. This Internet-Draft will expire on May 2, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 2, line 26 skipping to change at page 2, line 26
1.3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
1.4. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 1.4. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
1.5. Usage of Multicast Model . . . . . . . . . . . . . . . . 4 1.5. Usage of Multicast Model . . . . . . . . . . . . . . . . 4
2. Design of the multicast model . . . . . . . . . . . . . . . . 6 2. Design of the multicast model . . . . . . . . . . . . . . . . 6
2.1. Scope of Model . . . . . . . . . . . . . . . . . . . . . 6 2.1. Scope of Model . . . . . . . . . . . . . . . . . . . . . 6
2.2. Specification . . . . . . . . . . . . . . . . . . . . . . 7 2.2. Specification . . . . . . . . . . . . . . . . . . . . . . 7
3. Module Structure . . . . . . . . . . . . . . . . . . . . . . 7 3. Module Structure . . . . . . . . . . . . . . . . . . . . . . 7
3.1. UML like Class Diagram for Multicast YANG data Model . . 7 3.1. UML like Class Diagram for Multicast YANG data Model . . 7
3.2. Model Structure . . . . . . . . . . . . . . . . . . . . . 9 3.2. Model Structure . . . . . . . . . . . . . . . . . . . . . 9
3.3. Multicast YANG data model Configuration . . . . . . . . . 12 3.3. Multicast YANG data model Configuration . . . . . . . . . 12
3.4. Multicast YANG data model State . . . . . . . . . . . . . 12 3.4. Multicast YANG data model State . . . . . . . . . . . . . 13
3.5. Multicast YANG data model Notification . . . . . . . . . 12 3.5. Multicast YANG data model Notification . . . . . . . . . 13
4. Multicast YANG data Model . . . . . . . . . . . . . . . . . . 13 4. Multicast YANG data Model . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 26 5. Security Considerations . . . . . . . . . . . . . . . . . . . 27
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.1. Normative References . . . . . . . . . . . . . . . . . . 28 8.1. Normative References . . . . . . . . . . . . . . . . . . 28
8.2. Informative References . . . . . . . . . . . . . . . . . 31 8.2. Informative References . . . . . . . . . . . . . . . . . 31
Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 33 Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
Currently, there are many multicast protocol YANG models, such as Currently, there are many multicast protocol YANG models, such as
PIM, MLD, and BIER and so on. But all these models are distributed PIM, MLD, and BIER and so on. But all these models are distributed
in different working groups as separate files and focus on the in different working groups as separate files and focus on the
protocol itself. Furthermore, they cannot describe a high-level protocol itself. Furthermore, they cannot describe a high-level
multicast service required by network operators. multicast service required by network operators.
This document provides a general and all-round multicast model, which This document provides a general and all-round multicast model, which
skipping to change at page 5, line 29 skipping to change at page 5, line 29
Figure 1: Usage of Multicast Model Figure 1: Usage of Multicast Model
Detailly, in figure 1, there is an example of usage of this multicast Detailly, in figure 1, there is an example of usage of this multicast
model. Network operators can use this model in a controller which is model. Network operators can use this model in a controller which is
responsible to implement specific multicast flows with specific responsible to implement specific multicast flows with specific
protocols and invoke the corresponding protocols' model to configure protocols and invoke the corresponding protocols' model to configure
the network elements through NETCONF/RESTCONF/CLI. Or network the network elements through NETCONF/RESTCONF/CLI. Or network
operators can use this model to the EMS/NMS to manage the network operators can use this model to the EMS/NMS to manage the network
elements or configure the network elements directly. elements or configure the network elements directly.
+------------+ +------------+
| +----------------------------+ | +---------------------------+
+--------------+ Controller | | +--------------+ Controller | |
| | +-----------+ | | | +-----------+ |
| +------------+ | | | +------------+ | |
| | | | | |
| +-----------------------------+ | | | +-----------------------------+ | |
| | | | | | | | | |
| | +------+---+--+ | | | +------+---+--+ |
| | |Egress router+--+ Receiver | | | |Egress router+--+ Receiver|
| | +------+------+ | | | +------+------+ |
+---+-----+----+ | | +---+-----+----+ | |
Source +-|Ingress router| BIER domain | | Source +-|Ingress router| BIER domain | |
+---------+----+ | | +---------+----+ | |
| +------+------+ | | +------+------+ |
| |Egress router+--+ Receiver | | |Egress router+--+ Receiver|
| +------+----+-+ | | +------+----+-+ |
| | | | | | | |
+-----------------------------+ +---------------+ +-----------------------------+ +--------------+
Figure 2: Example Figure 2: Example
The network administrator can use the multicast model and associated The network administrator can use the multicast model and associated
models to deploy the multicast service. For example, suppose that models to deploy the multicast service. For example, suppose that
the flow for a multicast service is 233.252.0.0/16, the flow should the flow for a multicast service is 233.252.0.0/16, the flow should
be forwarded by BIER [RFC8279] with MPLS encapsulation [RFC8296]. be forwarded by BIER [RFC8279] with MPLS encapsulation [RFC8296].
Correspoding IGP protocol which is used to build BIER transport layer Correspoding IGP protocol which is used to build BIER transport layer
is OSPF [RFC2328]. is OSPF [RFC2328].
skipping to change at page 9, line 7 skipping to change at page 9, line 7
| | +------+ +------+ | | +------+ +------+
+----------+-- | ISIS | | BGP | +----------+-- | ISIS | | BGP |
| +--+---+ +--+---+ | +--+---+ +--+---+
| | | | | |
+--------------+---------+ +--------------+---------+
Figure 3: UML like Class Diagram for Multicast YANG data Model Figure 3: UML like Class Diagram for Multicast YANG data Model
3.2. Model Structure 3.2. Model Structure
module: ietf-multicast-model module: ietf-multicast-model
+--rw multicast-model +--rw multicast-model
+--rw multicast-keys* [vpn-rd source-address group-address +--rw multicast-keys*
vni-type vni-value] [vpn-rd source-address group-address vni-type vni-value]
+--rw vpn-rd rt-types:route-distinguisher +--rw vpn-rd rt-types:route-distinguisher
+--rw source-address ip-multicast-source-address +--rw source-address ip-multicast-source-address
+--rw group-address +--rw group-address
rt-types:ip-multicast-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? uint16 | | +--rw sub-domain? uint16
| | +--rw ingress-node? uint16 | | +--rw ingress-node? uint16
| | +--rw egress-nodes* [egress-node] | | +--rw egress-nodes* [egress-node]
| | +--rw egress-node uint16 | | +--rw egress-node uint16
| +--rw (overlay-tech-type)? | +--rw (overlay-tech-type)?
| +--:(bgp) | +--:(bgp)
| +--:(evpn) | +--:(evpn)
| +--:(mld) | +--:(mld)
| | +--rw mld-instance-group? | | +--rw mld-instance-group?
rt-types:ip-multicast-group-address rt-types:ip-multicast-group-address
| +--:(mld-snooping) | +--:(mld-snooping)
| +--:(mvpn) | +--:(mvpn)
| +--:(pim) | +--:(pim)
+--rw multicast-transport +--rw multicast-transport
| +--rw (transport)? | +--rw (transport)?
| +--:(bier) | +--:(bier)
| | +--rw bier | | +--rw bier
| | +--rw sub-domain? uint16 | | +--rw sub-domain? uint16
| | +--rw bitstringlength? uint16 | | +--rw bitstringlength? uint16
| | +--rw set-identifier? uint16 | | +--rw set-identifier? uint16
| | +--rw (encap-type)? | | +--rw (encap-type)?
| | +--:(mpls) | | +--:(mpls)
| | +--:(eth) | | +--:(eth)
| | +--:(ipv6) | | +--:(ipv6)
| +--:(bier-te) | +--:(bier-te)
| | +--rw bier-te | | +--rw bier-te
| | +--rw sub-domain? uint16 | | +--rw sub-domain? uint16
| | +--rw bitstringlength? uint16 | | +--rw bitstringlength? uint16
| | +--rw set-identifier? uint16 | | +--rw set-identifier? uint16
| | +--rw (encap-type)? | | +--rw (encap-type)?
| | | +--:(mpls) | | | +--:(mpls)
| | | +--:(eth) | | | +--:(eth)
| | | +--:(ipv6) | | | +--:(ipv6)
| | +--rw bier-te-adj* uint16 | | +--rw bier-te-adj* uint16
| +--:(cisco-mode) | +--:(cisco-mode)
| | +--rw cisco-mode | | +--rw cisco-mode
| | +--rw p-group? | | +--rw p-group?
rt-types:ip-multicast-group-address rt-types:ip-multicast-group-address
| +--:(mpls) | +--:(mpls)
| | +--rw mpls | | +--rw mpls
| | +--rw (mpls-tunnel-type)? | | +--rw (mpls-lsp-type)?
| | +--:(mldp) | | +--:(mldp)
| | | +--rw mldp-tunnel-id? uint32 | | | +--rw mldp-lsp
| | | +--rw mldp-backup-tunnel? boolean | | | +--rw root-address?
| | +--:(p2mp-te) ip-multicast-source-address
| | +--rw te-tunnel-id? uint32 | | | +--rw lsp-id? uint32
| | +--rw te-backup-tunnel? boolean | | | +--rw backup-lsp-id? uint32
| +--:(pim) | | +--:(p2mp-te)
| +--rw pim | | +--rw p2mp-te-lsp
+--rw multicast-underlay | | +--rw root-address?
+--rw (underlay)? ip-multicast-source-address
+--:(bgp) | | +--rw lsp-id? uint32
+--:(ospf) | | +--rw backup-lsp-id? uint32
| +--rw ospf | +--:(pim)
| +--rw topology? | +--rw pim
-> /rt:routing/control-plane-protocols +--rw multicast-underlay
/control-plane-protocol/ospf:ospf +--rw (underlay)?
/topologies/topology/name +--:(bgp)
+--:(isis) +--:(ospf)
+--:(babel) | +--rw ospf
| +--rw topology?
-> /rt:routing/control-plane-protocols
/control-plane-protocol/ospf:ospf
/topologies/topology/name
+--:(isis)
+--:(babel)
notifications: notifications:
+---n head-end-event +---n head-end-event
+--ro event-type? enumeration +--ro event-type? enumeration
+--ro multicast-key +--ro multicast-key
| +--ro vpn-rd? rt-types:route-distinguisher | +--ro vpn-rd? rt-types:route-distinguisher
| +--ro source-address? ip-multicast-source-address | +--ro source-address? ip-multicast-source-address
| +--ro group-address? rt-types:ip-multicast-group-address | +--ro group-address? rt-types:ip-multicast-group-address
| +--ro vni-type? virtual-type | +--ro vni-type? virtual-type
| +--ro vni-value? uint32 | +--ro vni-value? uint32
+--ro (overlay-tech-type)? +--ro (overlay-tech-type)?
| +--:(bgp) | +--:(bgp)
| +--:(evpn) | +--:(evpn)
| +--:(mld) | +--:(mld)
| | +--ro mld-instance-group? | | +--ro mld-instance-group?
rt-types:ip-multicast-group-address rt-types:ip-multicast-group-address
| +--:(mld-snooping) | +--:(mld-snooping)
| +--:(mvpn) | +--:(mvpn)
| +--:(pim) | +--:(pim)
+--ro transport-tech +--ro transport-tech
| +--ro (transport)? | +--ro (transport)?
| +--:(bier) | +--:(bier)
| | +--ro bier | | +--ro bier
| | +--ro sub-domain? uint16 | | +--ro sub-domain? uint16
| | +--ro bitstringlength? uint16 | | +--ro bitstringlength? uint16
| | +--ro set-identifier? uint16 | | +--ro set-identifier? uint16
| | +--ro (encap-type)? | | +--ro (encap-type)?
| | +--:(mpls) | | +--:(mpls)
| | +--:(eth) | | +--:(eth)
| | +--:(ipv6) | | +--:(ipv6)
| +--:(bier-te) | +--:(bier-te)
| | +--ro bier-te | | +--ro bier-te
| | +--ro sub-domain? uint16 | | +--ro sub-domain? uint16
| | +--ro bitstringlength? uint16 | | +--ro bitstringlength? uint16
| | +--ro set-identifier? uint16 | | +--ro set-identifier? uint16
| | +--ro (encap-type)? | | +--ro (encap-type)?
| | | +--:(mpls) | | | +--:(mpls)
| | | +--:(eth) | | | +--:(eth)
| | | +--:(ipv6) | | | +--:(ipv6)
| | +--ro bier-te-adj* uint16 | | +--ro bier-te-adj* uint16
| +--:(cisco-mode) | +--:(cisco-mode)
| | +--ro cisco-mode | | +--ro cisco-mode
| | +--ro p-group? rt-types:ip-multicast-group-address | | +--ro p-group?
| +--:(mpls) rt-types:ip-multicast-group-address
| | +--ro mpls | +--:(mpls)
| | +--ro (mpls-tunnel-type)? | | +--ro mpls
| | +--:(mldp) | | +--ro (mpls-lsp-type)?
| | | +--ro mldp-tunnel-id? uint32 | | +--:(mldp)
| | | +--ro mldp-backup-tunnel? boolean | | | +--ro mldp-lsp
| | +--:(p2mp-te) | | | +--ro root-address?
| | +--ro te-tunnel-id? uint32 ip-multicast-source-address
| | +--ro te-backup-tunnel? boolean | | | +--ro lsp-id? uint32
| +--:(pim) | | | +--ro backup-lsp-id? uint32
| +--ro pim | | +--:(p2mp-te)
+--ro underlay-tech | | +--ro p2mp-te-lsp
+--ro (underlay)? | | +--ro root-address?
+--:(bgp) ip-multicast-source-address
+--:(ospf) | | +--ro lsp-id? uint32
| +--ro ospf | | +--ro backup-lsp-id? uint32
| +--ro topology? | +--:(pim)
-> /rt:routing/control-plane-protocols | +--ro pim
/control-plane-protocol/ospf:ospf +--ro underlay-tech
/topologies/topology/name +--ro (underlay)?
+--:(isis) +--:(bgp)
+--:(babel) +--:(ospf)
| +--ro ospf
| +--ro topology?
-> /rt:routing/control-plane-protocols
/control-plane-protocol/ospf:ospf
/topologies/topology/name
+--:(isis)
+--:(babel)
3.3. Multicast YANG data model Configuration 3.3. Multicast YANG data model Configuration
This model is used with other protocol data model to provide This model is used with other protocol data model to provide
multicast service. multicast service.
This model includes multicast service keys and three layers: the This model includes multicast service keys and three layers: the
multicast overlay, the transport layer and the multicast underlay multicast overlay, the transport layer and the multicast underlay
information. Multicast keys include the features of multicast flow, information. Multicast keys include the features of multicast flow,
such as(vpnid, multicast source and multicast group) information. In such as(vpnid, multicast source and multicast group) information. In
skipping to change at page 13, line 17 skipping to change at page 13, line 31
This module references [RFC1195], [RFC2328], [RFC4271], [RFC4541], This module references [RFC1195], [RFC2328], [RFC4271], [RFC4541],
[RFC4875], [RFC5340], [RFC6037], [RFC6388], [RFC6513], [RFC6991], [RFC4875], [RFC5340], [RFC6037], [RFC6388], [RFC6513], [RFC6991],
[RFC7348], [RFC7432], [RFC7637], [RFC7716], [RFC7761], [RFC8279], [RFC7348], [RFC7432], [RFC7637], [RFC7716], [RFC7761], [RFC8279],
[RFC8294], [RFC8296], [RFC8343], [RFC8344], [RFC8349], [RFC8639], [RFC8294], [RFC8296], [RFC8343], [RFC8344], [RFC8349], [RFC8639],
[RFC8641], [I-D.ietf-pim-yang], [I-D.ietf-bier-bier-yang], [RFC8641], [I-D.ietf-pim-yang], [I-D.ietf-bier-bier-yang],
[I-D.ietf-bier-te-arch], [I-D.ietf-nvo3-geneve], [I-D.ietf-bier-mld], [I-D.ietf-bier-te-arch], [I-D.ietf-nvo3-geneve], [I-D.ietf-bier-mld],
[I-D.ietf-bess-evpn-bum-procedure-updates], [I-D.ietf-bier-evpn], [I-D.ietf-bess-evpn-bum-procedure-updates], [I-D.ietf-bier-evpn],
[I-D.zhang-bier-bierin6], [I-D.ietf-babel-rfc6126bis], [I-D.zhang-bier-bierin6], [I-D.ietf-babel-rfc6126bis],
[I-D.ietf-bier-pim-signaling]. [I-D.ietf-bier-pim-signaling].
<CODE BEGINS> file "ietf-multicast-model@2020-03-06.yang" <CODE BEGINS> file "ietf-multicast-model@2020-10-28.yang"
module ietf-multicast-model { module ietf-multicast-model {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-multicast-model"; namespace "urn:ietf:params:xml:ns:yang:ietf-multicast-model";
prefix multicast-model; prefix multicast-model;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference reference
skipping to change at page 13, line 52 skipping to change at page 14, line 17
prefix "ospf"; prefix "ospf";
reference reference
"I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol"; "I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol";
} }
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:zhang.zheng@zte.com.cn>
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>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Mahesh Sivakumar Editor: Mahesh Sivakumar
<mailto:sivakumar.mahesh@gmail.com> <mailto:sivakumar.mahesh@gmail.com>
"; ";
skipping to change at page 14, line 43 skipping to change at page 15, line 8
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices. itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119) are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all (RFC 8174) when, and only when, they appear in all
capitals, as shown here."; capitals, as shown here.";
revision 2020-03-06 { revision 2020-09-30 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for multicast YANG."; "RFC XXXX: A YANG Data Model for multicast YANG.";
} }
/* /*
*typedef *typedef
*/ */
skipping to change at page 18, line 4 skipping to change at page 18, line 19
} }
leaf bitstringlength { leaf bitstringlength {
type uint16; type uint16;
description description
"The bitstringlength used by BIER forwarding."; "The bitstringlength used by BIER forwarding.";
} }
leaf set-identifier { leaf set-identifier {
type uint16; type uint16;
description description
"The set identifier used by the multicast flow."; "The set identifier used by the multicast flow.";
} }
uses encap-type; uses encap-type;
} }
grouping lsp {
description "The lsp information.";
leaf root-address {
type ip-multicast-source-address;
description
"Root address of the mldp fec.";
}
leaf lsp-id {
type uint32;
description
"The lsp id that corresponding this flow.";
}
leaf backup-lsp-id {
type uint32;
description
"The backup lsp id that corresponding this flow.
In case the lsp fails, the backup lsp can be used.";
}
} // lsp
grouping transport-tech { grouping transport-tech {
choice transport { choice transport {
description "The selected transport technology."; description "The selected transport technology.";
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 BIER YANG data model."; with the definition in BIER YANG data model.";
reference reference
"RFC 8279: Multicast Using Bit Index Explicit "RFC 8279: Multicast Using Bit Index Explicit
skipping to change at page 19, line 13 skipping to change at page 19, line 47
description description
"The address of p-group. It is used to encapsulate "The address of p-group. It is used to encapsulate
and forward flow according to multicast tree from and forward flow according to multicast tree from
ingress node to egress nodes."; ingress node to egress nodes.";
} }
uses transport-pim; uses transport-pim;
} }
container mpls { container mpls {
description description
"The transport technology is mpls. MVPN overlay can use "The transport technology is mpls. Multicast overlay can use
mpls tunnel technologies to build transport layer."; mpls technologies to build transport layer.";
reference reference
"RFC 6513: Multicast in MPLS/BGP IP VPNs."; "RFC 6513: Multicast in MPLS/BGP IP VPNs.";
choice mpls-tunnel-type { choice mpls-lsp-type {
case mldp { case mldp {
description "The mldp tunnel."; description
"The mldp type of lsp is used as multicast
transportation.
The YANG data model defined in 'ietf-mpls-mldp-yang'
can be invoked.";
reference reference
"RFC 6388: Label Distribution Protocol Extensions "RFC 6388: Label Distribution Protocol Extensions
for Point-to-Multipoint and Multipoint-to-Multipoint for Point-to-Multipoint and Multipoint-to-Multipoint
Label Switched Paths."; Label Switched Paths.
I-D.ietf-mpls-mldp-yang:
YANG Data Model for MPLS mLDP.";
leaf mldp-tunnel-id { container mldp-lsp {
type uint32;
description
"The tunnel id that correspond this flow.";
}
leaf mldp-backup-tunnel {
type boolean;
description description
"If the backup tunnel function should be "The specific parameters can be set to use
supported."; the specific mldp fec.";
uses lsp;
} }
} }
case p2mp-te { case p2mp-te {
description description
"The p2mp te tunnel."; "The p2mp te type of lsp is used as multicast
transportation.";
reference reference
"RFC 4875: Extensions to Resource Reservation Protocol "RFC 4875: Extensions to Resource Reservation Protocol
- Traffic Engineering (RSVP-TE) for Point-to-Multipoint - Traffic Engineering (RSVP-TE) for Point-to-Multipoint
TE Label Switched Paths (LSPs)."; TE Label Switched Paths (LSPs).";
leaf te-tunnel-id { container p2mp-te-lsp {
type uint32;
description
"The tunnel id that correspond this flow.";
}
leaf te-backup-tunnel {
type boolean;
description description
"If the backup tunnel function should be "The specific parameters can be set to use
supported."; the specific mldp fec.";
uses lsp;
} }
} }
description "The collection types of mpls tunnels"; description "The collection types of mpls tunnels";
} }
} // mpls } // mpls
container pim { container pim {
description description
"The transport technology is PIM. PIM is used "The transport technology is PIM. PIM is used
commonly in traditional network."; commonly in traditional network.";
skipping to change at page 20, line 31 skipping to change at page 21, line 15
uses transport-pim; uses transport-pim;
} }
} // choice } // choice
} // transport-tech } // transport-tech
grouping underlay-tech { grouping underlay-tech {
choice underlay { choice underlay {
case bgp { case bgp {
description description
"The underlay technology is BGP. BGP protocol "The underlay technology is BGP. BGP protocol
should be used to run if BGP is used as should run if BGP is used as underlay protocol.";
underlay protocol.";
reference reference
"RFC 4271: A Border Gateway Protocol 4 (BGP-4)"; "RFC 4271: A Border Gateway Protocol 4 (BGP-4)";
} }
container ospf { container ospf {
description description
"The underlay technology is OSPF. OSPF protocol "The underlay technology is OSPF. OSPF protocol
should be triggered to run if OSPF is used as underlay should be triggered to run if OSPF is used as underlay
protocol."; protocol.";
reference reference
"RFC 2328: OSPF Version 2. "RFC 2328: OSPF Version 2.
skipping to change at page 22, line 5 skipping to change at page 22, line 36
"RFC 7432: BGP MPLS-Based Ethernet VPN. "RFC 7432: BGP MPLS-Based Ethernet VPN.
I-D.ietf-bess-evpn-bum-procedure-updates: Updates on I-D.ietf-bess-evpn-bum-procedure-updates: Updates on
EVPN BUM Procedures. EVPN BUM Procedures.
I-D.ietf-bier-evpn: EVPN BUM Using BIER."; I-D.ietf-bier-evpn: EVPN BUM Using BIER.";
} }
case mld { case mld {
description description
"MLD technology is used for multicast overlay."; "MLD technology is used for multicast overlay.";
reference reference
"I-D.ietf-bier-mld: BIER Ingress Multicast Flow Overlay "I-D.ietf-bier-mld: BIER Ingress Multicast Flow Overlay
using Multicast Listener Discovery Protocols."; using Multicast Listener Discovery Protocols.";
leaf mld-instance-group { leaf mld-instance-group {
type rt-types:ip-multicast-group-address; type rt-types:ip-multicast-group-address;
description description
"The multicast address used for multiple MLD instance "The multicast address used for multiple MLD instance
support."; support.";
} }
} }
case mld-snooping { case mld-snooping {
description description
"MLD snooping technology is used for multicast overlay."; "MLD snooping technology is used for multicast overlay.";
skipping to change at page 22, line 32 skipping to change at page 23, line 14
description description
"MVPN technology is used for multicast overlay."; "MVPN technology is used for multicast overlay.";
reference reference
"RFC 6513: Multicast in MPLS/BGP IP VPNs."; "RFC 6513: Multicast in MPLS/BGP IP VPNs.";
} }
case pim { case pim {
description description
"PIM technology is used for multicast overlay."; "PIM technology is used for multicast overlay.";
reference reference
"I-D.ietf-bier-pim-signaling: PIM Signaling "I-D.ietf-bier-pim-signaling: PIM Signaling
Through BIER Core."; Through BIER Core.";
} }
description description
"The overlay technology used for multicast service."; "The overlay technology used for multicast service.";
} }
description "The overlay technology used for multicast service."; description "The overlay technology used for multicast service.";
} // overlay-tech } // overlay-tech
/*transport*/ /*transport*/
grouping transport-pim { grouping transport-pim {
skipping to change at page 31, line 13 skipping to change at page 31, line 46
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-babel-rfc6126bis] [I-D.ietf-babel-rfc6126bis]
Chroboczek, J. and D. Schinazi, "The Babel Routing Chroboczek, J. and D. Schinazi, "The Babel Routing
Protocol", draft-ietf-babel-rfc6126bis-17 (work in Protocol", draft-ietf-babel-rfc6126bis-20 (work in
progress), February 2020. progress), August 2020.
[I-D.ietf-bess-evpn-bum-procedure-updates] [I-D.ietf-bess-evpn-bum-procedure-updates]
Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A. Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A.
Sajassi, "Updates on EVPN BUM Procedures", draft-ietf- Sajassi, "Updates on EVPN BUM Procedures", draft-ietf-
bess-evpn-bum-procedure-updates-08 (work in progress), bess-evpn-bum-procedure-updates-08 (work in progress),
November 2019. November 2019.
[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-06 (work in progress), February draft-ietf-bier-bier-yang-07 (work in progress), September
2020. 2020.
[I-D.ietf-bier-evpn] [I-D.ietf-bier-evpn]
Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan, Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,
"EVPN BUM Using BIER", draft-ietf-bier-evpn-02 (work in "EVPN BUM Using BIER", draft-ietf-bier-evpn-03 (work in
progress), November 2019. progress), April 2020.
[I-D.ietf-bier-mld] [I-D.ietf-bier-mld]
Pfister, P., Wijnands, I., Venaas, S., Wang, C., Zhang, Pfister, P., Wijnands, I., Venaas, S., Wang, C., Zhang,
Z., and M. Stenberg, "BIER Ingress Multicast Flow Overlay Z., and M. Stenberg, "BIER Ingress Multicast Flow Overlay
using Multicast Listener Discovery Protocols", draft-ietf- using Multicast Listener Discovery Protocols", draft-ietf-
bier-mld-04 (work in progress), March 2020. bier-mld-04 (work in progress), March 2020.
[I-D.ietf-bier-pim-signaling] [I-D.ietf-bier-pim-signaling]
Bidgoli, H., Kotalwar, J., Xu, F., mishra, m., Zhang, Z., Bidgoli, H., Xu, F., Kotalwar, J., Wijnands, I., Mishra,
and A. Dolganow, "PIM Signaling Through BIER Core", draft- M., and Z. Zhang, "PIM Signaling Through BIER Core",
ietf-bier-pim-signaling-08 (work in progress), November draft-ietf-bier-pim-signaling-10 (work in progress), July
2019. 2020.
[I-D.ietf-bier-te-arch] [I-D.ietf-bier-te-arch]
Eckert, T., Cauchie, G., and M. Menth, "Path Engineering Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering
for Bit Index Explicit Replication (BIER-TE)", draft-ietf- for Bit Index Explicit Replication (BIER-TE)", draft-ietf-
bier-te-arch-06 (work in progress), February 2020. bier-te-arch-08 (work in progress), July 2020.
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", draft-ietf- Network Virtualization Encapsulation", draft-ietf-
nvo3-geneve-14 (work in progress), September 2019. nvo3-geneve-16 (work in progress), March 2020.
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"YANG Data Model for OSPF Protocol", draft-ietf-ospf- "YANG Data Model for OSPF Protocol", draft-ietf-ospf-
yang-29 (work in progress), October 2019. yang-29 (work in progress), October 2019.
[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.
[I-D.zhang-bier-bierin6] [I-D.zhang-bier-bierin6]
Zhang, Z., Przygienda, T., Wijnands, I., Bidgoli, H., and Zhang, Z., Zhang, Z., Wijnands, I., Bidgoli, H., and M.
M. McBride, "BIER in IPv6 (BIERin6)", draft-zhang-bier- McBride, "BIER in IPv6 (BIERin6)", draft-zhang-bier-
bierin6-04 (work in progress), January 2020. bierin6-07 (work in progress), July 2020.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC4541] Christensen, M., Kimball, K., and F. Solensky, [RFC4541] Christensen, M., Kimball, K., and F. Solensky,
"Considerations for Internet Group Management Protocol "Considerations for Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) Snooping (IGMP) and Multicast Listener Discovery (MLD) Snooping
Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006, Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006,
<https://www.rfc-editor.org/info/rfc4541>. <https://www.rfc-editor.org/info/rfc4541>.
skipping to change at page 34, line 47 skipping to change at page 35, line 11
] ]
} }
} }
Authors' Addresses Authors' Addresses
Zheng Zhang Zheng Zhang
ZTE Corporation ZTE Corporation
China China
Email: zzhang_ietf@hotmail.com Email: zhang.zheng@zte.com.cn
Cui(Linda) Wang Cui(Linda) Wang
Individual Individual
Australia Australia
Email: lindawangjoy@gmail.com Email: lindawangjoy@gmail.com
Ying Cheng Ying Cheng
China Unicom China Unicom
Beijing Beijing
China China
 End of changes. 36 change blocks. 
218 lines changed or deleted 246 lines changed or added

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