draft-ietf-pim-igmp-mld-snooping-yang-03.txt   draft-ietf-pim-igmp-mld-snooping-yang-04.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: November 28, 2018 Jabil Expires: February 06, 2019 Jabil
Y. Liu Y. Liu
Huawei Huawei
M. Sivakumar M. Sivakumar
Cisco Juniper
A. Peter A. Peter
Individual Individual
May 29, 2018 August 07, 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-03.txt draft-ietf-pim-igmp-mld-snooping-yang-04.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. The YANG module in
this document conforms to Network Management Datastore Architecture
(NMDA).
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 44 skipping to change at page 2, line 4
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."
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 February 06, 2019.
This Internet-Draft will expire on November 28, 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
skipping to change at page 2, line 25 skipping to change at page 2, line 26
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...................................................3 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...........................................4 2. Design of Data Model...........................................3
2.1. Overview..................................................4 2.1. Overview..................................................4
2.2. IGMP Snooping Instances...................................4 2.2. IGMP Snooping Instances...................................4
2.3. MLD Snooping Instances....................................7 2.3. MLD Snooping Instances....................................6
2.4. IGMP and MLD Snooping References..........................9 2.4. IGMP and MLD Snooping Instances Reference.................7
2.5. Augment /if:interfaces/if:interface......................10 2.5. Augment /if:interfaces/if:interface.......................8
2.6. IGMP and MLD Snooping RPC................................12 2.6. IGMP and MLD Snooping RPC................................10
3. IGMP and MLD Snooping YANG Module.............................12 3. IGMP and MLD Snooping YANG Module.............................10
4. Security Considerations.......................................42 4. Security Considerations.......................................36
5. IANA Considerations...........................................43 5. IANA Considerations...........................................37
6. Normative References..........................................44 6. Normative References..........................................38
Appendix A. Data Tree Example...................................45 Appendix A. Data Tree Example...................................40
Authors' Addresses...............................................49 Authors' Addresses...............................................45
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
of Internet Group Management Protocol (IGMP) and Multicast Listener Internet Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) Snooping devices. Discovery (MLD) Snooping devices.
The YANG model in this document conforms to the Network Management The YANG module in this document conforms to the Network Management
Datastore Architecture defined in [I-D.ietf-netmod-revised- Datastore Architecture defined in [RFC8342]. The "Network Management
datastores]. The "Network Management Datastore Architecture" (NMDA) Datastore Architecture" (NMDA) adds the ability to inspect the current
adds the ability to inspect the current operational values for operational values for configuration, allowing clients to use identical
configuration, allowing clients to use identical paths for retrieving paths for retrieving the configured values and the 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 14 "OPTIONAL" in this document are to be interpreted as described in BCP 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 this A simplified graphical representation of the data model is used in this
document. The meaning of the symbols in these diagrams is as follows: document. The meaning of the symbols in these diagrams is as 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).
skipping to change at page 4, line 22 skipping to change at page 4, line 16
common user interface to IGMP and MLD Snooping. This document provides common user interface to IGMP and MLD Snooping. This document provides
freedom for vendors to adapt this data model to their product freedom for vendors to adapt this data model to their product
implementations. implementations.
2.1. Overview 2.1. Overview
The IGMP and MLD Snooping YANG module defined in this document has all The IGMP and MLD Snooping YANG module defined in this document has all
the common building blocks for the IGMP and MLD Snooping protocol. the common building blocks for the IGMP and MLD Snooping protocol.
The YANG module includes IGMP and MLD Snooping instance definition, The YANG module includes IGMP and MLD Snooping instance definition,
instance reference in the scenario of BRIDGE, L2VPN. The module also instance reference in the scenario of BRIDGE and L2VPN. The module also
includes the RPC methods for clearing IGMP and MLD Snooping group includes the RPC methods for clearing IGMP and MLD Snooping group
tables. tables.
This YANG model follows the Guidelines for YANG Module Authors (NMDA) This YANG module follows the Guidelines for YANG Module Authors (NMDA)
[draft-dsdt-nmda-guidelines-01]. This NMDA ("Network Management [draft-dsdt-nmda-guidelines-01]. This NMDA ("Network Management
Datastore Architecture") architecture provides an architectural Datastore Architecture") architecture provides an architectural
framework for datastores as they are used by network management framework for datastores as they are used by network management
protocols such as NETCONF [RFC6241], RESTCONF [RFC8040] and the YANG protocols such as NETCONF [RFC6241], RESTCONF [RFC8040] and the YANG
[RFC7950] data modeling language. [RFC7950] data modeling language.
2.2. IGMP Snooping Instances 2.2. IGMP Snooping Instances
The YANG module defines igmp-snooping-instance which could be referenced The YANG module defines igmp-snooping-instance which could be referenced
in the BRIDGE or L2VPN scenario to enable IGMP Snooping. in the BRIDGE or L2VPN scenario to enable IGMP Snooping.
All the IGMP Snooping related attributes have been defined in the igmp- All the IGMP Snooping related attributes have been defined in the igmp-
snooping-instance. The read-write attribute is configurable data. The snooping-instance. The read-write attribute means configurable data. The
read-only attribute shows state data. The key attribute of the igmp- read-only attribute means state data. The key attribute of the igmp-
snooping-instance is name. snooping-instance is name.
One igmp-snooping-instance could be referenced in one BRIDGE instance or
L2VPN instance. One igmp-snooping-instance corresponds to one BRIDGE
instance or L2VPN instance.
The value of type in igmp-snooping-instance is bridge or l2vpn. When it 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 is bridge, the igmp-snooping-instance will be referenced in the BRIDGE
scenario. When it is l2vpn, the igmp-snooping-instance will be scenario. When it is l2vpn, the igmp-snooping-instance will be
referenced in the L2VPN scenario. referenced in the L2VPN scenario.
The value of bridge-mrouter-interface, l2vpn-mrouter-interface-ac, The value of bridge-mrouter-interface, l2vpn-mrouter-interface-ac,
l2vpn-mrouter-interface-pw are filled by routing system dynamically. l2vpn-mrouter-interface-pw are filled by snooping device dynamically.
They are different from static-bridge-mrouter-interface, static-l2vpn- They are different from static-bridge-mrouter-interface, static-l2vpn-
mrouter-interface-ac, and static-l2vpn-mrouter-interface-pw which are mrouter-interface-ac, and static-l2vpn-mrouter-interface-pw which are
configured statically. 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 type? enumeration
| +--rw enable? boolean {admin-enable}?
| +--rw forwarding-mode? enumeration
| +--rw explicit-tracking? boolean {explicit-tracking}?
| +--rw exclude-lite? boolean {exclude-lite}?
| +--rw send-query? boolean
| +--rw immediate-leave? empty {immediate-leave}?
| +--rw last-member-query-interval? uint16
| +--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}?
| +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref {static-
mrouter-interface}?
| +--rw static-l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref
{static-mrouter-interface}?
| +--rw querier-source? inet:ipv4-address
| +--rw static-l2-multicast-group* [group source-addr] {static-l2-
multicast-group}?
| | +--rw group inet:ipv4-address
| | +--rw source-addr source-ipv4-addr-type
| | +--rw bridge-outgoing-interface* if:interface-ref
| | +--rw l2vpn-outgoing-ac* l2vpn-instance-ac-ref
| | +--rw l2vpn-outgoing-pw* l2vpn-instance-pw-ref
| +--ro entries-count? uint32
| +--ro bridge-mrouter-interface* if:interface-ref
| +--ro l2vpn-mrouter-interface-ac* if:interface-ref
| +--ro l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref
| +--ro group* [address]
| +--ro address inet:ipv4-address
| +--ro mac-address? yang:phys-address
| +--ro expire? uint32
| +--ro up-time? uint32
| +--ro last-reporter? inet:ipv4-address
| +--ro source* [address]
| +--ro address inet:ipv4-address
| +--ro bridge-outgoing-interface* if:interface-ref
| +--ro l2vpn-outgoing-ac* l2vpn-instance-ac-ref
| +--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref
| +--ro up-time? uint32
| +--ro expire? uint32
| +--ro host-count? uint32 {explicit-tracking}?
| +--ro last-reporter? inet:ipv4-address
| +--ro host* [host-address] {explicit-tracking}?
| +--ro host-address inet:ipv4-address
| +--ro host-filter-mode? enumeration
2.3. MLD Snooping Instances
The YANG module defines mld-snooping-instance which could be referenced
in the BRIDGE or L2VPN scenario to enable MLD Snooping.
The mld-snooping-instance is the same as IGMP snooping except changing
IPV4 addresses to IPV6 addresses.
module: ietf-igmp-mld-snooping
+--rw mld-snooping-instances
| +--rw mld-snooping-instance* [name]
| +--rw name string | +--rw name string
| +--rw type? enumeration | +--rw type? enumeration
| +--rw enable? boolean
| +--rw enable? boolean {admin-enable}?
| +--rw forwarding-mode? enumeration | +--rw forwarding-mode? enumeration
| +--rw explicit-tracking? boolean
| +--rw explicit-tracking? boolean {explicit- | | {explicit-tracking}?
tracking}? | +--rw exclude-lite? boolean
| | {exclude-lite}?
| +--rw exclude-lite? boolean {exclude-lite}?
| +--rw send-query? boolean | +--rw send-query? boolean
| +--rw immediate-leave? empty
| +--rw immediate-leave? empty {immediate-leave}? | | {immediate-leave}?
| +--rw last-member-query-interval? uint16 | +--rw last-member-query-interval? uint16
| +--rw query-interval? uint16 | +--rw query-interval? uint16
| +--rw query-max-response-time? uint16 | +--rw query-max-response-time? uint16
| +--rw require-router-alert? boolean
| +--rw require-router-alert? boolean {require-router- | | {require-router-alert}?
alert}?
| +--rw robustness-variable? uint8 | +--rw robustness-variable? uint8
| +--rw version? uint8 | +--rw version? uint8
| +--rw static-bridge-mrouter-interface* if:interface-ref
| +--rw static-bridge-mrouter-interface* if:interface-ref {static- | | {static-mrouter-interface}?
mrouter-interface}? | +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref
| +--rw static-l2vpn-mrouter-interface-ac* if:interface-ref {static- | | {static-mrouter-interface}?
mrouter-interface}? | +--rw static-l2vpn-mrouter-interface-pw*
| | l2vpn-instance-pw-ref {static-mrouter-interface}?
| +--rw static-l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref | +--rw querier-source? inet:ipv4-address
{static-mrouter-interface}? | +--rw static-l2-multicast-group* [group source-addr]
| | {static-l2-multicast-group}?
| +--rw querier-source? inet:ipv6-address | | +--rw group inet:ipv4-address
| | +--rw source-addr source-ipv4-addr-type
| +--rw static-l2-multicast-group* [group source-addr] {static-l2-
multicast-group}?
| | +--rw group inet:ipv6-address
| | +--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*
| +--ro l2vpn-mrouter-interface-pw* l2vpn-instance-pw-ref | | l2vpn-instance-pw-ref
| +--ro group* [address] | +--ro group* [address]
| +--ro address inet:ipv4-address
| +--ro address inet:ipv6-address
| +--ro mac-address? yang:phys-address | +--ro mac-address? yang:phys-address
| +--ro expire? uint32 | +--ro expire? uint32
| +--ro up-time? uint32 | +--ro up-time? uint32
| +--ro last-reporter? inet:ipv4-address
| +--ro last-reporter? inet:ipv6-address
| +--ro source* [address] | +--ro source* [address]
| +--ro address inet:ipv4-address
| +--ro address inet:ipv6-address
| +--ro bridge-outgoing-interface* if:interface-ref | +--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
| +--ro host-count? uint32 {explicit-tracking}? | | {explicit-tracking}?
| +--ro last-reporter? inet:ipv4-address
| +--ro last-reporter? inet:ipv6-address
| +--ro host* [host-address] {explicit-tracking}? | +--ro host* [host-address] {explicit-tracking}?
| +--ro host-address inet:ipv4-address
| +--ro host-address inet:ipv6-address
| +--ro host-filter-mode? enumeration | +--ro host-filter-mode? enumeration
2.4. IGMP and MLD Snooping References 2.3. MLD Snooping Instances
The igmp-snooping-instance could be referenced in the scenario of BRIDGE
or L2VPN to configure the IGMP Snooping. The name of the instance is the
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 bridge* [name]
| +--rw name name-type
| +--rw igmp-snooping-instance? igmp-snooping-instance-ref
| +--rw mld-snooping-instance? mld-snooping-instance-ref The YANG module defines mld-snooping-instance which could be referenced
in the BRIDGE or L2VPN scenario to enable MLD Snooping.
| +--rw component* [name] The mld-snooping-instance is the same as IGMP snooping except changing
IPV4 addresses to IPV6 addresses.
| +--rw name string module: ietf-igmp-mld-snooping
+--rw mld-snooping-instances
+--rw mld-snooping-instance* [name]
+--rw name string
+--rw type? enumeration
+--rw enable? boolean
+--rw forwarding-mode? enumeration
+--rw explicit-tracking? boolean
| {explicit-tracking}?
+--rw exclude-lite? boolean
| {exclude-lite}?
+--rw send-query? boolean
+--rw immediate-leave? empty
| {immediate-leave}?
+--rw last-member-query-interval? uint16
+--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}?
+--rw static-l2vpn-mrouter-interface-ac* if:interface-ref
| {static-mrouter-interface}?
+--rw static-l2vpn-mrouter-interface-pw*
| l2vpn-instance-pw-ref {static-mrouter-interface}?
+--rw querier-source? inet:ipv6-address
+--rw static-l2-multicast-group* [group source-addr]
| {static-l2-multicast-group}?
| +--rw group inet:ipv6-address
| +--rw source-addr source-ipv6-addr-type
| +--rw bridge-outgoing-interface* if:interface-ref
| +--rw l2vpn-outgoing-ac* l2vpn-instance-ac-ref
| +--rw l2vpn-outgoing-pw* l2vpn-instance-pw-ref
+--ro entries-count? uint32
+--ro bridge-mrouter-interface* if:interface-ref
+--ro l2vpn-mrouter-interface-ac* if:interface-ref
+--ro l2vpn-mrouter-interface-pw*
| l2vpn-instance-pw-ref
+--ro group* [address]
+--ro address inet:ipv6-address
+--ro mac-address? yang:phys-address
+--ro expire? uint32
+--ro up-time? uint32
+--ro last-reporter? inet:ipv6-address
+--ro source* [address]
+--ro address inet:ipv6-address
+--ro bridge-outgoing-interface* if:interface-ref
+--ro l2vpn-outgoing-ac* l2vpn-instance-ac-ref
+--ro l2vpn-outgoing-pw* l2vpn-instance-pw-ref
+--ro up-time? uint32
+--ro expire? uint32
+--ro host-count? uint32
| {explicit-tracking}?
+--ro last-reporter? inet:ipv6-address
+--ro host* [host-address] {explicit-tracking}?
+--ro host-address inet:ipv6-address
+--ro host-filter-mode? enumeration
| +--rw bridge-vlan 2.4. IGMP and MLD Snooping Instances Reference
| +--rw vlan* [vid] The igmp-snooping-instance could be referenced in the scenario of BRIDGE
or L2VPN to configure the IGMP Snooping.
| +--rw vid vlan-index-type For the BRIDGE scenario this model augments /dot1q:bridges/dot1q:bridge
to reference igmp-snooping-instance. It means IGMP Snooping is enabled
in the whole bridge.
| +--rw igmp-snooping-instance? igmp-snooping-instance-ref It also augments /dot1q:bridges/dot1q:bridge/dot1q:component/
| +--rw mld-snooping-instance? mld-snooping-instance-ref dot1q:bridge-vlan/dot1q:vlan to reference igmp-snooping-instance. It
means IGMP Snooping is enabled in the certain VLAN of the bridge.
+--rw l2vpn-instances augment /dot1q:bridges/dot1q:bridge:
+--rw igmp-snooping-instance? igmp-snooping-instance-ref
+--rw mld-snooping-instance? mld-snooping-instance-ref
+--rw l2vpn-instance* [name] augment /dot1q:bridges/dot1q:bridge/dot1q:component/dot1q:bridge-vlan/dot1q:vlan:
+--rw igmp-snooping-instance? igmp-snooping-instance-ref
+--rw mld-snooping-instance? mld-snooping-instance-ref
+--rw name string For the L2VPN scenario this model augments /ni:network-instances/
ni:network-instance/ni:ni-type/l2vpn:l2vpn to reference igmp-snooping-
instance. It means IGMP Snooping is enabled in the specified l2vpn
instance.
+--rw igmp-snooping-instance? igmp-snooping-instance-ref augment /ni:network-instances/ni:network-instance/ni:ni-type/l2vpn:l2vpn:
+--rw igmp-snooping-instance? igmp-snooping-instance-ref
+--rw mld-snooping-instance? mld-snooping-instance-ref
+--rw mld-snooping-instance? mld-snooping-instance-ref The mld-snooping-instance could be referenced in concurrence with igmp-
snooping-instance to configure the MLD Snooping.
2.5. Augment /if:interfaces/if:interface 2.5. Augment /if:interfaces/if:interface
This model augment /if:interfaces/if:interface and then add the IGMP and This model augments /if:interfaces/if:interface and then add the IGMP
MLD Snooping related attributes under it. The attributes include enable, and MLD Snooping related attributes under it. The attributes include
version, etc. enable, version, etc.
The static-mrouter-interface and static-l2-multicast-group could be The static-mrouter-interface and static-l2-multicast-group could be
configured statically under the /if:interfaces/if:interface/ims:igmp- configured statically under the /if:interfaces/if:interface/ims:igmp-
mld-snooping view. Meanwhile, you can configure them under the IGMP and mld-snooping view. Meanwhile, you can configure them under the IGMP and
MLD Snooping instance view. MLD Snooping instance view.
The attributes under the statistics are read-only. They show the The attributes under the statistics are read-only. They show the
statistics of IGMP and MLD Snooping related packets. 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
+--rw version? uint8
+--rw enable? boolean {admin-enable}? +--rw type? enumeration
+--rw static-mrouter-interface
+--rw version? uint8 | +--rw (static-mrouter-interface)?
| +--:(bridge)
+--rw type? enumeration | | +--rw bridge-name? string
| | +--rw vlan-id* uint32
+--rw static-mrouter-interface | +--:(l2vpn)
| +--rw l2vpn-instance-name? string
| +--rw (static-mrouter-interface)? +--rw static-l2-multicast-group
| +--rw (static-l2-multicast-group)?
| +--:(bridge) | +--:(bridge)
| | +--rw bridge-name? string
| | +--rw bridge-name? string | | +--rw bridge-group-v4* [group source-addr]
| | | +--rw group inet:ipv4-address
| | +--rw vlan-id* uint32 | | | +--rw source-addr source-ipv4-addr-type
| | | +--rw vlan-id* uint32
| +--:(l2vpn) | | +--rw bridge-group-v6* [group source-addr]
| | +--rw group inet:ipv6-address
| +--rw l2vpn-instance-name? string | | +--rw source-addr source-ipv6-addr-type
+--rw static-l2-multicast-group | | +--rw vlan-id* uint32
| +--:(l2vpn)
| +--rw (static-l2-multicast-group)? | +--rw l2vpn-group-v4* [group source-addr]
| | +--rw group inet:ipv4-address
| +--:(bridge) | | +--rw source-addr source-ipv4-addr-type
| | +--rw l2vpn-instance-name? string
| | +--rw bridge-name? string | +--rw l2vpn-group-v6* [group source-addr]
| +--rw group inet:ipv6-address
| | +--rw bridge-group-v4* [group source-addr] | +--rw source-addr source-ipv6-addr-type
| +--rw l2vpn-instance-name? string
| | | +--rw group inet:ipv4-address +--ro statistics
+--ro received
| | | +--rw source-addr source-ipv4-addr-type | +--ro query? yang:counter64
| +--ro membership-report-v1? yang:counter64
| | | +--rw vlan-id* uint32 | +--ro membership-report-v2? yang:counter64
| +--ro membership-report-v3? yang:counter64
| | +--rw bridge-group-v6* [group source-addr] | +--ro leave? yang:counter64
| +--ro non-member-leave? yang:counter64
| | +--rw group inet:ipv6-address | +--ro pim? yang:counter64
+--ro sent
| | +--rw source-addr source-ipv6-addr-type +--ro query? yang:counter64
+--ro membership-report-v1? yang:counter64
| | +--rw vlan-id* uint32 +--ro membership-report-v2? yang:counter64
+--ro membership-report-v3? yang:counter64
| +--:(l2vpn) +--ro leave? yang:counter64
+--ro non-member-leave? yang:counter64
| +--rw l2vpn-group-v4* [group source-addr] +--ro pim? yang:counter64
| | +--rw group inet:ipv4-address
| | +--rw source-addr source-ipv4-addr-type
| | +--rw l2vpn-instance-name? string
| +--rw l2vpn-group-v6* [group source-addr]
| +--rw group inet:ipv6-address
| +--rw source-addr source-ipv6-addr-type
| +--rw l2vpn-instance-name? string
+--ro statistics
+--ro received
| +--ro query? yang:counter64
| +--ro membership-report-v1? yang:counter64
| +--ro membership-report-v2? yang:counter64
| +--ro membership-report-v3? yang:counter64
| +--ro leave? yang:counter64
| +--ro non-member-leave? yang:counter64
| +--ro pim? yang:counter64
+--ro sent
+--ro query? yang:counter64
+--ro membership-report-v1? yang:counter64
+--ro membership-report-v2? yang:counter64
+--ro membership-report-v3? yang:counter64
+--ro leave? yang:counter64
+--ro non-member-leave? yang:counter64
+--ro pim? yang:counter64
2.6. 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-05-03.yang <CODE BEGINS> file ietf-igmp-mld-snooping@2018-08-02.yang
module ietf-igmp-mld-snooping { module ietf-igmp-mld-snooping {
namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping"; yang-version 1.1;
// replace with IANA namespace when assigned namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping";
prefix ims; // replace with IANA namespace when assigned
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";
} }
import ietf-l2vpn { import ietf-l2vpn {
prefix "l2vpn"; prefix "l2vpn";
} }
import ietf-network-instance { import ietf-network-instance {
prefix "ni"; prefix "ni";
} }
organization import ieee802-dot1q-bridge {
"IETF PIM Working Group"; prefix "dot1q";
}
organization
"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>
Editors: Hongji Zhao Editors: Hongji Zhao
<mailto:hongji.zhao@ericsson.com> <mailto:hongji.zhao@ericsson.com>
Xufeng Liu Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.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:sivakumar.mahesh@gmail.com> <mailto:sivakumar.mahesh@gmail.com>
"; ";
description
"The module defines a collection of YANG definitions common for
all Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) Snooping devices.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the description
RFC itself for full legal notices."; "The module defines a collection of YANG definitions common for
all Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) Snooping devices.
revision 2018-05-03 { Copyright (c) 2018 IETF Trust and the persons identified as
description authors of the code. All rights reserved.
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
}
/* Redistribution and use in source and binary forms, with or
* Features without modification, is permitted pursuant to, and subject to
*/ the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
feature admin-enable { This version of this YANG module is part of RFC XXXX; see the
description RFC itself for full legal notices.";
"Support configuration to enable or disable IGMP and MLD
Snooping.";
}
feature immediate-leave { revision 2018-08-02 {
description description
"Support configuration of immediate-leave."; "Initial revision.";
} reference
"RFC XXXX: A YANG Data Model for IGMP and MLD Snooping";
}
/*
* Features
*/
feature join-group { feature immediate-leave {
description description
"Support configuration of join-group."; "Support configuration of immediate-leave.";
} }
feature require-router-alert { feature join-group {
description description
"Support configuration of require-router-alert."; "Support configuration of join-group.";
} }
feature static-l2-multicast-group { feature require-router-alert {
description description
"Support configuration of L2 multicast static-group."; "Support configuration of require-router-alert.";
}
} feature static-l2-multicast-group {
description
"Support configuration of L2 multicast static-group.";
}
feature static-mrouter-interface { feature static-mrouter-interface {
description description
"Support configuration of mrouter interface."; "Support configuration of mrouter interface.";
} }
feature per-instance-config { feature rpc-clear-groups {
description description
"Support configuration of each VLAN or l2vpn instance or EVPN "Support clearing statistics by RPC for IGMP & MLD snooping.";
instance."; }
}
feature rpc-clear-groups { feature explicit-tracking {
description description
"Support to clear statistics by RPC for IGMP and MLD "Support configuration of per instance explicit-tracking.";
Snooping."; }
}
feature explicit-tracking { feature exclude-lite {
description description
"Support configuration of per instance explicit-tracking "Support configuration of per instance exclude-lite.";
hosts."; }
}
feature exclude-lite { /*
description * Typedefs
"Support configuration of per instance exclude-lite."; */
} typedef igmp-snooping-instance-ref {
type leafref {
path "/igmp-snooping-instances/igmp-snooping-instance/name";
}
description
"This type is used by data models that need to reference
IGMP snooping instance.";
}
/* typedef mld-snooping-instance-ref {
* Typedefs type leafref {
*/ path "/mld-snooping-instances/mld-snooping-instance/name";
typedef name-type {
type string {
length "0..32";
}
description
"A text string of up to 32 characters, of locally determined
significance.";
} }
typedef vlan-index-type { description
type uint32 { "This type is used by data models that need to reference
range "1..4094 | 4096..4294967295"; MLD snooping instance.";
}
description
"A value used to index per-VLAN tables. Values of 0 and 4095
are not permitted. The range of valid VLAN indices. If the
value is greater than 4095, then it represents a VLAN with
scope local to the particular agent, i.e., one without a
global VLAN-ID assigned to it. Such VLANs are outside the
scope of IEEE 802.1Q, but it is convenient to be able to
manage them in the same way using this YANG module.";
reference
"IEEE Std 802.1Q-2014: Virtual Bridged Local Area Networks.";
} }
typedef igmp-snooping-instance-ref { typedef l2vpn-instance-ac-ref {
type leafref { type leafref {
path "/igmp-snooping-instances/igmp-snooping-instance/name"; path "/ni:network-instances/ni:network-instance"+
} "/l2vpn:endpoint/l2vpn:name";
description
"This type is used by data models that need to reference igmp
snooping instance.";
}
typedef mld-snooping-instance-ref {
type leafref {
path "/mld-snooping-instances/mld-snooping-instance/name";
}
description
"This type is used by data models that need to reference mld
snooping instance.";
}
typedef l2vpn-instance-ac-ref {
type leafref {
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;
} }
description }
"Multicast source IPV4 address type."; type inet:ipv4-address;
} // source-ipv4-addr-type }
description
"Multicast source IPV4 address 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;
} }
description
"Multicast source IPV6 address type.";
} // source-ipv6-addr-type
/* }
* Identities type inet:ipv6-address;
*/ }
description
"Multicast source IPV6 address type.";
} // source-ipv6-addr-type
/* /*
* Groupings * Groupings
*/ */
grouping general-state-attributes { grouping general-state-attributes {
description "General State attributes"; description "General State attributes";
container received { container received {
config false;
description "Statistics of received IGMP and MLD Snooping
related packets.";
uses general-statistics-sent-received;
}
container sent {
config false; config false;
description "Statistics of sent IGMP and MLD Snooping related description "Statistics of received IGMP and MLD snooping
packets."; related packets.";
uses general-statistics-sent-received;
}
} // general-state-attributes
grouping instance-config-attributes-igmp-snooping {
description "IGMP snooping configuration for each VLAN or l2vpn
instance or EVPN instance.";
uses instance-config-attributes-igmp-mld-snooping; uses general-statistics-sent-received;
}
container sent {
config false;
description "Statistics of sent IGMP and MLD snooping
related packets.";
leaf querier-source { uses general-statistics-sent-received;
type inet:ipv4-address; }
description "Use the IGMP snooping querier to support IGMP
snooping in a VLAN where PIM and IGMP are not configured.
The IPV4 address is used as the source address in
messages.";
}
list static-l2-multicast-group { } // general-state-attributes
if-feature static-l2-multicast-group;
key "group source-addr";
description
"A static multicast route, (*,G) or (S,G).";
leaf group { grouping instance-config-attributes-igmp-snooping {
type inet:ipv4-address; description "IGMP snooping configuration for each"+
description "BRIDGE or L2VPN instance.";
"Multicast group IPV4 address";
}
leaf source-addr { uses instance-config-attributes-igmp-mld-snooping;
type source-ipv4-addr-type;
description
"Multicast source IPV4 address.";
}
leaf-list bridge-outgoing-interface { leaf querier-source {
when "../../type = 'bridge'"; type inet:ipv4-address;
type if:interface-ref; description "Use the IGMP snooping querier to support IGMP
description "Outgoing interface in bridge fowarding"; snooping in a VLAN where PIM and IGMP are not configured.
The IPV4 address is used as source address in messages.";
}
} list static-l2-multicast-group {
if-feature static-l2-multicast-group;
key "group source-addr";
description
"A static multicast route, (*,G) or (S,G).";
leaf-list l2vpn-outgoing-ac { leaf group {
when "../../type = 'l2vpn'"; type inet:ipv4-address;
type l2vpn-instance-ac-ref; description
description "Outgoing AC in L2VPN fowarding"; "Multicast group IPV4 address";
}
} leaf source-addr {
type source-ipv4-addr-type;
description
"Multicast source IPV4 address.";
}
leaf-list l2vpn-outgoing-pw { leaf-list bridge-outgoing-interface {
when "../../type = 'l2vpn'"; when "../../type = 'bridge'";
type l2vpn-instance-pw-ref; type if:interface-ref;
description "Outgoing PW in L2VPN fowarding"; description "Outgoing interface in BRIDGE forwarding";
}
} leaf-list l2vpn-outgoing-ac {
when "../../type = 'l2vpn'";
type l2vpn-instance-ac-ref;
description "Outgoing AC in L2VPN forwarding";
}
} // static-l2-multicast-group leaf-list l2vpn-outgoing-pw {
when "../../type = 'l2vpn'";
type l2vpn-instance-pw-ref;
description "Outgoing PW in L2VPN forwarding";
}
} // static-l2-multicast-group
} // instance-config-attributes-igmp-snooping
} // instance-config-attributes-igmp-snooping grouping instance-config-attributes-igmp-mld-snooping {
description
"IGMP and MLD snooping configuration of each VLAN.";
grouping instance-config-attributes-igmp-mld-snooping { leaf enable {
type boolean;
default false;
description description
"IGMP and MLD Snooping configuration of each VLAN."; "Set the value to true to enable IGMP and MLD snooping in the
VLAN instance.";
}
leaf enable { leaf forwarding-mode {
if-feature admin-enable; type enumeration {
type boolean; enum "mac" {
default false;
description description
"Set the value to true to enable IGMP and MLD Snooping in "MAC-based lookup mode";
the VLAN instance.";
} }
enum "ip" {
leaf forwarding-mode {
type enumeration {
enum "mac" {
description
"MAC-based lookup mode";
}
enum "ip" {
description
"IP-based lookup mode";
}
}
default "ip";
description "The default forwarding mode for IGMP and MLD
Snooping is ip.
cisco command is as below
Router(config-vlan-config)# multicast snooping lookup
{ ip | mac } ";
}
leaf explicit-tracking {
if-feature explicit-tracking;
type boolean;
default false;
description "Tracks IGMP & MLD Snooping v3 membership reports
from individual hosts.
It contributes to saving network resources and
shortening leave latency.";
}
leaf exclude-lite {
if-feature exclude-lite;
type boolean;
default false;
description description
"lightweight IGMPv3 and MLDv2 protocols, which simplify the "IP-based lookup mode";
standard versions of IGMPv3 and MLDv2.";
reference "RFC5790";
} }
leaf send-query {
type boolean;
default true;
description "Enable quick response for topo changes.
To support IGMP snooping in a VLAN where PIM and IGMP are
not configured.
It cooperates with param querier-source. ";
}
/**
leaf mrouter-aging-time {
type uint16 ;
default 180;
description "Aging time for mrouter interface";
} }
**/ default "ip";
description "The default forwarding mode is ip";
}
leaf immediate-leave { leaf explicit-tracking {
if-feature immediate-leave; if-feature explicit-tracking;
type empty; type boolean;
description default false;
"When fast leave is enabled, the IGMP software assumes that description "Tracks IGMP & MLD snooping v3 membership reports
no more than one host is present on each VLAN port."; from individual hosts. It contributes to saving network
} resources and shortening leave latency.";
}
leaf last-member-query-interval { leaf exclude-lite {
type uint16 { if-feature exclude-lite;
range "1..65535"; type boolean;
} default false;
units seconds; description
default 1; "lightweight IGMPv3 and MLDv2 protocols, which simplify the
description standard versions of IGMPv3 and MLDv2.";
"Last Member Query Interval, which may be tuned to modify reference "RFC5790";
the }
leave latency of the network.";
reference "RFC3376. Sec. 8.8.";
}
leaf query-interval { leaf send-query {
type boolean;
default false;
description "Enable quick response for topo changes.
To support IGMP snooping in a VLAN where PIM and IGMP are
not configured. It cooperates with param querier-source. ";
}
type uint16; leaf immediate-leave {
units seconds; if-feature immediate-leave;
default 125; type empty;
description description
"The Query Interval is the interval between General "When immediate leave is enabled, the IGMP software assumes
Queries that no more than one host is present on each VLAN port.";
sent by the Querier."; }
reference "RFC3376. Sec. 4.1.7, 8.2, 8.14.2.";
}
leaf query-max-response-time { leaf last-member-query-interval {
type uint16 {
range "1..65535";
}
units seconds;
default 1;
description
"Last Member Query Interval, which may be tuned to modify
the leave latency of the network.";
reference "RFC3376. Sec. 8.8.";
}
type uint16; leaf query-interval {
units seconds; type uint16;
default 10; units seconds;
description default 125;
"Query maximum response time specifies the maximum time description
allowed before sending a responding report."; "The Query Interval is the interval between General Queries
reference "RFC3376. Sec. 4.1.1, 8.3, 8.14.3."; sent by the Querier.";
reference "RFC3376. Sec. 4.1.7, 8.2, 8.14.2.";
}
} leaf query-max-response-time {
type uint16;
units seconds;
default 10;
description
"Query maximum response time specifies the maximum time
allowed before sending a responding report.";
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 should exist in the IP "When the value is true, router alert should exist
head of IGMP or MLD packet."; in the IP head of IGMP or MLD packet.";
} }
leaf robustness-variable { leaf robustness-variable {
type uint8 { type uint8 {
range "1..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 {
type uint8 { type uint8 {
range "1..3"; range "1..3";
}
description "IGMP and MLD Snooping version.";
}
leaf-list static-bridge-mrouter-interface { }
default 2;
description "IGMP and MLD snooping version.";
}
when "../type = 'bridge'"; leaf-list static-bridge-mrouter-interface {
if-feature static-mrouter-interface; when "../type = 'bridge'";
type if:interface-ref; if-feature static-mrouter-interface;
description "static mrouter interface in bridge fowarding"; type if:interface-ref;
description "static mrouter interface in BRIDGE forwarding";
}
} leaf-list static-l2vpn-mrouter-interface-ac {
when "../type = 'l2vpn'";
if-feature static-mrouter-interface;
type if:interface-ref;
description "static mrouter interface whose type is interface
in L2VPN forwarding";
}
leaf-list static-l2vpn-mrouter-interface-ac { leaf-list static-l2vpn-mrouter-interface-pw {
when "../type = 'l2vpn'";
if-feature static-mrouter-interface;
type l2vpn-instance-pw-ref;
description "static mrouter interface whose type is PW
in L2VPN forwarding";
}
} // instance-config-attributes-igmp-mld-snooping
when "../type = 'l2vpn'"; grouping instance-config-attributes-mld-snooping {
if-feature static-mrouter-interface; description "MLD snooping configuration of each VLAN.";
type if:interface-ref;
description "static mrouter interface whose type is interface
in l2vpn forwarding";
} uses instance-config-attributes-igmp-mld-snooping;
leaf-list static-l2vpn-mrouter-interface-pw { leaf querier-source {
type inet:ipv6-address;
description
"Use the MLD snooping querier to support MLD snooping where
PIM and MLD are not configured. The IPV6 address is used as
the source address in messages.";
}
when "../type = 'l2vpn'"; list static-l2-multicast-group {
if-feature static-mrouter-interface; if-feature static-l2-multicast-group;
type l2vpn-instance-pw-ref; key "group source-addr";
description "static mrouter interface whose type is pw in l2vpn description
forwarding"; "A static multicast route, (*,G) or (S,G).";
leaf group {
type inet:ipv6-address;
description
"Multicast group IPV6 address";
} }
} // instance-config-attributes-igmp-mld-snooping leaf source-addr {
type source-ipv6-addr-type;
description
"Multicast source IPV6 address.";
}
grouping instance-config-attributes-mld-snooping { leaf-list bridge-outgoing-interface {
description "MLD snooping configuration of each VLAN."; when "../../type = 'bridge'";
type if:interface-ref;
description "Outgoing interface in BRIDGE forwarding";
}
uses instance-config-attributes-igmp-mld-snooping; leaf-list l2vpn-outgoing-ac {
when "../../type = 'l2vpn'";
type l2vpn-instance-ac-ref;
description "Outgoing AC in L2VPN forwarding";
}
leaf querier-source { leaf-list l2vpn-outgoing-pw {
type inet:ipv6-address; when "../../type = 'l2vpn'";
description type l2vpn-instance-pw-ref;
"Use the MLD snooping querier to support MLD snooping where PIM description "Outgoing PW in L2VPN forwarding";
and MLD are not configured. }
The IPV6 address is used as the source address in messages."; } // static-l2-multicast-group
} } // instance-config-attributes-mld-snooping
list static-l2-multicast-group { grouping instance-state-group-attributes-igmp-mld-snooping {
if-feature static-l2-multicast-group; description
key "group source-addr"; "Attributes for both IGMP and MLD snooping groups.";
description
"A static multicast route, (*,G) or (S,G).";
leaf group { leaf mac-address {
type inet:ipv6-address; type yang:phys-address;
description description "Destination MAC address for L2 multicast.";
"Multicast group IPV6 address"; }
}
leaf source-addr { leaf expire {
type source-ipv6-addr-type; type uint32;
description units seconds;
"Multicast source IPV6 address."; description
} "The time left before multicast group timeout.";
}
leaf-list bridge-outgoing-interface { leaf up-time {
when "../../type = 'bridge'"; type uint32;
type if:interface-ref; units seconds;
description "Outgoing interface in bridge fowarding"; description
"The time elapsed since L2 multicast record created.";
}
} } // instance-state-group-attributes-igmp-mld-snooping
leaf-list l2vpn-outgoing-ac { grouping instance-state-attributes-igmp-snooping {
when "../../type = 'l2vpn'"; description
type l2vpn-instance-ac-ref; "State attributes for IGMP snooping for each instance.";
description "Outgoing AC in L2VPN fowarding";
} uses instance-state-attributes-igmp-mld-snooping;
leaf-list l2vpn-outgoing-pw { list group {
when "../../type = 'l2vpn'";
type l2vpn-instance-pw-ref;
description "Outgoing PW in L2VPN fowarding";
} key "address";
} // static-l2-multicast-group config false;
} // instance-config-attributes-mld-snooping description "IGMP snooping information";
grouping instance-state-group-attributes-igmp-mld-snooping { leaf address {
type inet:ipv4-address;
description description
"Attributes for both IGMP and MLD snooping groups."; "Multicast group IPV4 address";
leaf mac-address {
type yang:phys-address;
description "Destination MAC address for L2 multicast
forwarding.";
} }
leaf expire { uses instance-state-group-attributes-igmp-mld-snooping;
type uint32;
units seconds;
description
"The time left before multicast group timeout.";
}
leaf up-time {
type uint32;
units seconds;
description
"The time elapsed since the device created L2 multicast
record.";
}
} // instance-state-group-attributes-igmp-mld-snooping
grouping instance-state-attributes-igmp-snooping {
leaf last-reporter {
type inet:ipv4-address;
description description
"State attributes for IGMP snooping for each VLAN or l2vpn "Address of the last host which has sent report to join
instance or EVPN instance."; the multicast group.";
}
uses instance-state-attributes-igmp-mld-snooping;
list group {
list source {
key "address"; key "address";
description "Source IPV4 address for multicast stream";
leaf address {
type inet:ipv4-address;
description "Source IPV4 address for multicast stream";
}
config false; uses instance-state-source-attributes-igmp-mld-snooping;
description "IGMP snooping information";
leaf address { leaf last-reporter {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IPV4 address"; "Address of the last host which has sent report
} to join the multicast group.";
}
uses instance-state-group-attributes-igmp-mld-snooping; list host {
if-feature explicit-tracking;
key "host-address";
description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf last-reporter { leaf host-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Address of the last host which has sent report to join "Multicast membership host address.";
the multicast group.";
} }
leaf host-filter-mode {
list source { type enumeration {
key "address"; enum "include" {
description "Source IPV4 address for multicast stream";
leaf address {
type inet:ipv4-address;
description "Source IPV4 address for multicast stream";
}
uses instance-state-source-attributes-igmp-mld-snooping;
leaf last-reporter {
type inet:ipv4-address;
description
"Address of the last host which has sent report to join
the multicast group.";
}
list host {
if-feature explicit-tracking;
key "host-address";
description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf host-address {
type inet:ipv4-address;
description description
"Multicast membership host address."; "In include mode";
} }
leaf host-filter-mode { enum "exclude" {
type enumeration {
enum "include" {
description
"In include mode";
}
enum "exclude" {
description
"In exclude mode.";
}
}
description description
"Filter mode for a multicast membership "In exclude mode.";
host may be either include or exclude.";
} }
}// list host }
} // list source
} // list group
} // instance-state-attributes-igmp-snooping
grouping instance-state-attributes-igmp-mld-snooping {
description
"State attributes for both IGMP and MLD Snooping of each
VLAN or l2vpn instance or EVPN instance.";
leaf entries-count {
type uint32;
config false;
description description
"The number of L2 multicast entries in IGMP and MLD "Filter mode for a multicast membership
Snooping."; host may be either include or exclude.";
} }
}// list host
leaf-list bridge-mrouter-interface { } // list source
} // list group
} // instance-state-attributes-igmp-snooping
when "../type = 'bridge'"; grouping instance-state-attributes-igmp-mld-snooping {
type if:interface-ref;
config false;
description " mrouter interface in bridge fowarding";
} description
"State attributes for IGMP & MLD snooping instance.";
leaf-list l2vpn-mrouter-interface-ac { leaf entries-count {
type uint32;
config false;
description
"The number of L2 multicast entries in IGMP & MLD snooping";
}
when "../type = 'l2vpn'"; leaf-list bridge-mrouter-interface {
type if:interface-ref; when "../type = 'bridge'";
config false; type if:interface-ref;
description " mrouter interface whose type is interface in config false;
l2vpn fowarding"; description "mrouter interface in BRIDGE forwarding";
}
} leaf-list l2vpn-mrouter-interface-ac {
when "../type = 'l2vpn'";
type if:interface-ref;
config false;
description "mrouter interface whose type is interface
in L2VPN forwarding";
leaf-list l2vpn-mrouter-interface-pw { }
when "../type = 'l2vpn'"; leaf-list l2vpn-mrouter-interface-pw {
type l2vpn-instance-pw-ref; when "../type = 'l2vpn'";
config false; type l2vpn-instance-pw-ref;
description " mrouter interface whose type is pw in l2vpn config false;
fowarding"; description "mrouter interface whose type is PW
in L2VPN forwarding";
}
} // instance-config-attributes-igmp-mld-snooping
} grouping instance-state-attributes-mld-snooping {
description
"State attributes for MLD snooping of each VLAN.";
} // instance-config-attributes-igmp-mld-snooping uses instance-state-attributes-igmp-mld-snooping;
grouping instance-state-attributes-mld-snooping { list group {
key "address";
config false;
description "MLD snooping statistics information";
leaf address {
type inet:ipv6-address;
description description
"State attributes for MLD snooping of each VLAN."; "Multicast group IPV6 address";
}
uses instance-state-attributes-igmp-mld-snooping; uses instance-state-group-attributes-igmp-mld-snooping;
list group { leaf last-reporter {
type inet:ipv6-address;
description
"Address of the last host which has sent report
to join the multicast group.";
}
list source {
key "address"; key "address";
description "Source IPV6 address for multicast stream";
config false; leaf address {
description "MLD snooping statistics information"; type inet:ipv6-address;
description "Source IPV6 address for multicast stream";
leaf address { }
type inet:ipv6-address; uses instance-state-source-attributes-igmp-mld-snooping;
description
"Multicast group IPV6 address";
}
uses instance-state-group-attributes-igmp-mld-snooping;
leaf last-reporter { leaf last-reporter {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Address of the last host which has sent report to join "Address of the last host which has sent report
the multicast group."; to join the multicast group.";
} }
list source {
key "address";
description "Source IPV6 address for multicast stream";
leaf address {
type inet:ipv6-address;
description "Source IPV6 address for multicast stream";
}
uses instance-state-source-attributes-igmp-mld-snooping; list host {
if-feature explicit-tracking;
key "host-address";
description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf last-reporter { leaf host-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Address of the last host which has sent report to join "Multicast membership host address.";
the multicast group."; }
} leaf host-filter-mode {
type enumeration {
list host { enum "include" {
if-feature explicit-tracking;
key "host-address";
description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf host-address {
type inet:ipv6-address;
description description
"Multicast membership host address."; "In include mode";
} }
leaf host-filter-mode { enum "exclude" {
type enumeration {
enum "include" {
description
"In include mode";
}
enum "exclude" {
description
"In exclude mode.";
}
}
description description
"Filter mode for a multicast membership "In exclude mode.";
host may be either include or exclude.";
} }
}// list host }
description
} // list source "Filter mode for a multicast membership
} // list group host may be either include or exclude.";
}
} // instance-state-attributes-mld-snooping }// list host
} // list source
grouping instance-state-source-attributes-igmp-mld-snooping { } // list group
description } // instance-state-attributes-mld-snooping
"State attributes for both IGMP and MLD Snooping of each VLAN
or l2vpn instance or EVPN instance.";
leaf-list bridge-outgoing-interface {
when "../../../type = 'bridge'";
type if:interface-ref;
description "Outgoing interface in bridge fowarding";
}
leaf-list l2vpn-outgoing-ac { grouping instance-state-source-attributes-igmp-mld-snooping {
when "../../../type = 'l2vpn'"; description
type l2vpn-instance-ac-ref; "State attributes for IGMP & MLD snooping instance.";
description "Outgoing AC in L2VPN fowarding";
} leaf-list bridge-outgoing-interface {
when "../../../type = 'bridge'";
type if:interface-ref;
description "Outgoing interface in BRIDGE forwarding";
}
leaf-list l2vpn-outgoing-ac {
when "../../../type = 'l2vpn'";
type l2vpn-instance-ac-ref;
description "Outgoing AC in L2VPN forwarding";
}
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 forwarding";
}
} leaf up-time {
type uint32;
units seconds;
description "The time elapsed since L2 multicast
record created";
}
leaf up-time { leaf expire {
type uint32; type uint32;
units seconds; units seconds;
description "The time elapsed since the device created L2 description
multicast record"; "The time left before multicast group timeout.";
} }
leaf expire { leaf host-count {
type uint32; if-feature explicit-tracking;
units seconds; type uint32;
description description
"The time left before multicast group timeout."; "The number of host addresses.";
} }
} // instance-state-source-attributes-igmp-mld-snooping
leaf host-count { grouping general-statistics-error {
if-feature explicit-tracking; description
type uint32; "A grouping defining statistics attributes for errors.";
description
"The number of host addresses.";
}
} // instance-state-source-attributes-igmp-mld-snooping leaf checksum {
type yang:counter64;
description
"The number of checksum errors.";
}
leaf too-short {
type yang:counter64;
description
"The number of messages that are too short.";
}
} // general-statistics-error
grouping general-statistics-sent-received {
description
"A grouping defining statistics attributes.";
grouping general-statistics-error { leaf query {
type yang:counter64;
description description
"A grouping defining statistics attributes for errors."; "The number of query messages.";
}
leaf checksum { leaf membership-report-v1 {
type yang:counter64; type yang:counter64;
description
"The number of checksum errors.";
}
leaf too-short {
type yang:counter64;
description
"The number of messages that are too short.";
}
} // general-statistics-error
grouping general-statistics-sent-received {
description description
"A grouping defining statistics attributes."; "The number of membership report v1 messages.";
}
leaf query {
type yang:counter64;
description
"The number of query messages.";
}
leaf membership-report-v1 {
type yang:counter64;
description
"The number of membership report v1 messages.";
}
leaf membership-report-v2 { leaf membership-report-v2 {
type yang:counter64; type yang:counter64;
description description
"The number of membership report v2 messages."; "The number of membership report v2 messages.";
}
}
leaf membership-report-v3 { leaf membership-report-v3 {
type yang:counter64; type yang:counter64;
description description
"The number of membership report v3 messages."; "The number of membership report v3 messages.";
} }
leaf leave { leaf leave {
type yang:counter64; type yang:counter64;
description description
"The number of leave messages."; "The number of leave messages.";
} }
leaf non-member-leave { leaf non-member-leave {
type yang:counter64; type yang:counter64;
description description
"The number of non member leave messages."; "The number of non member leave messages.";
} }
leaf pim { leaf pim {
type yang:counter64; type yang:counter64;
description description
"The number of pim hello messages."; "The number of pim hello messages.";
} }
} // general-statistics-sent-received } // general-statistics-sent-received
grouping interface-endpoint-attributes-igmp-snooping { grouping interface-endpoint-attributes-igmp-snooping {
description "interface attributes for igmp snooping"; description "interface attributes for IGMP snooping";
list host { list host {
if-feature explicit-tracking; if-feature explicit-tracking;
key "host-address"; key "host-address";
config false;
config false; description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf host-address {
type inet:ipv4-address;
description
"Multicast membership host address.";
}
leaf host-filter-mode {
type enumeration {
enum "include" {
description description
"List of multicast membership hosts "In include mode";
of the specific multicast source-group."; }
enum "exclude" {
leaf host-address { description
type inet:ipv4-address; "In exclude mode.";
description }
"Multicast membership host address."; }
} description
leaf host-filter-mode { "Filter mode for a multicast membership
type enumeration { host may be either include or exclude.";
enum "include" { }
description }// list host
"In include mode"; } // interface-endpoint-attributes-igmp-snooping
} grouping interface-endpoint-attributes-mld-snooping {
enum "exclude" {
description
"In exclude mode.";
}
}
description
"Filter mode for a multicast membership
host may be either include or exclude.";
}
}// list host
} // interface-endpoint-attributes-igmp-snooping
grouping interface-endpoint-attributes-mld-snooping { description "interface endpoint attributes MLD snooping";
description "interface endpoint attributes mld snooping"; list host {
list host { if-feature explicit-tracking;
if-feature explicit-tracking; key "host-address";
key "host-address"; config false;
config false; description
"List of multicast membership hosts
of the specific multicast source-group.";
leaf host-address {
type inet:ipv6-address;
description
"Multicast membership host address.";
}
leaf host-filter-mode {
type enumeration {
enum "include" {
description description
"List of multicast membership hosts "In include mode";
of the specific multicast source-group."; }
enum "exclude" {
description
"In exclude mode.";
}
}
description
"Filter mode for a multicast membership
host may be either include or exclude.";
}
}// list host
} // interface-endpoint-attributes-mld-snooping
leaf host-address {
type inet:ipv6-address;
description
"Multicast membership host address.";
}
leaf host-filter-mode {
type enumeration {
enum "include" {
description
"In include mode";
}
enum "exclude" {
description
"In exclude mode.";
}
}
description
"Filter mode for a multicast membership
host may be either include or exclude.";
}
}// list host
} // interface-endpoint-attributes-mld-snooping
/* /*
* igmp-snooping-instance * igmp-snooping-instance
*/ */
container igmp-snooping-instances { container igmp-snooping-instances {
description description
"igmp-snooping-instance list"; "igmp-snooping-instance list";
list igmp-snooping-instance { list igmp-snooping-instance {
key "name"; key "name";
description description
"IGMP Snooping instance to configure the igmp- "IGMP snooping instance to configure the igmp-snooping.";
snooping.";
leaf name { leaf name {
type string; type string;
description description
"Name of the igmp-snooping-instance to configure the igmp "Name of the igmp-snooping-instance";
snooping."; }
}
leaf type { leaf type {
type enumeration { type enumeration {
enum "bridge" { enum "bridge" {
description "bridge"; description "BRIDGE";
} }
enum "l2vpn" { enum "l2vpn" {
description "l2vpn"; description "L2VPN";
} }
} }
description "The type indicates bridge or l2vpn."; description "The type indicates BRIDGE or L2VPN.";
} }
uses instance-config-attributes-igmp-snooping { uses instance-config-attributes-igmp-snooping;
if-feature per-instance-config;
}
uses instance-state-attributes-igmp-snooping; uses instance-state-attributes-igmp-snooping;
} //igmp-snooping-instance } //igmp-snooping-instance
} //igmp-snooping-instances } //igmp-snooping-instances
/* /*
* mld-snooping-instance * mld-snooping-instance
*/ */
container mld-snooping-instances {
description
"mld-snooping-instance list";
list mld-snooping-instance { container mld-snooping-instances {
key "name"; description
description "mld-snooping-instance list";
"MLD Snooping instance to configure the mld-snooping.";
leaf name { list mld-snooping-instance {
type string; key "name";
description description
"Name of the mld-snooping-instance to configure the mld "MLD snooping instance to configure the mld-snooping.";
snooping.";
}
leaf type { leaf name {
type enumeration { type string;
enum "bridge" { description
description "bridge"; "Name of the mld-snooping-instance";
} }
enum "l2vpn" {
description "l2vpn";
}
}
description "The type indicates bridge or l2vpn.";
}
uses instance-config-attributes-mld-snooping { leaf type {
if-feature per-instance-config; type enumeration {
enum "bridge" {
description "BRIDGE";
} }
enum "l2vpn" {
description "L2VPN";
}
}
description "The type indicates BRIDGE or L2VPN.";
}
uses instance-state-attributes-mld-snooping; uses instance-config-attributes-mld-snooping;
} //mld-snooping-instance
} //mld-snooping-instances
container bridges { uses instance-state-attributes-mld-snooping;
description
"Apply igmp-mld-snooping instance in the bridge scenario";
list bridge { } //mld-snooping-instance
key name; } //mld-snooping-instances
description /* augments */
"bridge list";
leaf name { augment "/dot1q:bridges/dot1q:bridge" {
type name-type; description
description "Reference IGMP & MLD snooping instance in BRIDGE scenario";
"bridge name";
} leaf igmp-snooping-instance {
leaf igmp-snooping-instance { type igmp-snooping-instance-ref;
type igmp-snooping-instance-ref; description
description "Configure igmp-snooping instance under the "Configure IGMP snooping instance under bridge view";
bridge view"; }
} leaf mld-snooping-instance {
leaf mld-snooping-instance { type mld-snooping-instance-ref;
type mld-snooping-instance-ref; description
description "Configure mld-snooping instance under the "Configure MLD snooping instance under bridge view";
bridge view"; }
} }
list component {
key "name";
description
" ";
leaf name { augment "/dot1q:bridges/dot1q:bridge"+
type string; "/dot1q:component/dot1q:bridge-vlan/dot1q:vlan" {
description description
"The name of the Component."; "Refrence IGMP & MLD snooping instance in BRIDGE scenario";
}
container bridge-vlan {
description "bridge vlan";
list vlan {
key "vid";
description
"";
leaf vid { leaf igmp-snooping-instance {
type vlan-index-type; type igmp-snooping-instance-ref;
description description
"The VLAN identifier to which this entry "Configure IGMP snooping instance under VLAN view";
applies."; }
} leaf mld-snooping-instance {
leaf igmp-snooping-instance { type mld-snooping-instance-ref;
type igmp-snooping-instance-ref; description
description "Configure igmp-snooping instance "Configure MLD snooping instance under VLAN view";
under the vlan view"; }
} }
leaf mld-snooping-instance {
type mld-snooping-instance-ref;
description "Configure mld-snooping instance
under the vlan view";
}
}//vlan augment "/ni:network-instances/ni:network-instance"+
}//bridge-vlan "/ni:ni-type/l2vpn:l2vpn" {
}//component
}//bridge
} //bridges
container l2vpn-instances { description
description "Apply igmp-mld-snooping instance in the l2vpn "Reference IGMP & MLD snooping instance in L2VPN scenario";
scenario";
list l2vpn-instance { leaf igmp-snooping-instance {
key "name"; type igmp-snooping-instance-ref;
description "An l2vpn service instance"; description
"Configure IGMP snooping instance in L2VPN scenario";
}
leaf mld-snooping-instance {
type mld-snooping-instance-ref;
description
"Configure MLD snooping instance in L2VPN scenario";
}
}
augment "/if:interfaces/if:interface" {
description
"Augment interface for referencing attributes
which only fit for interface view.";
leaf name { container igmp-mld-snooping {
type string; description
description "Name of l2vpn service instance"; "igmp-mld-snooping related attributes under interface view";
}
leaf igmp-snooping-instance { leaf enable {
type igmp-snooping-instance-ref; type boolean;
description "Configure igmp-snooping instance under the default false;
l2vpn-instance view"; description
} "Set the value to true to enable IGMP and MLD snooping
leaf mld-snooping-instance { in the VLAN instance.";
type mld-snooping-instance-ref; }
description "Configure mld-snooping instance under the
l2vpn-instance view";
}
leaf version {
type uint8 {
range "1..3";
}
default 2;
description "IGMP and MLD snooping version.";
} }
leaf type {
type enumeration {
enum "bridge" {
description "BRIDGE";
}
enum "l2vpn" {
description "L2VPN";
}
}
description "The type indicates BRIDGE or L2VPN.";
} }
/* augments */ container static-mrouter-interface {
description
"Container for choice static-mrouter-interface";
augment "/if:interfaces/if:interface" { choice static-mrouter-interface {
description "Augment interface for referencing attributes which description
only fit for interface view."; "Configure static multicast router interface
under the interface view";
container igmp-mld-snooping { case bridge {
description when "../type = 'bridge'" {
"igmp-mld-snooping related attributes under interface view"; description
"Applies to BRIDGE scenario.";
}
leaf enable { description
if-feature admin-enable; "Applies to BRIDGE scenario.";
type boolean;
default false;
description
"Set the value to true to enable IGMP and MLD Snooping in
the VLAN instance.";
}
leaf version { leaf bridge-name {
type uint8 { type string;
range "1..3"; description
} "The name for a bridge.
description "IGMP and MLD Snooping version."; Each interface belongs to only one bridge.";
}
leaf type { }
type enumeration { leaf-list vlan-id {
enum "bridge" { type uint32;
description "bridge"; description
} "The VLAN ids for bridge. If you don't specify
enum "l2vpn" { VLAN id here, the interface serves as the mrouter
description "l2vpn"; interface for all the VLANs in this bridge.";
} }
}
case l2vpn {
when "../type = 'l2vpn'" {
description
"Applies to L2VPN scenario.";
} }
description "The type indicates bridge or l2vpn.";
}
container static-mrouter-interface {
description description
"Container for choice static-mrouter-interface"; "Applies to L2VPN scenario.";
choice static-mrouter-interface {
description
"Configure static multicast router interface under the
interface view";
case bridge {
when "../type = 'bridge'" {
description
"Applies to bridge scenario.";
}
description
"Applies to bridge scenario.";
leaf bridge-name { leaf l2vpn-instance-name {
type string; type string;
description description
"The name for a bridge. Each interface "The L2VPN instance name applied in the interface";
belongs to only one bridge.";
} }
leaf-list vlan-id { }
type uint32; } // choice static-mrouter-interface
description } // container static-mrouter-interface
"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.";
}
} container static-l2-multicast-group {
case l2vpn { description
when "../type = 'l2vpn'" { "Container for static-l2-multicast-group";
description
"Applies to l2vpn scenario.";
}
description
"Applies to l2vpn scenario.";
leaf l2vpn-instance-name { choice static-l2-multicast-group {
type string; description
description "Configure static l2 multicast group
"The l2vpn instance name applied in the under interface view";
interface";
} case bridge {
} when "../type = 'bridge'" {
description
"Applies to BRIDGE scenario.";
} // choice static-mrouter-interface }
} // container static-mrouter-interface
container static-l2-multicast-group {
description description
"Container for static-l2-multicast-group"; "Applies to BRIDGE scenario.";
choice static-l2-multicast-group {
description
"Configure static l2 multicast group under the
interface view";
case bridge {
when "../type = 'bridge'" {
description
"Applies to bridge scenario.";
}
description
"Applies to bridge scenario.";
leaf bridge-name {
type string;
description
"bridge name.";
}
list bridge-group-v4 {
key "group source-addr";
description
"A static multicast route, (*,G) or (S,G).";
leaf group {
type inet:ipv4-address;
description
"Multicast group IPV4 address";
}
leaf source-addr {
type source-ipv4-addr-type;
description
"Multicast source IPV4 address.";
}
leaf-list vlan-id { leaf bridge-name {
type uint32; type string;
description description
"vlan id."; "bridge name.";
} }
} list bridge-group-v4 {
key "group source-addr";
description
"A static multicast route, (*,G) or (S,G).";
list bridge-group-v6 { leaf group {
key "group source-addr"; type inet:ipv4-address;
description description
"A static multicast route, (*,G) or (S,G)."; "Multicast group IPV4 address";
}
leaf group { leaf source-addr {
type inet:ipv6-address; type source-ipv4-addr-type;
description description
"Multicast group IPV6 address"; "Multicast source IPV4 address.";
} }
leaf source-addr { leaf-list vlan-id {
type source-ipv6-addr-type; type uint32;
description description
"Multicast source IPV6 address."; "VLAN id.";
} }
}
leaf-list vlan-id { list bridge-group-v6 {
type uint32; key "group source-addr";
description description
"vlan id."; "A static multicast route, (*,G) or (S,G).";
}
} leaf group {
type inet:ipv6-address;
description
"Multicast group IPV6 address";
}
} leaf source-addr {
case l2vpn { type source-ipv6-addr-type;
description
"Multicast source IPV6 address.";
}
leaf-list vlan-id {
type uint32;
description
"VLAN id.";
}
}
} // case bridge
when "../type = 'l2vpn'" { case l2vpn {
description
"Applies to l2vpn scenario.";
}
description
"Applies to l2vpn scenario.";
list l2vpn-group-v4 { when "../type = 'l2vpn'" {
key "group source-addr"; description
description "A static multicast route, (*,G) or "Applies to L2VPN scenario.";
(S,G)."; }
description
"Applies to L2VPN scenario.";
leaf group { list l2vpn-group-v4 {
type inet:ipv4-address; key "group source-addr";
description description
"Multicast group IPV4 address"; "A static multicast route, (*,G) or (S,G).";
}
leaf source-addr { leaf group {
type source-ipv4-addr-type; type inet:ipv4-address;
description description
"Multicast source IPV4 address."; "Multicast group IPV4 address";
} }
leaf l2vpn-instance-name { leaf source-addr {
type string; type source-ipv4-addr-type;
description description
"The l2vpn instance name applied in the "Multicast source IPV4 address.";
interface"; }
} leaf l2vpn-instance-name {
} type string;
list l2vpn-group-v6 { description
"L2VPN instance name applied in the interface";
}
}
key "group source-addr"; list l2vpn-group-v6 {
description key "group source-addr";
"A static multicast route, (*,G) or (S,G).";
leaf group { description
type inet:ipv6-address; "A static multicast route, (*,G) or (S,G).";
description
"Multicast group IPV6 address";
}
leaf source-addr { leaf group {
type source-ipv6-addr-type; type inet:ipv6-address;
description description
"Multicast source IPV6 address."; "Multicast group IPV6 address";
} }
leaf l2vpn-instance-name { leaf source-addr {
type string; type source-ipv6-addr-type;
description description
"The l2vpn instance name applied in the "Multicast source IPV6 address.";
interface"; }
} leaf l2vpn-instance-name {
} type string;
} description
"L2VPN instance name applied in the interface";
}
}
}
} //choice static-l2-multicast-group
} // container static-l2-multicast-group
} //choice static-l2-multicast-group container statistics {
config false;
description
"A collection of interface-related statistics objects.";
} // container static-l2-multicast-group uses general-state-attributes;
}
}
}
container statistics { /* RPCs */
config false;
description
"A collection of interface-related statistics objects.";
uses general-state-attributes; rpc clear-igmp-snooping-groups {
if-feature rpc-clear-groups;
description
"Clears the specified IGMP snooping cache tables.";
} input {
leaf name {
type string;
description
"Name of the igmp-snooping-instance";
} }
} leaf group {
type inet:ipv4-address;
/* RPCs */
rpc clear-igmp-snooping-groups {
if-feature rpc-clear-groups;
description description
"Clears the specified IGMP Snooping cache tables."; "Multicast group IPv4 address.
If it is not specified, all IGMP snooping group tables
input {
leaf name { are cleared.";
type string; }
description
"Name of the igmp-snooping-instance";
}
leaf group { leaf source {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast group IPv4 address. "Multicast source IPv4 address.
If it is not specified, all IGMP snooping group tables If it is not specified, all IGMP snooping source-group
are tables are cleared.";
cleared."; }
} }
} // rpc clear-igmp-snooping-groups
leaf source { rpc clear-mld-snooping-groups {
type inet:ipv4-address; if-feature rpc-clear-groups;
description description
"Multicast source IPv4 address. "Clears the specified MLD snooping cache tables.";
If it is not specified, all IGMP snooping source-group
tables are
cleared.";
}
}
} // rpc clear-igmp-snooping-groups
rpc clear-mld-snooping-groups { input {
if-feature rpc-clear-groups; leaf name {
type string;
description description
"Clears the specified MLD Snooping cache tables."; "Name of the mld-snooping-instance";
}
input {
leaf name {
type string;
description
"Name of the mld-snooping-instance";
}
leaf group { leaf group {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast group IPv6 address. "Multicast group IPv6 address.
If it is not specified, all MLD snooping group tables are If it is not specified, all MLD snooping group tables are
cleared."; cleared.";
} }
leaf source { leaf source {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast source IPv6 address. "Multicast source IPv6 address.
If it is not specified, all MLD snooping source-group If it is not specified, all MLD snooping source-group
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 YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
skipping to change at page 44, line 7 skipping to change at page 38, line 7
namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-snooping
prefix: ims prefix: ims
reference: RFC XXXX reference: RFC XXXX
-------------------------------------------------------------------- --------------------------------------------------------------------
6. Normative References 6. Normative References
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [P802.1Qcp/D2.2] IEEE Approved Draft Standard for Local and
the Network Configuration Protocol (NETCONF)", RFC 6020, Metropolitan Area Networks, "Bridges and Bridged Networks
October 2010. Amendment: YANG Data Model", Mar 2018
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC4541] M. Christensen, K. Kimball, F. Solensky, "Considerations
for Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) Snooping Switches", RFC 4541, May
2006.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710, October 1999. Listener Discovery (MLD) for IPv6", RFC 2710, October 1999.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using [RFC4541] M. Christensen, K. Kimball, F. Solensky, "Considerations
InternetGroup Management Protocol Version 3 (IGMPv3) and for Internet Group Management Protocol (IGMP) and Multicast
Multicast Listener Discovery Protocol Version 2 (MLDv2) for Listener Discovery (MLD) Snooping Switches", RFC 4541, May
Source-Specific Multicast", RFC 4604, August 2006. 2006.
[RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet
Group Management Protocol Version 3 (IGMPv3) and Multicast
Listener Discovery Protocol Version 2 (MLDv2) for Source-
Specific Multicast", RFC 4604, August 2006.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006. IP", RFC 4607, August 2006.
[draft-ietf-pim-igmp-mld-yang-01] X. Liu, F. Guo, M. Sivakumar, P. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
McAllister, A. Peter, "A YANG data model for Internet Group the Network Configuration Protocol (NETCONF)", RFC 6020,
Management Protocol (IGMP) and Multicast Listener Discovery October 2010.
(MLD)", draft-ietf-pim-igmp-mld-yang-01, October 28, 2016.
[draft-ietf-pim-igmp-mld-yang-03] X. Liu, F. Guo, M. Sivakumar, P. [RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991,
July 2013.
[RFC8342] M. Bjorklund and J. Schoenwaelder, "Network Management
Datastore Architecture (NMDA)", RFC 8342, March 2018.
[RFC8343] M. Bjorklund, "A YANG Data Model for Interface Management",
RFC 8343, March 2018.
[draft-ietf-pim-igmp-mld-yang-06] X. Liu, F. Guo, M. Sivakumar, P.
McAllister, A. Peter, "A YANG data model for Internet Group McAllister, A. Peter, "A YANG data model for Internet Group
Management Protocol (IGMP) and Multicast Listener Discovery Management Protocol (IGMP) and Multicast Listener Discovery
(MLD)", draft-ietf-pim-igmp-mld-yang-03, March 13, 2017. (MLD)", draft-ietf-pim-igmp-mld-yang-06, Oct 20, 2017.
[draft-dsdt-nmda-guidelines-01] M. Bjorklund, J. Schoenwaelder, P. [draft-dsdt-nmda-guidelines-01] M. Bjorklund, J. Schoenwaelder, P.
Shafer, K. Watsen, R. Wilton, "Guidelines for YANG Module Shafer, K. Watsen, R. Wilton, "Guidelines for YANG Module
Authors (NMDA)", draft-dsdt-nmda-guidelines-01, May 2017 Authors (NMDA)", draft-dsdt-nmda-guidelines-01, May 2017
[draft-bjorklund-netmod-rfc7223bis-00] M. Bjorklund, "A YANG Data [draft-bjorklund-netmod-rfc7223bis-00] M. Bjorklund, "A YANG Data
Model for Interface Management", draft-bjorklund-netmod- Model for Interface Management", draft-bjorklund-netmod-
rfc7223bis-00, August 21, 2017 rfc7223bis-00, August 21, 2017
[draft-bjorklund-netmod-rfc7277bis-00] M. Bjorklund, "A YANG Data [draft-bjorklund-netmod-rfc7277bis-00] M. Bjorklund, "A YANG Data
skipping to change at page 45, line 23 skipping to change at page 39, line 32
[draft-ietf-netmod-revised-datastores-03] M. Bjorklund, J. [draft-ietf-netmod-revised-datastores-03] M. Bjorklund, J.
Schoenwaelder, P. Shafer, K. Watsen, R. Wilton, "Network Schoenwaelder, P. Shafer, K. Watsen, R. Wilton, "Network
Management Datastore Architecture", draft-ietf-netmod- Management Datastore Architecture", draft-ietf-netmod-
revised-datastores-03, July 3, 2017 revised-datastores-03, July 3, 2017
[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-08] 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,
30, 2017 February 17, 2018
[draft-ietf-rtgwg-ni-model-12] L. Berger, C. Hopps, A. Lindem, X.
Liu, "YANG Model for Network Instances", draft-ietf-rtgwg-
ni-model-12.txt, March 19, 2018
Appendix A. Data Tree Example Appendix A. Data Tree Example
This section contains an example of an instance data tree in the JSON This section contains an example of an instance data tree in the JSON
encoding [RFC7951], containing both configuration and state data. encoding [RFC7951], containing both configuration and state data.
| +-------+ | +-----------+
| eth2/1 | | eth2/2 | +------------+ + Source +
| +-----+ R2 +-----------+----+ Receiver 1 + +-----+-----+
| | | | | +------------+ |
| | +-------+ | -----------------+----------------------------
| | | |eth1/1
| +-------+ eth1/2 | +-------+ | +---+---+
| | +-----------+ | | eth3/2 | +------------+ + R1 +
eth1/1 +--+ R1 | | R3 +-----------+----+ Receiver 2 + +-+---+-+
| | +-----------------+ | | +------------+ eth1/2 | \ eth1/3
+-------+ | +-------+ eth1/3 eth3/1 +-------+ | | \
| | | | | \
| +--+ | | \
| | | | | \
| | | | eth2/1 | \ eth3/1
+-------+ | | +---+---+ +--+---+
Source + R2 + + R3 +
+---+---+ +--+---+
eth2/2 | | eth3/2
| |
---------------+----------+-------------------
| |
| |
+--------+--+ +---+--------+
+ Receiver1 + + Receiver2 +
+-----------+ +------------+
The configuration instance data tree for R1 in the above figure could be The configuration instance data tree for R1 in the above figure could be
as follows: as follows:
{ {
"ietf-igmp-mld-snooping:igmp-snooping-instances": { "ietf-igmp-mld-snooping:igmp-snooping-instances": {
"igmp-snooping-instance": [ "igmp-snooping-instance": [
{ {
"name": "ins101", "name": "ins101",
"type": "bridge", "type": "bridge",
"enable": true "enable": true
} }
] ]
}, },
"ietf-igmp-mld-snooping:mld-snooping-instances": { "ietf-igmp-mld-snooping:mld-snooping-instances": {
"mld-snooping-instance": [ "mld-snooping-instance": [
{ {
"name": "ins102", "name": "ins102",
"type": "bridge", "type": "bridge",
"enable": true "enable": true
} }
] ]
}, },
"ietf-igmp-mld-snooping:bridges": { "ieee802-dot1q-bridge:bridges": {
"bridge": [ "bridge": [
{ {
"name": "isp", "name": "isp",
"component": [ "address": "00-23-ef-a5-77-12",
{ "bridge-type": "ieee802-dot1q-bridge:customer-vlan-bridge",
"name": "comp1", "component": [
"bridge-vlan": {
"vlan": [
{
"vid": 101,
"igmp-snooping-instance": "ins101"
},
{ {
"vid": 102, "name": "comp1",
"mld-snooping-instance": "ins102" "type": "ieee802-dot1q-bridge:c-vlan-component",
"bridge-vlan": {
"vlan": [
{
"vid": 101,
"ietf-igmp-mld-snooping:igmp-snooping-instance": "ins101"
},
{
"vid": 102,
"ietf-igmp-mld-snooping:mld-snooping-instance": "ins102"
}
]
}
} }
] ]
} }
} ]
] }
} }
]
}
}
The corresponding operational state data for R1 could be as follows: The corresponding operational state data for R1 could be as follows:
{ {
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interface": [ "interface": [
{
"name": "1/1",
"type": "iana-if-type:ethernetCsmacd",
"admin-status": "up",
"if-index": 214748,
"oper-status": "up",
"statistics": {
"discontinuity-time": "2018-05-23T12:34:56-05:00"
}
},
{ {
"name": "1/2", "name": "1/1",
"type": "iana-if-type:ethernetCsmacd", "type": "iana-if-type:ethernetCsmacd",
"admin-status": "up", "admin-status": "up",
"if-index": 214749, "if-index": 214748,
"oper-status": "up", "oper-status": "up",
"statistics": { "statistics": {
"discontinuity-time": "2018-05-23T12:35:06-05:02" "discontinuity-time": "2018-05-23T12:34:56-05:00"
} }
},
{
"name": "1/2",
"type": "iana-if-type:ethernetCsmacd",
"admin-status": "up",
"if-index": 214749,
"oper-status": "up",
"statistics": {
"discontinuity-time": "2018-05-23T12:35:06-05:02"
}
}
]
},
"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:igmp-snooping-instances": { "ietf-igmp-mld-snooping:mld-snooping-instances": {
"igmp-snooping-instance": [ "mld-snooping-instance": [
{ {
"name": "ins101", "name": "ins102",
"type": "bridge", "type": "bridge",
"enable": true, "enable": true,
"forwarding-mode": "ip", "forwarding-mode": "ip",
"explicit-tracking": false, "explicit-tracking": false,
"exclude-lite": false, "exclude-lite": false,
"send-query": true, "send-query": true,
"immediate-leave": [null], "immediate-leave": [null],
"last-member-query-interval": 1, "last-member-query-interval": 1,
"query-interval": 125, "query-interval": 125,
"query-max-response-time": 10, "query-max-response-time": 10,
"require-router-alert": false, "require-router-alert": false,
"robustness-variable": 2, "robustness-variable": 2,
"entries-count": 1, "entries-count": 1,
"bridge-mrouter-interface": ["1/1"], "bridge-mrouter-interface": ["1/1"],
"group": [ "group": [
{ {
"address": "223.0.0.1", "address": "FF0E::1",
"mac-address": "01:00:5e:00:00:01", "mac-address": "01:00:5e:00:00:01",
"expire": 120, "expire": 120,
"up-time": 180,
"last-reporter": "2001::1",
"source": [
{
"address": "3001::1",
"bridge-outgoing-interface": ["1/2"],
"up-time": 180, "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, "expire": 120,
"up-time": 180, "last-reporter": "2001::1"
"last-reporter": "2001::1", }
"source": [ ]
{ }
"address": "3001::1",
"bridge-outgoing-interface": ["1/2"], ]
"up-time": 180, }
"expire": 120, ]
"last-reporter": "2001::1" }
} }
]
}
]
}
]
}
}
Authors' Addresses 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
skipping to change at page 49, line 35 skipping to change at page 45, line 36
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 Juniper
510 McCarthy Boulevard 510 McCarthy Boulevard
Milpitas, California Milpitas, California
USA USA
EMail: sivakumar.mahesh@gmail.com EMail: sivakumar.mahesh@gmail.com
 End of changes. 330 change blocks. 
1688 lines changed or deleted 1415 lines changed or added

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