draft-ietf-pim-igmp-mld-snooping-yang-01.txt   draft-ietf-pim-igmp-mld-snooping-yang-02.txt 
PIM Working Group H. Zhao PIM Working Group H. Zhao
Internet Draft Ericsson Internet Draft Ericsson
Intended status: Standards Track X. Liu Intended status: Standards Track X. Liu
Expires: August 23, 2018 Jabil Expires: November 13, 2018 Jabil
Y. Liu Y. Liu
Huawei Huawei
M. Sivakumar M. Sivakumar
Cisco Cisco
A. Peter A. Peter
Individual Individual
February 24, 2018 May 14, 2018
A Yang Data Model for IGMP and MLD Snooping A Yang Data Model for IGMP and MLD Snooping
draft-ietf-pim-igmp-mld-snooping-yang-01.txt draft-ietf-pim-igmp-mld-snooping-yang-02.txt
Abstract Abstract
This document defines a YANG data model that can be used to This document defines a YANG data model that can be used to
configure and manage Internet Group Management Protocol (IGMP) and configure and manage Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) Snooping devices. Multicast Listener Discovery (MLD) Snooping devices.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on August 23, 2018. This Internet-Draft will expire on November 13, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................3
1.1. Terminology...............................................3 1.1. Terminology...............................................3
1.2. Tree Diagrams.............................................3 1.2. Tree Diagrams.............................................3
2. Design of Data Model...........................................3 2. Design of Data Model...........................................4
2.1. Overview..................................................4 2.1. Overview..................................................4
2.2. IGMP and MLD Snooping Instances...........................4 2.2. IGMP Snooping Instances...................................4
2.3. IGMP and MLD Snooping References..........................9 2.3. MLD Snooping Instances....................................7
2.4. Augment /if:interfaces/if:interface......................10 2.4. IGMP and MLD Snooping References..........................9
2.5. IGMP and MLD Snooping RPC................................12 2.5. Augment /if:interfaces/if:interface......................10
2.6. IGMP and MLD Snooping RPC................................12
3. IGMP and MLD Snooping YANG Module.............................13 3. IGMP and MLD Snooping YANG Module.............................13
4. Security Considerations.......................................42 4. Security Considerations.......................................42
5. IANA Considerations...........................................42 5. IANA Considerations...........................................44
6. Normative References..........................................43 6. Normative References..........................................44
Appendix A. Data Tree Example...................................46
Authors' Addresses...............................................52
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for the management This document defines a YANG [RFC6020] data model for the management
of Internet Group Management Protocol (IGMP) and Multicast Listener of Internet Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) Snooping devices. Discovery (MLD) Snooping devices.
This data model follows the Guidelines for YANG Module Authors The YANG model in this document conforms to the Network Management
NMDA)[draft-dsdt-nmda-guidelines-01]. The "Network Management Datastore Architecture defined in [I-D.ietf-netmod-revised-
Datastore Architecture" (NMDA) adds the ability to inspect the datastores]. The "Network Management Datastore Architecture" (NMDA)
current operational values for configuration, allowing clients to use adds the ability to inspect the current operational values for
identical paths for retrieving the configured values and the configuration, allowing clients to use identical paths for retrieving
operational values. the configured values and the operational values.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP 14
14 [RFC2119]. [RFC2119].
The terminology for describing YANG data models is found in[RFC6020]. The terminology for describing YANG data models is found in[RFC6020].
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in this
this document. The meaning of the symbols in these diagrams is as document. The meaning of the symbols in these diagrams is as follows:
follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" means state data (read-only). (read-write), and "ro" means state data (read-only).
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Design of Data Model 2. Design of Data Model
The model covers Considerations for Internet Group Management The model covers Considerations for Internet Group Management Protocol
Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches
Switches [RFC4541]. [RFC4541].
The goal of this document is to define a data model that provides a The goal of this document is to define a data model that provides a
common user interface to IGMP and MLD Snooping. There is very common user interface to IGMP and MLD Snooping. This document provides
information that is designated as "mandatory", providing freedom for freedom for vendors to adapt this data model to their product
vendors to adapt this data model to their respective product implementations.
implementations.
2.1. Overview 2.1. Overview
The IGMP and MLD Snooping YANG module defined in this document has The IGMP and MLD Snooping YANG module defined in this document has all
all the common building blocks for the IGMP and MLD Snooping the common building blocks for the IGMP and MLD Snooping protocol.
protocol.
The YANG module includes IGMP and MLD Snooping instances The YANG module includes IGMP and MLD Snooping instance definition,
definition, instance references in the scenario of BRIDGE, VPLS. The instance reference in the scenario of BRIDGE, L2VPN. The module also
module also includes the RPC methods for clearing the specified IGMP includes the RPC methods for clearing IGMP and MLD Snooping group
and MLD Snooping. tables.
This YANG model follows the Guidelines for YANG Module Authors This YANG model follows the Guidelines for YANG Module Authors (NMDA)
(NMDA) [draft-dsdt-nmda-guidelines-01]. This NMDA ("Network [draft-dsdt-nmda-guidelines-01]. This NMDA ("Network Management
Management Datastore Architecture") architecture provides an Datastore Architecture") architecture provides an architectural
architectural framework for datastores as they are used by network framework for datastores as they are used by network management
management protocols such as NETCONF [RFC6241], RESTCONF [RFC8040] protocols such as NETCONF [RFC6241], RESTCONF [RFC8040] and the YANG
and the YANG [RFC7950] data modeling language.. [RFC7950] data modeling language.
2.2. IGMP and MLD Snooping Instances 2.2. IGMP Snooping Instances
The YANG module defines IGMP and MLD Snooping instance. The instance The YANG module defines igmp-snooping-instance which could be referenced
will be referenced in all kinds of scenarios to configure IGMP and MLD in the BRIDGE or L2VPN scenario to enable IGMP Snooping.
Snooping. The attribute who could be read and written shows
configuration data. The read-only attribute shows state data. The key All the IGMP Snooping related attributes have been defined in the igmp-
attribute is name. snooping-instance. The read-write attribute is configurable data. The
read-only attribute shows state data. The key attribute of the igmp-
snooping-instance is name.
The value of type in igmp-snooping-instance is bridge or l2vpn. When it
is bridge, the igmp-snooping-instance will be referenced in the BRIDGE
scenario. When it is l2vpn, the igmp-snooping-instance will be
referenced in the L2VPN scenario.
The value of bridge-mrouter-interface, l2vpn-mrouter-interface-ac,
l2vpn-mrouter-interface-pw are filled by routing system dynamically.
They are different from static-bridge-mrouter-interface, static-l2vpn-
mrouter-interface-ac, and static-l2vpn-mrouter-interface-pw which are
configured statically.
module: ietf-igmp-mld-snooping module: ietf-igmp-mld-snooping
+--rw igmp-snooping-instances +--rw igmp-snooping-instances
| +--rw igmp-snooping-instance* [name] | +--rw igmp-snooping-instance* [name]
| +--rw name string | +--rw name string
| +--rw type? enumeration | +--rw type? enumeration
skipping to change at page 6, line 27 skipping to change at page 7, line 4
| +--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref | +--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref
| +--ro up-time? uint32 | +--ro up-time? uint32
| +--ro expire? uint32 | +--ro expire? uint32
| +--ro host-count? uint32 {explicit-tracking}? | +--ro host-count? uint32 {explicit-tracking}?
| +--ro last-reporter? inet:ipv4-address | +--ro last-reporter? inet:ipv4-address
| +--ro host* [host-address] {explicit-tracking}? | +--ro host* [host-address] {explicit-tracking}?
| +--ro host-address inet:ipv4-address | +--ro host-address inet:ipv4-address
| +--ro host-filter-mode? enumeration | +--ro host-filter-mode? enumeration
+--rw mld-snooping-instances 2.3. MLD Snooping Instances
| +--rw mld-snooping-instance* [name] The YANG module defines mld-snooping-instance which could be referenced
in the BRIDGE or L2VPN scenario to enable MLD Snooping.
| +--rw name string The mld-snooping-instance is the same as IGMP snooping except changing
IPV4 addresses to IPV6 addresses.
| +--rw type? enumeration module: ietf-igmp-mld-snooping
| +--rw enable? boolean {admin-enable}? +--rw mld-snooping-instances
| +--rw forwarding-mode? enumeration | +--rw mld-snooping-instance* [name]
| +--rw explicit-tracking? boolean {explicit-tracking}? | +--rw name string
| +--rw exclude-lite? boolean {exclude-lite}? | +--rw type? enumeration
| +--rw send-query? boolean | +--rw enable? boolean {admin-enable}?
| +--rw immediate-leave? empty {immediate-leave}? | +--rw forwarding-mode? enumeration
| +--rw last-member-query-interval? uint16
| +--rw query-interval? uint16 | +--rw explicit-tracking? boolean {explicit-
tracking}?
| +--rw query-max-response-time? uint16 | +--rw exclude-lite? boolean {exclude-lite}?
| +--rw require-router-alert? boolean {require-router- | +--rw send-query? boolean
alert}?
| +--rw robustness-variable? uint8 | +--rw immediate-leave? empty {immediate-leave}?
| +--rw version? uint8 | +--rw last-member-query-interval? uint16
| +--rw static-bridge-mrouter-interface* if:interface-ref {static- | +--rw query-interval? uint16
| +--rw query-max-response-time? uint16
| +--rw require-router-alert? boolean {require-router-
alert}?
| +--rw robustness-variable? uint8
| +--rw version? uint8
| +--rw static-bridge-mrouter-interface* if:interface-ref {static-
mrouter-interface}? mrouter-interface}?
| +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref {static- | +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref {static-
mrouter-interface}? mrouter-interface}?
| +--rw static-l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref | +--rw static-l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref
{static-mrouter-interface}? {static-mrouter-interface}?
| +--rw querier-source? inet:ipv6-address | +--rw querier-source? inet:ipv6-address
| +--rw static-l2-multicast-group* [group source-addr] {static-l2- | +--rw static-l2-multicast-group* [group source-addr] {static-l2-
multicast-group}? multicast-group}?
| | +--rw group inet:ipv6-address | | +--rw group inet:ipv6-address
| | +--rw source-addr source-ipv6-addr-type | | +--rw source-addr source-ipv6-addr-type
| | +--rw bridge-outgoing-interface* if:interface-ref | | +--rw bridge-outgoing-interface* if:interface-ref
| | +--rw l2vpn-outgoing-ac* l2vpn-instance-ac-ref | | +--rw l2vpn-outgoing-ac* l2vpn-instance-ac-ref
| | +--rw l2vpn-outgoing-pw* l2vpn-instance-pw-ref | | +--rw l2vpn-outgoing-pw* l2vpn-instance-pw-ref
| +--ro entries-count? uint32 | +--ro entries-count? uint32
| +--ro bridge-mrouter-interface* if:interface-ref | +--ro bridge-mrouter-interface* if:interface-ref
| +--ro l2vpn-mrouter-interface-ac* if:interface-ref | +--ro l2vpn-mrouter-interface-ac* if:interface-ref
| +--ro l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref | +--ro l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref
| +--ro group* [address] | +--ro group* [address]
| +--ro address inet:ipv6-address | +--ro address inet:ipv6-address
| +--ro mac-address? yang:phys-address | +--ro mac-address? yang:phys-address
| +--ro expire? uint32
| +--ro up-time? uint32 | +--ro expire? uint32
| +--ro last-reporter? inet:ipv6-address | +--ro up-time? uint32
| +--ro source* [address] | +--ro last-reporter? inet:ipv6-address
| +--ro address inet:ipv6-address | +--ro source* [address]
| +--ro bridge-outgoing-interface* if:interface-ref | +--ro address inet:ipv6-address
| +--ro bridge-outgoing-interface* if:interface-ref
| +--ro l2vpn-outgoing-ac* l2vpn-instance-ac-ref | +--ro l2vpn-outgoing-ac* l2vpn-instance-ac-ref
| +--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref | +--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref
| +--ro up-time? uint32 | +--ro up-time? uint32
| +--ro expire? uint32 | +--ro expire? uint32
| +--ro host-count? uint32 {explicit-tracking}? | +--ro host-count? uint32 {explicit-tracking}?
| +--ro last-reporter? inet:ipv6-address | +--ro last-reporter? inet:ipv6-address
| +--ro host* [host-address] {explicit-tracking}? | +--ro host* [host-address] {explicit-tracking}?
| +--ro host-address inet:ipv6-address | +--ro host-address inet:ipv6-address
| +--ro host-filter-mode? Enumeration | +--ro host-filter-mode? enumeration
2.3. IGMP and MLD Snooping References 2.4. IGMP and MLD Snooping References
The IGMP and MLD Snooping instance could be referenced in the scenario The igmp-snooping-instance could be referenced in the scenario of BRIDGE
of bridge, L2VPN to configure the IGMP and MLD Snooping. The name of the or L2VPN to configure the IGMP Snooping. The name of the instance is the
instance is the key attribute. key attribute.
When the igmp-snooping-instance is referenced under the bridge view, it
means IGMP Snooping is enabled in the whole bridge. When the igmp-
snooping-instance is referenced under the VLAN view, it means IGMP
Snooping is enabled in the certain VLAN of the bridge.
The mld-snooping-instance could be referenced in concurrence with igmp-
snooping-instance to configure the MLD Snooping.
+--rw bridges +--rw bridges
| +--rw bridge* [name] | +--rw bridge* [name]
| +--rw name name-type | +--rw name name-type
| +--rw igmp-snooping-instance? igmp-snooping-instance-ref | +--rw igmp-snooping-instance? igmp-snooping-instance-ref
| +--rw mld-snooping-instance? mld-snooping-instance-ref | +--rw mld-snooping-instance? mld-snooping-instance-ref
skipping to change at page 10, line 5 skipping to change at page 10, line 24
+--rw l2vpn-instances +--rw l2vpn-instances
+--rw l2vpn-instance* [name] +--rw l2vpn-instance* [name]
+--rw name string +--rw name string
+--rw igmp-snooping-instance? igmp-snooping-instance-ref +--rw igmp-snooping-instance? igmp-snooping-instance-ref
+--rw mld-snooping-instance? mld-snooping-instance-ref +--rw mld-snooping-instance? mld-snooping-instance-ref
2.4. Augment /if:interfaces/if:interface 2.5. Augment /if:interfaces/if:interface
Augment /if:interfaces/if:interface then add the IGMP MLD SNOOPING This model augment /if:interfaces/if:interface and then add the IGMP and
related attributes under it. It includes enable, version, static- MLD Snooping related attributes under it. The attributes include enable,
mrouter-interface, etc. version, etc.
The static-mrouter-interface and static-l2-multicast-group could be
configured statically under the /if:interfaces/if:interface/ims:igmp-
mld-snooping view. Meanwhile, you can configure them under the IGMP and
MLD Snooping instance view.
The attributes under the statistics are read-only. They show the
statistics of IGMP and MLD Snooping related packets.
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw igmp-mld-snooping +--rw igmp-mld-snooping
+--rw enable? boolean {admin-enable}? +--rw enable? boolean {admin-enable}?
+--rw version? uint8 +--rw version? uint8
+--rw type? enumeration +--rw type? enumeration
skipping to change at page 10, line 41 skipping to change at page 11, line 20
| +--:(l2vpn) | +--:(l2vpn)
| +--rw l2vpn-instance-name? string | +--rw l2vpn-instance-name? string
+--rw static-l2-multicast-group +--rw static-l2-multicast-group
| +--rw (static-l2-multicast-group)? | +--rw (static-l2-multicast-group)?
| +--:(bridge) | +--:(bridge)
| | +--rw bridgename? string | | +--rw bridge-name? string
| | +--rw bridge-group-v4* [address] | | +--rw bridge-group-v4* [group source-addr]
| | | +--rw address inet:ipv4-address | | | +--rw group inet:ipv4-address
| | | +--rw source* inet:ipv4-address | | | +--rw source-addr source-ipv4-addr-type
| | | +--rw vlan-id* uint32 | | | +--rw vlan-id* uint32
| | +--rw bridge-group-v6* [address] | | +--rw bridge-group-v6* [group source-addr]
| | +--rw address inet:ipv6-address
| | +--rw source* inet:ipv6-address | | +--rw group inet:ipv6-address
| | +--rw vlan-id* uint32 | | +--rw source-addr source-ipv6-addr-type
| | +--rw vlan-id* uint32
| +--:(l2vpn) | +--:(l2vpn)
| +--rw l2vpn-group-v4* [address] | +--rw l2vpn-group-v4* [group source-addr]
| | +--rw address inet:ipv4-address | | +--rw group inet:ipv4-address
| | +--rw source* inet:ipv4-address | | +--rw source-addr source-ipv4-addr-type
| | +--rw l2vpn-instance-name? string | | +--rw l2vpn-instance-name? string
| +--rw l2vpn-group-v6* [address] | +--rw l2vpn-group-v6* [group source-addr]
| +--rw address inet:ipv6-address
| +--rw source* inet:ipv6-address | +--rw group inet:ipv6-address
| +--rw source-addr source-ipv6-addr-type
| +--rw l2vpn-instance-name? string | +--rw l2vpn-instance-name? string
+--ro statistics +--ro statistics
+--ro received +--ro received
| +--ro query? yang:counter64 | +--ro query? yang:counter64
| +--ro membership-report-v1? yang:counter64 | +--ro membership-report-v1? yang:counter64
skipping to change at page 12, line 4 skipping to change at page 12, line 31
| +--ro pim? yang:counter64 | +--ro pim? yang:counter64
+--ro sent +--ro sent
+--ro query? yang:counter64 +--ro query? yang:counter64
+--ro membership-report-v1? yang:counter64 +--ro membership-report-v1? yang:counter64
+--ro membership-report-v2? yang:counter64 +--ro membership-report-v2? yang:counter64
+--ro membership-report-v3? yang:counter64 +--ro membership-report-v3? yang:counter64
+--ro leave? yang:counter64 +--ro leave? yang:counter64
+--ro non-member-leave? yang:counter64 +--ro non-member-leave? yang:counter64
+--ro pim? yang:counter64 +--ro pim? yang:counter64
2.5. IGMP and MLD Snooping RPC 2.6. IGMP and MLD Snooping RPC
IGMP and MLD Snooping RPC clears the specified IGMP and MLD Snooping IGMP and MLD Snooping RPC clears the specified IGMP and MLD Snooping
group tables. group tables.
rpcs: rpcs:
+---x clear-igmp-snooping-groups {rpc-clear-groups}? +---x clear-igmp-snooping-groups {rpc-clear-groups}?
| +---w input | +---w input
| +---w name? string | +---w name? string
| +---w group? inet:ipv4-address | +---w group? inet:ipv4-address
| +---w source? inet:ipv4-address | +---w source? inet:ipv4-address
+---x clear-mld-snooping-groups {rpc-clear-groups}? +---x clear-mld-snooping-groups {rpc-clear-groups}?
+---w input +---w input
+---w name? string +---w name? string
+---w group? inet:ipv6-address +---w group? inet:ipv6-address
+---w source? inet:ipv6-address +---w source? inet:ipv6-address
3. IGMP and MLD Snooping YANG Module 3. IGMP and MLD Snooping YANG Module
<CODE BEGINS> file "ietf-igmp-mld-snooping@2018-02-26.yang" <CODE BEGINS> file ietf-igmp-mld-snooping@2018-05-03.yang
module ietf-igmp-mld-snooping { module ietf-igmp-mld-snooping {
namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping"; namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping";
// replace with IANA namespace when assigned // replace with IANA namespace when assigned
prefix ims; prefix ims;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix inet;
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
skipping to change at page 13, line 40 skipping to change at page 13, line 44
prefix "ni"; prefix "ni";
} }
organization organization
"IETF PIM Working Group"; "IETF PIM Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/pim/> "WG Web: <http://tools.ietf.org/wg/pim/>
WG List: <mailto:pim@ietf.org> WG List: <mailto:pim@ietf.org>
WG Chair: Stig Venaas
<mailto:stig@venaas.com>
WG Chair: Mike McBride
<mailto:Michael.McBride@huawei.com>
Editors: Hongji Zhao Editors: Hongji Zhao
<mailto:hongji.zhao@ericsson.com> <mailto:hongji.zhao@ericsson.com>
Xufeng Liu Xufeng Liu
<mailto:Xufeng_Liu@jabil.com> <mailto:xufeng.liu.ietf@gmail.com>
Yisong Liu Yisong Liu
<mailto:liuyisong@huawei.com> <mailto:liuyisong@huawei.com>
Anish Peter Anish Peter
<mailto:anish.ietf@gmail.com> <mailto:anish.ietf@gmail.com>
Mahesh Sivakumar Mahesh Sivakumar
<mailto:masivaku@cisco.com> <mailto:sivakumar.mahesh@gmail.com>
"; ";
description description
"The module defines a collection of YANG definitions common for "The module defines a collection of YANG definitions common for
IGMP and MLD Snooping."; all Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) Snooping devices.
revision 2018-02-26 {
description
"augment /if:interfaces/if:interface";
reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
}
revision 2017-10-24 { Copyright (c) 2018 IETF Trust and the persons identified as
description authors of the code. All rights reserved.
"Change model definition to fit NMDA standard.";
reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
}
revision 2017-08-14 { Redistribution and use in source and binary forms, with or
description without modification, is permitted pursuant to, and subject to
"using profile to cooperate with ieee-dot1Q-bridge module"; the license terms contained in, the Simplified BSD License set
reference forth in Section 4.c of the IETF Trust's Legal Provisions
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping"; Relating to IETF Documents
} (http://trustee.ietf.org/license-info).
revision 2017-06-28 { This version of this YANG module is part of RFC XXXX; see the
description RFC itself for full legal notices.";
"augment /rt:routing/rt:control-plane-protocols
augment /rt:routing-state/rt:control-plane-protocols";
reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
}
revision 2017-02-05 { revision 2018-05-03 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping"; "RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
} }
/* /*
* Features * Features
*/ */
feature admin-enable { feature admin-enable {
description description
"Support configuration to enable or disable IGMP and MLD "Support configuration to enable or disable IGMP and MLD
Snooping."; Snooping.";
} }
skipping to change at page 17, line 8 skipping to change at page 16, line 46
type leafref { type leafref {
path "/mld-snooping-instances/mld-snooping-instance/name"; path "/mld-snooping-instances/mld-snooping-instance/name";
} }
description description
"This type is used by data models that need to reference mld "This type is used by data models that need to reference mld
snooping instance."; snooping instance.";
} }
typedef l2vpn-instance-ac-ref { typedef l2vpn-instance-ac-ref {
type leafref { type leafref {
path "/ni:network-instances/ni:network-instance/l2vpn:endpoint/l2vpn:name"; path "/ni:network-instances/ni:network-instance/l2vpn:endpoint/l2vpn:name";
} }
description "l2vpn-instance-ac-ref"; description "l2vpn-instance-ac-ref";
} }
typedef l2vpn-instance-pw-ref { typedef l2vpn-instance-pw-ref {
type leafref { type leafref {
path "/ni:network-instances/ni:network-instance/l2vpn:endpoint/l2vpn:name"; path "/ni:network-instances/ni:network-instance/l2vpn:endpoint/l2vpn:name";
} }
description "l2vpn-instance-pw-ref"; description "l2vpn-instance-pw-ref";
} }
typedef source-ipv4-addr-type { typedef source-ipv4-addr-type {
type union { type union {
type enumeration { type enumeration {
enum '*' { enum '*' {
description description
"Any source address."; "Any source address.";
} }
} }
type inet:ipv4-address; type inet:ipv4-address;
} }
description description
"Multicast source IP address type."; "Multicast source IPV4 address type.";
} // source-ipv4-addr-type } // source-ipv4-addr-type
typedef source-ipv6-addr-type { typedef source-ipv6-addr-type {
type union { type union {
type enumeration { type enumeration {
enum '*' { enum '*' {
description description
"Any source address."; "Any source address.";
} }
} }
type inet:ipv6-address; type inet:ipv6-address;
} }
description description
"Multicast source IP address type."; "Multicast source IPV6 address type.";
} // source-ipv6-addr-type } // source-ipv6-addr-type
/* /*
* Identities * Identities
*/ */
/* /*
* Groupings * Groupings
*/ */
grouping general-state-attributes { grouping general-state-attributes {
skipping to change at page 18, line 41 skipping to change at page 18, line 27
grouping instance-config-attributes-igmp-snooping { grouping instance-config-attributes-igmp-snooping {
description "IGMP snooping configuration for each VLAN or l2vpn description "IGMP snooping configuration for each VLAN or l2vpn
instance or EVPN instance."; instance or EVPN instance.";
uses instance-config-attributes-igmp-mld-snooping; uses instance-config-attributes-igmp-mld-snooping;
leaf querier-source { leaf querier-source {
type inet:ipv4-address; type inet:ipv4-address;
description "Use the IGMP snooping querier to support IGMP description "Use the IGMP snooping querier to support IGMP
snooping in a VLAN where PIM and IGMP are not configured. snooping in a VLAN where PIM and IGMP are not configured.
The IP address is used as the source address in The IPV4 address is used as the source address in
messages."; messages.";
} }
list static-l2-multicast-group { list static-l2-multicast-group {
if-feature static-l2-multicast-group; if-feature static-l2-multicast-group;
key "group source-addr"; key "group source-addr";
description description
"A static multicast route, (*,G) or (S,G)."; "A static multicast route, (*,G) or (S,G).";
leaf group { leaf group {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IP address"; "Multicast group IPV4 address";
} }
leaf source-addr { leaf source-addr {
type source-ipv4-addr-type; type source-ipv4-addr-type;
description description
"Multicast source IP address."; "Multicast source IPV4 address.";
} }
leaf-list bridge-outgoing-interface { leaf-list bridge-outgoing-interface {
when "../../type = 'bridge'"; when "../../type = 'bridge'";
type if:interface-ref; type if:interface-ref;
description "Outgoing interface in bridge fowarding"; description "Outgoing interface in bridge fowarding";
} }
leaf-list l2vpn-outgoing-ac { leaf-list l2vpn-outgoing-ac {
when "../../type = 'l2vpn'"; when "../../type = 'l2vpn'";
type l2vpn-instance-ac-ref; type l2vpn-instance-ac-ref;
description "Outgoing ac in l2vpn fowarding"; description "Outgoing AC in L2VPN fowarding";
} }
leaf-list l2vpn-outgoing-pw { leaf-list l2vpn-outgoing-pw {
when "../../type = 'l2vpn'"; when "../../type = 'l2vpn'";
type l2vpn-instance-pw-ref; type l2vpn-instance-pw-ref;
description "Outgoing pw in l2vpn fowarding"; description "Outgoing PW in L2VPN fowarding";
} }
} // static-l2-multicast-group } // static-l2-multicast-group
} // instance-config-attributes-igmp-snooping } // instance-config-attributes-igmp-snooping
grouping instance-config-attributes-igmp-mld-snooping { grouping instance-config-attributes-igmp-mld-snooping {
description description
"IGMP and MLD Snooping configuration of each VLAN."; "IGMP and MLD Snooping configuration of each VLAN.";
leaf enable { leaf enable {
if-feature admin-enable; if-feature admin-enable;
type boolean; type boolean;
default false;
description description
"Set the value to true to enable IGMP and MLD Snooping in "Set the value to true to enable IGMP and MLD Snooping in
the VLAN instance."; the VLAN instance.";
} }
leaf forwarding-mode { leaf forwarding-mode {
type enumeration { type enumeration {
enum "mac" { enum "mac" {
description description
""; "MAC-based lookup mode";
} }
enum "ip" { enum "ip" {
description description
""; "IP-based lookup mode";
} }
} }
default "ip";
description "The default forwarding mode for IGMP and MLD description "The default forwarding mode for IGMP and MLD
Snooping is ip. Snooping is ip.
cisco command is as below cisco command is as below
Router(config-vlan-config)# multicast snooping lookup Router(config-vlan-config)# multicast snooping lookup
{ ip | mac } "; { ip | mac } ";
} }
leaf explicit-tracking { leaf explicit-tracking {
if-feature explicit-tracking; if-feature explicit-tracking;
type boolean; type boolean;
default false;
description "Tracks IGMP & MLD Snooping v3 membership reports description "Tracks IGMP & MLD Snooping v3 membership reports
from individual hosts for each port of each VLAN or VSI."; from individual hosts.
It contributes to saving network resources and
shortening leave latency.";
} }
leaf exclude-lite { leaf exclude-lite {
if-feature exclude-lite; if-feature exclude-lite;
type boolean; type boolean;
default false;
description description
"lightweight IGMPv3 and MLDv2 protocols, which simplify the "lightweight IGMPv3 and MLDv2 protocols, which simplify the
standard versions of IGMPv3 and MLDv2."; standard versions of IGMPv3 and MLDv2.";
reference "RFC5790"; reference "RFC5790";
} }
leaf send-query { leaf send-query {
type boolean; type boolean;
default true; default true;
description "Enable quick response for topo changes. description "Enable quick response for topo changes.
skipping to change at page 22, line 4 skipping to change at page 21, line 48
description description
"Query maximum response time specifies the maximum time "Query maximum response time specifies the maximum time
allowed before sending a responding report."; allowed before sending a responding report.";
reference "RFC3376. Sec. 4.1.1, 8.3, 8.14.3."; reference "RFC3376. Sec. 4.1.1, 8.3, 8.14.3.";
} }
leaf require-router-alert { leaf require-router-alert {
if-feature require-router-alert; if-feature require-router-alert;
type boolean; type boolean;
default false; default false;
description description
"When the value is true, router alert exists in the IP head "When the value is true, router alert should exist in the IP
of IGMP or MLD packet."; head of IGMP or MLD packet.";
} }
leaf robustness-variable { leaf robustness-variable {
type uint8 { type uint8 {
range "2..7"; range "1..7";
} }
default 2; default 2;
description description
"Querier's Robustness Variable allows tuning for the "Querier's Robustness Variable allows tuning for the
expected expected
packet loss on a network."; packet loss on a network.";
reference "RFC3376. Sec. 4.1.6, 8.1, 8.14.1."; reference "RFC3376. Sec. 4.1.6, 8.1, 8.14.1.";
} }
leaf version { leaf version {
skipping to change at page 23, line 21 skipping to change at page 23, line 16
grouping instance-config-attributes-mld-snooping { grouping instance-config-attributes-mld-snooping {
description "MLD snooping configuration of each VLAN."; description "MLD snooping configuration of each VLAN.";
uses instance-config-attributes-igmp-mld-snooping; uses instance-config-attributes-igmp-mld-snooping;
leaf querier-source { leaf querier-source {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Use the MLD snooping querier to support MLD snooping where PIM "Use the MLD snooping querier to support MLD snooping where PIM
and MLD are not configured. and MLD are not configured.
The IP address is used as the source address in messages."; The IPV6 address is used as the source address in messages.";
} }
list static-l2-multicast-group { list static-l2-multicast-group {
if-feature static-l2-multicast-group; if-feature static-l2-multicast-group;
key "group source-addr"; key "group source-addr";
description description
"A static multicast route, (*,G) or (S,G)."; "A static multicast route, (*,G) or (S,G).";
leaf group { leaf group {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast group IP address"; "Multicast group IPV6 address";
} }
leaf source-addr { leaf source-addr {
type source-ipv6-addr-type; type source-ipv6-addr-type;
description description
"Multicast source IP address."; "Multicast source IPV6 address.";
} }
leaf-list bridge-outgoing-interface { leaf-list bridge-outgoing-interface {
when "../../type = 'bridge'"; when "../../type = 'bridge'";
type if:interface-ref; type if:interface-ref;
description "Outgoing interface in bridge fowarding"; description "Outgoing interface in bridge fowarding";
} }
leaf-list l2vpn-outgoing-ac { leaf-list l2vpn-outgoing-ac {
when "../../type = 'l2vpn'"; when "../../type = 'l2vpn'";
type l2vpn-instance-ac-ref; type l2vpn-instance-ac-ref;
description "Outgoing ac in l2vpn fowarding"; description "Outgoing AC in L2VPN fowarding";
} }
leaf-list l2vpn-outgoing-pw { leaf-list l2vpn-outgoing-pw {
when "../../type = 'l2vpn'"; when "../../type = 'l2vpn'";
type l2vpn-instance-pw-ref; type l2vpn-instance-pw-ref;
description "Outgoing pw in l2vpn fowarding"; description "Outgoing PW in L2VPN fowarding";
} }
} // static-l2-multicast-group } // static-l2-multicast-group
} // instance-config-attributes-mld-snooping } // instance-config-attributes-mld-snooping
grouping instance-state-group-attributes-igmp-mld-snooping { grouping instance-state-group-attributes-igmp-mld-snooping {
description description
"Attributes for both IGMP and MLD snooping groups."; "Attributes for both IGMP and MLD snooping groups.";
leaf mac-address { leaf mac-address {
type yang:phys-address; type yang:phys-address;
description "Destination mac address for L2 multicast description "Destination MAC address for L2 multicast
forwarding."; forwarding.";
} }
leaf expire { leaf expire {
type uint32; type uint32;
units seconds; units seconds;
description description
"The time left before multicast group timeout."; "The time left before multicast group timeout.";
} }
leaf up-time { leaf up-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"The time after the device created L2 multicast record."; "The time elapsed since the device created L2 multicast
record.";
} }
} // instance-state-group-attributes-igmp-mld-snooping } // instance-state-group-attributes-igmp-mld-snooping
grouping instance-state-attributes-igmp-snooping { grouping instance-state-attributes-igmp-snooping {
description description
"State attributes for IGMP snooping for each VLAN or l2vpn "State attributes for IGMP snooping for each VLAN or l2vpn
instance or EVPN instance."; instance or EVPN instance.";
skipping to change at page 25, line 4 skipping to change at page 24, line 46
} // instance-state-group-attributes-igmp-mld-snooping } // instance-state-group-attributes-igmp-mld-snooping
grouping instance-state-attributes-igmp-snooping { grouping instance-state-attributes-igmp-snooping {
description description
"State attributes for IGMP snooping for each VLAN or l2vpn "State attributes for IGMP snooping for each VLAN or l2vpn
instance or EVPN instance."; instance or EVPN instance.";
uses instance-state-attributes-igmp-mld-snooping; uses instance-state-attributes-igmp-mld-snooping;
list group { list group {
key "address"; key "address";
config false; config false;
description "IGMP snooping information"; description "IGMP snooping information";
leaf address { leaf address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IP address"; "Multicast group IPV4 address";
} }
uses instance-state-group-attributes-igmp-mld-snooping; uses instance-state-group-attributes-igmp-mld-snooping;
leaf last-reporter { leaf last-reporter {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The last host address which has sent the "Address of the last host which has sent report to join
report to join the multicast group."; the multicast group.";
} }
list source { list source {
key "address"; key "address";
description "Source IP address for multicast stream"; description "Source IPV4 address for multicast stream";
leaf address { leaf address {
type inet:ipv4-address; type inet:ipv4-address;
description "Source IP address for multicast stream"; description "Source IPV4 address for multicast stream";
} }
uses instance-state-source-attributes-igmp-mld-snooping; uses instance-state-source-attributes-igmp-mld-snooping;
leaf last-reporter { leaf last-reporter {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The last host address which has sent the "Address of the last host which has sent report to join
report to join the multicast source and group."; the multicast group.";
} }
list host { list host {
if-feature explicit-tracking; if-feature explicit-tracking;
key "host-address"; key "host-address";
description description
"List of multicast membership hosts "List of multicast membership hosts
of the specific multicast source-group."; of the specific multicast source-group.";
leaf host-address { leaf host-address {
skipping to change at page 27, line 41 skipping to change at page 27, line 35
key "address"; key "address";
config false; config false;
description "MLD snooping statistics information"; description "MLD snooping statistics information";
leaf address { leaf address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast group IP address"; "Multicast group IPV6 address";
} }
uses instance-state-group-attributes-igmp-mld-snooping; uses instance-state-group-attributes-igmp-mld-snooping;
leaf last-reporter { leaf last-reporter {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The last host address which has sent the "Address of the last host which has sent report to join
report to join the multicast group."; the multicast group.";
} }
list source { list source {
key "address"; key "address";
description "Source IP address for multicast stream"; description "Source IPV6 address for multicast stream";
leaf address { leaf address {
type inet:ipv6-address; type inet:ipv6-address;
description "Source IP address for multicast stream"; description "Source IPV6 address for multicast stream";
} }
uses instance-state-source-attributes-igmp-mld-snooping; uses instance-state-source-attributes-igmp-mld-snooping;
leaf last-reporter { leaf last-reporter {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The last host address which has sent the report to join "Address of the last host which has sent report to join
the multicast source and group."; the multicast group.";
} }
list host { list host {
if-feature explicit-tracking; if-feature explicit-tracking;
key "host-address"; key "host-address";
description description
"List of multicast membership hosts "List of multicast membership hosts
of the specific multicast source-group."; of the specific multicast source-group.";
leaf host-address { leaf host-address {
skipping to change at page 29, line 22 skipping to change at page 29, line 17
leaf-list bridge-outgoing-interface { leaf-list bridge-outgoing-interface {
when "../../../type = 'bridge'"; when "../../../type = 'bridge'";
type if:interface-ref; type if:interface-ref;
description "Outgoing interface in bridge fowarding"; description "Outgoing interface in bridge fowarding";
} }
leaf-list l2vpn-outgoing-ac { leaf-list l2vpn-outgoing-ac {
when "../../../type = 'l2vpn'"; when "../../../type = 'l2vpn'";
type l2vpn-instance-ac-ref; type l2vpn-instance-ac-ref;
description "Outgoing ac in l2vpn fowarding"; description "Outgoing AC in L2VPN fowarding";
} }
leaf-list l2vpn-outgoing-pw { leaf-list l2vpn-outgoing-pw {
when "../../../type = 'l2vpn'"; when "../../../type = 'l2vpn'";
type l2vpn-instance-pw-ref; type l2vpn-instance-pw-ref;
description "Outgoing pw in l2vpn fowarding"; description "Outgoing PW in L2VPN fowarding";
} }
leaf up-time { leaf up-time {
type uint32; type uint32;
units seconds; units seconds;
description "The time after the device created L2 multicast description "The time elapsed since the device created L2
record"; multicast record";
} }
leaf expire { leaf expire {
type uint32; type uint32;
units seconds; units seconds;
description description
"The time left before multicast group timeout."; "The time left before multicast group timeout.";
} }
leaf host-count { leaf host-count {
skipping to change at page 36, line 45 skipping to change at page 36, line 39
description "Augment interface for referencing attributes which description "Augment interface for referencing attributes which
only fit for interface view."; only fit for interface view.";
container igmp-mld-snooping { container igmp-mld-snooping {
description description
"igmp-mld-snooping related attributes under interface view"; "igmp-mld-snooping related attributes under interface view";
leaf enable { leaf enable {
if-feature admin-enable; if-feature admin-enable;
type boolean; type boolean;
default false;
description description
"Set the value to true to enable IGMP and MLD Snooping in "Set the value to true to enable IGMP and MLD Snooping in
the VLAN instance."; the VLAN instance.";
} }
leaf version { leaf version {
type uint8 { type uint8 {
range "1..3"; range "1..3";
} }
description "IGMP and MLD Snooping version."; description "IGMP and MLD Snooping version.";
skipping to change at page 37, line 29 skipping to change at page 37, line 24
container static-mrouter-interface { container static-mrouter-interface {
description description
"Container for choice static-mrouter-interface"; "Container for choice static-mrouter-interface";
choice static-mrouter-interface { choice static-mrouter-interface {
description description
"Configure static multicast router interface under the "Configure static multicast router interface under the
interface view"; interface view";
case bridge { case bridge {
when "type = 'bridge'" { when "../type = 'bridge'" {
description description
"Applies to bridge scenario."; "Applies to bridge scenario.";
} }
description description
"Applies to bridge scenario."; "Applies to bridge scenario.";
leaf bridge-name { leaf bridge-name {
type string; type string;
description description
"bridge name."; "The name for a bridge. Each interface
belongs to only one bridge.";
} }
leaf-list vlan-id { leaf-list vlan-id {
type uint32; type uint32;
description description
"vlan id."; "The vlan ids for bridge. If you don't
specify vlan id here, the interface serves as the mrouter interface for
all the vlans in this bridge.";
} }
} }
case l2vpn { case l2vpn {
when "type = 'l2vpn'" { when "../type = 'l2vpn'" {
description description
"Applies to l2vpn scenario."; "Applies to l2vpn scenario.";
} }
description description
"Applies to l2vpn scenario."; "Applies to l2vpn scenario.";
leaf l2vpn-instance-name { leaf l2vpn-instance-name {
type string; type string;
description description
"The l2vpn instance name applied in the "The l2vpn instance name applied in the
skipping to change at page 38, line 29 skipping to change at page 38, line 28
container static-l2-multicast-group { container static-l2-multicast-group {
description description
"Container for static-l2-multicast-group"; "Container for static-l2-multicast-group";
choice static-l2-multicast-group { choice static-l2-multicast-group {
description description
"Configure static l2 multicast group under the "Configure static l2 multicast group under the
interface view"; interface view";
case bridge { case bridge {
when "type = 'bridge'" { when "../type = 'bridge'" {
description description
"Applies to bridge scenario."; "Applies to bridge scenario.";
} }
description description
"Applies to bridge scenario."; "Applies to bridge scenario.";
leaf bridgename { leaf bridge-name {
type string; type string;
description description
"bridge name."; "bridge name.";
} }
list bridge-group-v4 { list bridge-group-v4 {
key "address"; key "group source-addr";
description
description ""; "A static multicast route, (*,G) or (S,G).";
leaf address { leaf group {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IPV4 address"; "Multicast group IPV4 address";
} }
leaf source-addr {
leaf-list source { type source-ipv4-addr-type;
type inet:ipv4-address; description
description "Source IPV4 address for multicast "Multicast source IPV4 address.";
stream";
} }
leaf-list vlan-id { leaf-list vlan-id {
type uint32; type uint32;
description description
"vlan id."; "vlan id.";
} }
} }
list bridge-group-v6 { list bridge-group-v6 {
key "address"; key "group source-addr";
description ""; description
leaf address { "A static multicast route, (*,G) or (S,G).";
leaf group {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast group IPv6 address"; "Multicast group IPV6 address";
} }
leaf-list source { leaf source-addr {
type inet:ipv6-address; type source-ipv6-addr-type;
description "Source IPv6 address for multicast description
stream"; "Multicast source IPV6 address.";
} }
leaf-list vlan-id { leaf-list vlan-id {
type uint32; type uint32;
description description
"vlan id."; "vlan id.";
} }
} }
} }
case l2vpn { case l2vpn {
when "type = 'l2vpn'" { when "../type = 'l2vpn'" {
description description
"Applies to l2vpn scenario."; "Applies to l2vpn scenario.";
} }
description description
"Applies to l2vpn scenario."; "Applies to l2vpn scenario.";
list l2vpn-group-v4 { list l2vpn-group-v4 {
key "address"; key "group source-addr";
description ""; description "A static multicast route, (*,G) or
leaf address { (S,G).";
leaf group {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IP address"; "Multicast group IPV4 address";
} }
leaf-list source { leaf source-addr {
type inet:ipv4-address; type source-ipv4-addr-type;
description "Source IP address for multicast description
stream"; "Multicast source IPV4 address.";
} }
leaf l2vpn-instance-name { leaf l2vpn-instance-name {
type string; type string;
description description
"The l2vpn instance name applied in the "The l2vpn instance name applied in the
interface"; interface";
} }
} }
list l2vpn-group-v6 { list l2vpn-group-v6 {
key "address";
description "";
leaf address { key "group source-addr";
description
"A static multicast route, (*,G) or (S,G).";
leaf group {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast group IP address"; "Multicast group IPV6 address";
} }
leaf-list source { leaf source-addr {
type inet:ipv6-address; type source-ipv6-addr-type;
description "Source IP address for multicast description
stream"; "Multicast source IPV6 address.";
} }
leaf l2vpn-instance-name { leaf l2vpn-instance-name {
type string; type string;
description description
"The l2vpn instance name applied in the "The l2vpn instance name applied in the
interface"; interface";
} }
} }
} }
} //choice static-l2-multicast-group } //choice static-l2-multicast-group
} // container static-l2-multicast-group } // container static-l2-multicast-group
container statistics { container statistics {
config false; config false;
skipping to change at page 42, line 43 skipping to change at page 42, line 48
tables are tables are
cleared."; cleared.";
} }
} }
} // rpc clear-mld-snooping-groups } // rpc clear-mld-snooping-groups
} }
<CODE ENDS> <CODE ENDS>
4. Security Considerations 4. Security Considerations
The data model defined does not create any security implications. The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) to
these data nodes without proper protection can have a negative effect
on network operations. These are the subtrees and data nodes and
their sensitivity/vulnerability:
/ims:igmp-snooping-instances/ims:igmp-snooping-instance
/ims:mld-snooping-instances/ims:mld-snooping-instance
/if:interfaces/if:interface/ims:igmp-mld-snooping
Unauthorized access to any data node of these subtrees can adversely
affect the IGMP & MLD Snooping subsystem of both the local device and
the network. This may lead to network malfunctions, delivery of
packets to inappropriate destinations, and other problems.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/ims:igmp-snooping-instances/ims:igmp-snooping-instance
/ims:mld-snooping-instances/ims:mld-snooping-instance
/if:interfaces/if:interface/ims:igmp-mld-snooping
Unauthorized access to any data node of these subtrees can disclose
the operational state information of IGMP & MLD Snooping on this
device.
Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. The IGMP & MLD
Snooping Yang module support the "clear-igmp-snooping-groups" and "
clear-mld-snooping-groups" RPCs. If it meets unauthorized RPC
operation invocation, the IGMP and MLD Snooping group tables will be
cleared unexpectedly.
5. IANA Considerations 5. IANA Considerations
This draft does not request any IANA action. RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML
registry [RFC3688]:
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG
Module Names registry [RFC7950]:
--------------------------------------------------------------------
name: ietf-igmp-mld-snooping
namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping
prefix: ims
reference: RFC XXXX
--------------------------------------------------------------------
6. Normative References 6. Normative References
[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,
October 2010. October 2010.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021, [RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021,
October 2010. October 2010.
skipping to change at page 44, line 28 skipping to change at page 46, line 20
[draft-ietf-bess-evpn-yang-02] P.Brissette, A. Sajassi, H. Shah, Z. [draft-ietf-bess-evpn-yang-02] P.Brissette, A. Sajassi, H. Shah, Z.
Li, H. Chen, K. Tiruveedhula, I. Hussain, J. Rabadan, "Yang Li, H. Chen, K. Tiruveedhula, I. Hussain, J. Rabadan, "Yang
Data Model for EVPN", draft-ietf-bess-evpn-yang-02, March Data Model for EVPN", draft-ietf-bess-evpn-yang-02, March
13, 2017 13, 2017
[draft-ietf-bess-l2vpn-yang-06] H. Shah, P. Brissette, I. Chen, I. [draft-ietf-bess-l2vpn-yang-06] H. Shah, P. Brissette, I. Chen, I.
Hussain, B. Wen, K. Tiruveedhula, "YANG Data Model for Hussain, B. Wen, K. Tiruveedhula, "YANG Data Model for
MPLS-based L2VPN", draft-ietf-bess-l2vpn-yang-06.txt, June MPLS-based L2VPN", draft-ietf-bess-l2vpn-yang-06.txt, June
30, 2017 30, 2017
Authors' Addresses Appendix A. Data Tree Example
This section contains an example of an instance data tree in the JSON
encoding [RFC7951], containing both configuration and state data.
| +-------+ |
| eth2/1 | | eth2/2 | +------------+
| +-----+ R2 +-----------+----+ Receiver 1 +
| | | | | +------------+
| | +-------+ |
| | |
| +-------+ eth1/2 | +-------+ |
| | +-----------+ | | eth3/2 | +------------+
eth1/1 +--+ R1 | | R3 +-----------+----+ Receiver 2 +
| | +-----------------+ | | +------------+
+-------+ | +-------+ eth1/3 eth3/1 +-------+ |
| | | |
| +--+ |
| | | |
| | | |
+-------+ | |
Source
The configuration instance data tree for R1 in the above figure could be
as follows:
{
"ietf-igmp-mld-snooping:igmp-snooping-instances": {
"igmp-snooping-instance": [
{
"name": "ins101",
"type": "bridge",
"enable": true
}
]
},
"ietf-igmp-mld-snooping:mld-snooping-instances": {
"mld-snooping-instance": [
{
"name": "ins102",
"type": "bridge",
"enable": true
}
]
},
"ietf-igmp-mld-snooping:bridges": {
"bridge": [
{
"name": "isp",
"component": [
{
"name": "comp1",
"bridge-vlan": {
"vlan": [
{
"vid": 101,
"igmp-snooping-instance": "ins101"
},
{
"vid": 102,
"mld-snooping-instance": "ins102"
}
]
}
}
]
}
]
}
}
The corresponding operational state data for R1 could be as follows:
{
"ietf-igmp-mld-snooping:igmp-snooping-instances": {
"igmp-snooping-instance": [
{
"name": "ins101",
"type": "bridge",
"enable": true,
"forwarding-mode": "ip",
"explicit-tracking": false,
"exclude-lite": false,
"send-query": true,
"immediate-leave": [null],
"last-member-query-interval": 1,
"query-interval": 125,
"query-max-response-time": 10,
"require-router-alert": false,
"robustness-variable": 2,
"entries-count": 1,
"bridge-mrouter-interface": ["1/1"],
"group": [
{
"address": "223.0.0.1",
"mac-address": "01:00:5e:00:00:01",
"expire": 120,
"up-time": 180,
"last-reporter": "100.0.0.1",
"source": [
{
"address": "192.168.0.1",
"bridge-outgoing-interface": ["1/2"],
"up-time": 180,
"expire": 120,
"last-reporter": "100.0.0.1"
}
]
}
]
}
]
},
"ietf-igmp-mld-snooping:mld-snooping-instances": {
"mld-snooping-instance": [
{
"name": "ins102",
"type": "bridge",
"enable": true,
"forwarding-mode": "ip",
"explicit-tracking": false,
"exclude-lite": false,
"send-query": true,
"immediate-leave": [null],
"last-member-query-interval": 1,
"query-interval": 125,
"query-max-response-time": 10,
"require-router-alert": false,
"robustness-variable": 2,
"entries-count": 1,
"bridge-mrouter-interface": ["1/1"],
"group": [
{
"address": "FF0E::1",
"mac-address": "01:00:5e:00:00:01",
"expire": 120,
"up-time": 180,
"last-reporter": "2001::1",
"source": [
{
"address": "3001::1",
"bridge-outgoing-interface": ["1/2"],
"up-time": 180,
"expire": 120,
"last-reporter": "2001::1"
}
]
}
]
}
]
}
Authors' Addresses
Hongji Zhao Hongji Zhao
Ericsson (China) Communications Company Ltd. Ericsson (China) Communications Company Ltd.
Ericsson Tower, No. 5 Lize East Street, Ericsson Tower, No. 5 Lize East Street,
Chaoyang District Beijing 100102, P.R. China Chaoyang District Beijing 100102, P.R. China
Email: hongji.zhao@ericsson.com Email: hongji.zhao@ericsson.com
Xufeng Liu Xufeng Liu
Jabil Jabil
8281 Greensboro Drive, Suite 200 8281 Greensboro Drive, Suite 200
McLean VA 22102 McLean VA 22102
USA USA
EMail: Xufeng_Liu@jabil.com EMail: Xufeng.liu.ietf@gmail.com
Yisong Liu Yisong Liu
Huawei Technologies Huawei Technologies
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: liuyisong@huawei.com Email: liuyisong@huawei.com
Anish Peter Anish Peter
Individual Individual
EMail: anish.ietf@gmail.com EMail: anish.ietf@gmail.com
Mahesh Sivakumar Mahesh Sivakumar
Cisco Systems Cisco Systems
510 McCarthy Boulevard 510 McCarthy Boulevard
Milpitas, California Milpitas, California
USA USA
EMail: masivaku@cisco.com EMail: sivakumar.mahesh@gmail.com
 End of changes. 179 change blocks. 
272 lines changed or deleted 660 lines changed or added

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