draft-ietf-pim-igmp-mld-yang-15.txt   rfc8652.txt 
PIM Working Group X. Liu
Internet-Draft Volta Networks
Intended Status: Standard Track F. Guo
Expires: December 14, 2019 Huawei
M. Sivakumar
Juniper
P. McAllister
Metaswitch Networks
A. Peter
Individual
June 14, 2019
A YANG Data Model for Internet Group Management Protocol (IGMP) and Internet Engineering Task Force (IETF) X. Liu
Multicast Listener Discovery (MLD) Request for Comments: 8652 Volta Networks
draft-ietf-pim-igmp-mld-yang-15 Category: Standards Track F. Guo
ISSN: 2070-1721 Huawei
M. Sivakumar
Juniper
P. McAllister
Metaswitch Networks
A. Peter
IP Infusion India
November 2019
Status of this Memo A YANG Data Model for the Internet Group Management Protocol (IGMP)
and Multicast Listener Discovery (MLD)
This Internet-Draft is submitted in full conformance with the Abstract
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document defines a YANG data model that can be used to configure
Task Force (IETF), its areas, and its working groups. Note that and manage Internet Group Management Protocol (IGMP) and Multicast
other groups may also distribute working documents as Internet- Listener Discovery (MLD) devices.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Status of This Memo
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on December 14, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8652.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described in include Simplified BSD License text as described in Section 4.e of
Section 4.e of the Trust Legal Provisions and are provided without the Trust Legal Provisions and are provided without warranty as
warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Abstract
This document defines a YANG data model that can be used to
configure and manage Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) devices.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction
1.1. Terminology...............................................3 1.1. Terminology
1.2. Tree Diagrams.............................................4 1.2. Conventions Used in This Document
1.3. Prefixes in Data Node Names...............................4 1.3. Tree Diagrams
2. Design of Data model...........................................4 1.4. Prefixes in Data Node Names
2.1. Scope of Model............................................4 2. Design of the Data Model
2.1.1. Parameters Not Covered at Global Level..................5 2.1. Scope of Model
2.1.2. Parameters Not Covered at Interface Level...............5 2.1.1. Parameters Not Covered at the Global Level
2.2. Optional Capabilities.....................................6 2.1.2. Parameters Not Covered at the Interface Level
2.3. Position of Address Family in Hierarchy...................6 2.2. Optional Capabilities
3. Module Structure...............................................7 2.3. Position of Address Family in Hierarchy
3.1. IGMP Configuration and Operational State..................7 3. Module Structure
3.2. MLD Configuration and Operational State..................10 3.1. IGMP Configuration and Operational State
3.3. IGMP and MLD Actions.....................................13 3.2. MLD Configuration and Operational State
4. IGMP and MLD YANG Module......................................13 3.3. IGMP and MLD Actions
5. Security Considerations.......................................43 4. IGMP and MLD YANG Module
6. IANA Considerations...........................................45 5. Security Considerations
7. Acknowledgments...............................................46 6. IANA Considerations
8. Contributing Authors..........................................46 7. References
9. References....................................................46 7.1. Normative References
9.1. Normative References.....................................46 7.2. Informative References
9.2. Informative References...................................48 Acknowledgments
Contributors
Authors' Addresses
1. Introduction 1. Introduction
YANG [RFC6020] [RFC7950] is a data definition language that was YANG [RFC6020] [RFC7950] is a data definition language that was
introduced to model the configuration and running state of a device introduced to model the configuration and running state of a device
managed using network management protocols such as NETCONF [RFC6241] managed using network management protocols such as NETCONF [RFC6241]
or RESTCONF [RFC8040]. YANG is now also being used as a component of or RESTCONF [RFC8040]. YANG is now also being used as a component of
wider management interfaces, such as command line interfaces (CLIs). wider management interfaces, such as command-line interfaces (CLIs).
This document defines a YANG data model that can be used to
configure and manage Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) devices. The protocol versions
include IGMPv1 [RFC1112], IGMPv2 [RFC2236], IGMPv3 [RFC3376], MLDv1
[RFC2710], and MLDv2 [RFC3810]. The core features of the IGMP and
MLD protocols are defined as required. Non-core features are
defined as optional in the provided data model.
The YANG model in this document conforms to the Network Management This document defines a YANG data model that can be used to configure
Datastore Architecture (NMDA) [RFC8342]. and manage Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) devices. The protocol versions include
IGMPv1 [RFC1112], IGMPv2 [RFC2236], IGMPv3 [RFC3376], MLDv1
[RFC2710], and MLDv2 [RFC3810]. The core features of the IGMP and
MLD protocols are defined as required. Non-core features are defined
as optional in the provided data model.
1.1. Terminology The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) [RFC8342].
The terminology for describing YANG data models is found in 1.1. Terminology
[RFC6020] and [RFC7950], including:
o augment The terminology for describing YANG data models is found in [RFC6020]
and [RFC7950], including:
o data model * augment
o data node * data model
o identity * data node
o module * identity
The following abbreviations are used in this document and the * module
defined model:
IGMP: The following abbreviations are used in this document and the defined
model:
Internet Group Management Protocol [RFC3376]. IGMP: Internet Group Management Protocol [RFC3376].
MLD: MLD: Multicast Listener Discovery [RFC3810].
Multicast Listener Discovery [RFC3810]. SSM: Source-Specific Multicast service model [RFC3569] [RFC4607].
SSM: 1.2. Conventions Used in This Document
Source-Specific Multicast service model [RFC3569] [RFC4607]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.2. Tree Diagrams 1.3. Tree Diagrams
Tree diagrams used in this document follow the notation defined in Tree diagrams used in this document follow the notation defined in
[RFC8340]. [RFC8340].
1.3. Prefixes in Data Node Names 1.4. Prefixes in Data Node Names
In this document, names of data nodes, actions, and other data model In this document, names of data nodes, actions, and other data model
objects are often used without a prefix, as long as it is clear from objects are often used without a prefix, as long as it is clear from
the context in which YANG module each name is defined. Otherwise, the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1. corresponding YANG module, as shown in Table 1.
+-----------+--------------------------+---------------------+ +----------+--------------------------+-----------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+-----------+--------------------------+---------------------+ +==========+==========================+===========+
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] | +----------+--------------------------+-----------+
| if | ietf-interfaces | [RFC8343] | | inet | ietf-inet-types | [RFC6991] |
| ip | ietf-ip | [RFC8344] | +----------+--------------------------+-----------+
| rt | ietf-routing | [RFC8349] | | if | ietf-interfaces | [RFC8343] |
| rt-types | ietf-routing-types | [RFC8294] | +----------+--------------------------+-----------+
| acl | ietf-access-control-list | [RFC8519] | | ip | ietf-ip | [RFC8344] |
+-----------+--------------------------+---------------------+ +----------+--------------------------+-----------+
| rt | ietf-routing | [RFC8349] |
+----------+--------------------------+-----------+
| rt-types | ietf-routing-types | [RFC8294] |
+----------+--------------------------+-----------+
| acl | ietf-access-control-list | [RFC8519] |
+----------+--------------------------+-----------+
Table 1: Prefixes and Corresponding YANG Modules Table 1: Prefixes and Corresponding YANG Modules
2. Design of Data model 2. Design of the Data Model
2.1. Scope of Model 2.1. Scope of Model
The model covers IGMPv1 [RFC1112], IGMPv2 [RFC2236], IGMPv3 The model covers IGMPv1 [RFC1112], IGMPv2 [RFC2236], IGMPv3
[RFC3376], MLDv1 [RFC2710], and MLDv2 [RFC3810]. [RFC3376], MLDv1 [RFC2710], and MLDv2 [RFC3810].
This model does not cover other IGMP and MLD related protocols such This model does not cover other IGMP- and MLD-related protocols such
as IGMP/MLD Proxy [RFC4605] or IGMP/MLD Snooping [RFC4541] etc., as IGMP/MLD Proxy [RFC4605] or IGMP/MLD Snooping [RFC4541] etc.,
which will be specified in separate documents. which will be specified in separate documents.
This model can be used to configure and manage various versions of This model can be used to configure and manage various versions of
IGMP and MLD protocols. The operational state data and statistics IGMP and MLD protocols. The operational state data and statistics
can be retrieved by this model. Even though no protocol specific can be retrieved by this model. Even though no protocol-specific
notifications are defined in this model, the subscription and push notifications are defined in this model, the subscription and push
mechanism defined in [I-D.ietf-netconf-subscribed-notifications] and mechanism defined in [RFC8639] and [RFC8641] can be implemented by
[I-D.ietf-netconf-yang-push] can be used by the user to subscribe to the user to subscribe to notifications on the data nodes in this
notifications on the data nodes in this model. model.
The model contains all the basic configuration parameters to operate The model contains all the basic configuration parameters to operate
the protocols listed above. Depending on the implementation choices, the protocols listed above. Depending on the implementation choices,
some systems may not allow some of the advanced parameters to be some systems may not allow some of the advanced parameters to be
configurable. The occasionally implemented parameters are modeled as configurable. The occasionally implemented parameters are modeled as
optional features in this model, while the rarely implemented optional features in this model, while the rarely implemented
parameters are not included this model and left for augmentation. parameters are not included in this model and left for augmentation.
This model can be extended, and has been structured in a way that This model can be extended, and it has been structured in a way that
such extensions can be conveniently made. such extensions can be conveniently made.
The protocol parameters covered in this model can been seen from the The protocol parameters covered in this model can been seen from the
model structure described in Section 3. model structure described in Section 3.
The protocol parameters that were considered but are not covered in The protocol parameters that were considered but are not covered in
this model are described in the following sections. this model are described in the following sections.
2.1.1. Parameters Not Covered at Global Level 2.1.1. Parameters Not Covered at the Global Level
The configuration parameters and operational states not covered on The configuration parameters and operational states not covered on an
an IGMP instance or an MLD instance are: IGMP instance or an MLD instance are:
o Explicit tracking * Explicit tracking
o Maximum transmit rate * Maximum transmit rate
o Last member query count * Last member query count
o Other querier present time * Other querier present time
o Send router alert * Send router alert
o Startup query interval * Startup query interval
o Startup query count * Startup query count
2.1.2. Parameters Not Covered at Interface Level 2.1.2. Parameters Not Covered at the Interface Level
The configuration parameters and operational states not covered on The configuration parameters and operational states not covered on an
an IGMP interface or an MLD interface are: IGMP interface or an MLD interface are:
o Disable router alert check * Disable router alert check
o Drop IGMP version 1, IGMP version 2, or MLD version 1 * Drop IGMP version 1, IGMP version 2, or MLD version 1
o Last member query count * Last member query count
o Maximum number of sources * Maximum number of sources
o Other querier present time * Other querier present time
o Passive mode * Passive mode
o Promiscuous mode * Promiscuous mode
o Query before immediate leave
o Send router alert * Query before immediate leave
2.2. Optional Capabilities * Send router alert
2.2. Optional Capabilities
This model is designed to represent the capabilities of IGMP and MLD This model is designed to represent the capabilities of IGMP and MLD
devices with various specifications, including the basic capability devices with various specifications, including the basic capability
subsets of the IGMP and MLD protocols. The main design goals of subsets of the IGMP and MLD protocols. The main design goals of this
this document are that the basic capabilities described in the model document are that the basic capabilities described in the model are
are supported by any major now-existing implementation, and that the supported by any major now-existing implementation, and that the
configuration of all implementations meeting the specifications is configuration of all implementations meeting the specifications is
easy to express through some combination of the optional features in easy to express through some combination of the optional features in
the model and simple vendor augmentations. the model and simple vendor augmentations.
There is also value in widely-supported features being standardized, There is also value in widely supported features being standardized,
to provide a standardized way to access these features, to save work to provide a standardized way to access these features, to save work
for individual vendors, and so that mapping between different for individual vendors, and so that mapping between different
vendors' configuration is not needlessly complicated. Therefore this vendors' configuration is not needlessly complicated. Therefore,
model declares a number of features representing capabilities that this model declares a number of features representing capabilities
not all deployed devices support. that not all deployed devices support.
The extensive use of feature declarations should also substantially The extensive use of feature declarations should also substantially
simplify the capability negotiation process for a vendor's IGMP and simplify the capability negotiation process for a vendor's IGMP and
MLD implementations. MLD implementations.
On the other hand, operational state parameters are not so widely On the other hand, operational state parameters are not so widely
designated as features, as there are many cases where the defaulting designated as features, as there are many cases where the defaulting
of an operational state parameter would not cause any harm to the of an operational state parameter would not cause any harm to the
system, and it is much more likely that an implementation without system, and it is much more likely that an implementation without
native support for a piece of operational state would be able to native support for a piece of operational state would be able to
derive a suitable value for a state variable that is not natively derive a suitable value for a state variable that is not natively
supported. supported.
2.3. Position of Address Family in Hierarchy 2.3. Position of Address Family in Hierarchy
The protocol IGMP only supports IPv4, while the protocol MLD only The protocol IGMP only supports IPv4, while the protocol MLD only
supports IPv6. The data model defined in this document can be used supports IPv6. The data model defined in this document can be used
for both IPv4 and IPv6 address families. for both IPv4 and IPv6 address families.
This document defines IGMP and MLD as separate schema branches in This document defines IGMP and MLD as separate schema branches in the
the structure. The benefits are: structure. The benefits are:
o The model can support IGMP (IPv4), MLD (IPv6), or both * The model can support IGMP (IPv4), MLD (IPv6), or both optionally
optionally and independently. Such flexibility cannot be and independently. Such flexibility cannot be achieved cleanly
achieved cleanly with a combined branch. with a combined branch.
o The structure is consistent with other YANG models such as RFC * The structure is consistent with other YANG data models such as
8344, which uses separate branches for IPv4 and IPv6. RFC 8344, which uses separate branches for IPv4 and IPv6.
o The separate branches for IGMP and MLD can accommodate their * The separate branches for IGMP and MLD can accommodate their
differences better and cleaner. The two branches can better differences better and cleaner. The two branches can better
support different features and node types. support different features and node types.
3. Module Structure 3. Module Structure
This model augments the core routing data model specified in This model augments the core routing data model specified in
[RFC8349]. [RFC8349].
+--rw routing +--rw routing
+--rw router-id? +--rw router-id?
+--rw control-plane-protocols +--rw control-plane-protocols
| +--rw control-plane-protocol* [type name] | +--rw control-plane-protocol* [type name]
| +--rw type | +--rw type
| +--rw name | +--rw name
| +--rw igmp <= Augmented by this Model | +--rw igmp <= Augmented by this Model
... ...
| +--rw mld <= Augmented by this Model | +--rw mld <= Augmented by this Model
... ...
The "igmp" container instantiates an IGMP protocol of version The "igmp" container instantiates an IGMP protocol of version IGMPv1,
IGMPv1, IGMPv2, or IGMPv3. The "mld" container instantiates an MLD IGMPv2, or IGMPv3. The "mld" container instantiates an MLD protocol
protocol of version MLDv1 or MLDv2. of version MLDv1 or MLDv2.
The YANG data model defined in this document conforms to the Network The YANG data model defined in this document conforms to the Network
Management Datastore Architecture (NMDA) [RFC8342]. The operational Management Datastore Architecture (NMDA) [RFC8342]. The operational
state data is combined with the associated configuration data in the state data is combined with the associated configuration data in the
same hierarchy [RFC8407]. same hierarchy [RFC8407].
A configuration data node is marked as mandatory only when its value A configuration data node is marked as mandatory only when its value
must be provided by the user. Where nodes are not essential to must be provided by the user. Where nodes are not essential to
protocol operation, they are marked as optional. Some other nodes protocol operation, they are marked as optional. Some other nodes
are essential but have a default specified, so that they are also are essential but have a default specified, so that they are also
optional and need not be configured explicitly. optional and need not be configured explicitly.
3.1. IGMP Configuration and Operational State 3.1. IGMP Configuration and Operational State
The IGMP data is modeled as a schema subtree augmenting the The IGMP data is modeled as a schema subtree augmenting the "control-
"control-plane-protocol" data node under "/rt:routing/rt:control- plane-protocol" data node under "/rt:routing/rt:control-plane-
plane-protocols" in the module ietf-routing, following the protocols" in the module ietf-routing, following the convention
convention described in [RFC8349]. The augmentation to the module described in [RFC8349]. The augmentation to the module ietf-routing
ietf-routing allows this model to support multiple instances of allows this model to support multiple instances of IGMP, but a
IGMP, but a restriction MAY be added depending on the implementation restriction MAY be added depending on the implementation and the
and the device. The identity "igmp" is derived from the "rt:control- device. The identity "igmp" is derived from the "rt:control-plane-
plane-protocol" base identity and indicates that a control-plane- protocol" base identity and indicates that a control-plane-protocol
protocol instance is IGMP. instance is IGMP.
The IGMP subtree is a three-level hierarchy structure as listed The IGMP subtree is a three-level hierarchy structure as listed
below: below:
Global level: Including IGMP configuration and operational state Global level: Including IGMP configuration and operational state
attributes for the entire IGMP protocol instance in this router. attributes for the entire IGMP protocol instance in this router.
Interface-global level: Including configuration data nodes that Interface-global level: Including configuration data nodes that are
are applicable to all the interfaces whose corresponding nodes are applicable to all the interfaces whose corresponding nodes are not
not defined or not configured at the interface level. For such a defined or not configured at the interface level. For such a node
node at the interface level, the system uses the same value of the at the interface level, the system uses the same value of the
corresponding node at the interface-global level. corresponding node at the interface-global level.
Interface level: Including IGMP configuration and operational Interface level: Including IGMP configuration and operational state
state attributes specific to the given interface. For a attributes specific to the given interface. For a configuration
configuration node at the interface level, there may exist a node at the interface level, there may exist a corresponding
corresponding configuration node with the same name at the configuration node with the same name at the interface-global
interface-global level. The value configured on a node at the level. The value configured on a node at the interface level
interface level overrides the value configured on the corresponding overrides the value configured on the corresponding node at the
node at the interface-global level. interface-global level.
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol: /rt:control-plane-protocol:
+--rw igmp {feature-igmp}? +--rw igmp {feature-igmp}?
+--rw global +--rw global
| +--rw enable? boolean {global-admin-enable}? | +--rw enabled? boolean {global-admin-enable}?
| +--rw max-entries? uint32 {global-max-entries}? | +--rw max-entries? uint32 {global-max-entries}?
| +--rw max-groups? uint32 {global-max-groups}? | +--rw max-groups? uint32 {global-max-groups}?
| +--ro entries-count? uint32 | +--ro entries-count? uint32
| +--ro groups-count? uint32 | +--ro groups-count? uint32
| +--ro statistics | +--ro statistics
| +--ro discontinuity-time? yang:date-and-time | +--ro discontinuity-time? yang:date-and-time
| +--ro error | +--ro error
| | +--ro total? yang:counter64 | | +--ro total? yang:counter64
| | +--ro query? yang:counter64 | | +--ro query? yang:counter64
| | +--ro report? yang:counter64 | | +--ro report? yang:counter64
skipping to change at page 9, line 19 skipping to change at line 399
| {intf-max-groups}? | {intf-max-groups}?
+--rw interface* [interface-name] +--rw interface* [interface-name]
+--rw interface-name if:interface-ref +--rw interface-name if:interface-ref
+--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
| {intf-require-router-alert}? | {intf-require-router-alert}?
+--rw robustness-variable? uint8 +--rw robustness-variable? uint8
+--rw version? uint8 +--rw version? uint8
+--rw enable? boolean +--rw enabled? boolean
| {intf-admin-enable}? | {intf-admin-enable}?
+--rw group-policy? +--rw group-policy?
| -> /acl:acls/acl/name | -> /acl:acls/acl/name
+--rw immediate-leave? empty +--rw immediate-leave? empty
| {intf-immediate-leave}? | {intf-immediate-leave}?
+--rw max-groups? uint32 +--rw max-groups? uint32
| {intf-max-groups}? | {intf-max-groups}?
+--rw max-group-sources? uint32 +--rw max-group-sources? uint32
| {intf-max-group-sources}? | {intf-max-group-sources}?
+--rw source-policy? +--rw source-policy?
| -> /acl:acls/acl/name {intf-source-policy}? | -> /acl:acls/acl/name {intf-source-policy}?
+--rw verify-source-subnet? empty +--rw verify-source-subnet? empty
| {intf-verify-source-subnet}? | {intf-verify-source-subnet}?
+--rw explicit-tracking? empty +--rw explicit-tracking? empty
| {intf-explicit-tracking}? | {intf-explicit-tracking}?
+--rw exclude-lite? empty +--rw lite-exclude-filter? empty
| {intf-exclude-lite}? | {intf-lite-exclude-filter}?
+--rw join-group* +--rw join-group*
| rt-types:ipv4-multicast-group-address | rt-types:ipv4-multicast-group-address
| {intf-join-group}? | {intf-join-group}?
+--rw ssm-map* +--rw ssm-map*
| | [ssm-map-source-addr ssm-map-group-policy] | [ssm-map-source-addr ssm-map-group-policy]
| | {intf-ssm-map}? | {intf-ssm-map}?
| +--rw ssm-map-source-addr ssm-map-ipv4-addr-type | +--rw ssm-map-source-addr ssm-map-ipv4-addr-type
| +--rw ssm-map-group-policy string | +--rw ssm-map-group-policy string
+--rw static-group* [group-addr source-addr] +--rw static-group* [group-addr source-addr]
| | {intf-static-group}? | {intf-static-group}?
| +--rw group-addr | +--rw group-addr
| | rt-types:ipv4-multicast-group-address | | rt-types:ipv4-multicast-group-address
| +--rw source-addr | +--rw source-addr
| rt-types:ipv4-multicast-source-address | rt-types:ipv4-multicast-source-address
+--ro oper-status enumeration +--ro oper-status enumeration
+--ro querier inet:ipv4-address +--ro querier inet:ipv4-address
+--ro joined-group* +--ro joined-group*
| rt-types:ipv4-multicast-group-address | rt-types:ipv4-multicast-group-address
| {intf-join-group}? | {intf-join-group}?
+--ro group* [group-address] +--ro group* [group-address]
skipping to change at page 10, line 22 skipping to change at line 451
+--ro up-time uint32 +--ro up-time uint32
+--ro last-reporter? inet:ipv4-address +--ro last-reporter? inet:ipv4-address
+--ro source* [source-address] +--ro source* [source-address]
+--ro source-address inet:ipv4-address +--ro source-address inet:ipv4-address
+--ro expire uint32 +--ro expire uint32
+--ro up-time uint32 +--ro up-time uint32
+--ro host-count? uint32 +--ro host-count? uint32
| {intf-explicit-tracking}? | {intf-explicit-tracking}?
+--ro last-reporter? inet:ipv4-address +--ro last-reporter? inet:ipv4-address
+--ro host* [host-address] +--ro host* [host-address]
| {intf-explicit-tracking}? {intf-explicit-tracking}?
+--ro host-address inet:ipv4-address +--ro host-address inet:ipv4-address
+--ro host-filter-mode enumeration +--ro host-filter-mode enumeration
3.2. MLD Configuration and Operational State 3.2. MLD Configuration and Operational State
The MLD data is modeled as a schema subtree augmenting the "control- The MLD data is modeled as a schema subtree augmenting the "control-
plane-protocol" data node under "/rt:routing/rt:control-plane- plane-protocol" data node under "/rt:routing/rt:control-plane-
protocols" in the module ietf-routing, following the convention protocols" in the module ietf-routing, following the convention
described in [RFC8349]. The augmentation to the module ietf-routing described in [RFC8349]. The augmentation to the module ietf-routing
allows this model to support multiple instances of MLD, but a allows this model to support multiple instances of MLD, but a
restriction MAY be added depending on the implementation and the restriction MAY be added depending on the implementation and the
device. The identity "mld" is derived from the "rt:control-plane- device. The identity "mld" is derived from the "rt:control-plane-
protocol" base identity and indicates that a control-plane-protocol protocol" base identity and indicates that a control-plane-protocol
instance is MLD. instance is MLD.
The MLD subtree is a three-level hierarchy structure as listed The MLD subtree is a three-level hierarchy structure as listed below:
below:
Global level: Including MLD configuration and operational state Global level: Including MLD configuration and operational state
attributes for the entire MLD protocol instance in this router. attributes for the entire MLD protocol instance in this router.
Interface-global level: Including configuration data nodes that Interface-global level: Including configuration data nodes that are
are applicable to all the interfaces whose corresponding nodes are applicable to all the interfaces whose corresponding nodes are not
not defined or not configured at the interface level. For such a defined or not configured at the interface level. For such a node
node at the interface level, the system uses the same value of the at the interface level, the system uses the same value of the
corresponding node at the interface-global level. corresponding node at the interface-global level.
Interface level: Including MLD configuration and operational Interface level: Including MLD configuration and operational state
state attributes specific to the given interface. For a attributes specific to the given interface. For a configuration
configuration node at the interface level, there may exist a node at the interface level, there may exist a corresponding
corresponding configuration node with the same name at the configuration node with the same name at the interface-global
interface-global level. The value configured on a node at the level. The value configured on a node at the interface level
interface level overrides the value configured on the corresponding overrides the value configured on the corresponding node at the
node at the interface-global level. interface-global level.
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol: /rt:control-plane-protocol:
+--rw mld {feature-mld}? +--rw mld {feature-mld}?
+--rw global +--rw global
| +--rw enable? boolean {global-admin-enable}? | +--rw enabled? boolean {global-admin-enable}?
| +--rw max-entries? uint32 {global-max-entries}? | +--rw max-entries? uint32 {global-max-entries}?
| +--rw max-groups? uint32 {global-max-groups}? | +--rw max-groups? uint32 {global-max-groups}?
| +--ro entries-count? uint32 | +--ro entries-count? uint32
| +--ro groups-count? uint32 | +--ro groups-count? uint32
| +--ro statistics | +--ro statistics
| +--ro discontinuity-time? yang:date-and-time | +--ro discontinuity-time? yang:date-and-time
| +--ro error | +--ro error
| | +--ro total? yang:counter64 | | +--ro total? yang:counter64
| | +--ro query? yang:counter64 | | +--ro query? yang:counter64
| | +--ro report? yang:counter64 | | +--ro report? yang:counter64
skipping to change at page 12, line 7 skipping to change at line 533
| {intf-max-groups}? | {intf-max-groups}?
+--rw interface* [interface-name] +--rw interface* [interface-name]
+--rw interface-name if:interface-ref +--rw interface-name if:interface-ref
+--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
| {intf-require-router-alert}? | {intf-require-router-alert}?
+--rw robustness-variable? uint8 +--rw robustness-variable? uint8
+--rw version? uint8 +--rw version? uint8
+--rw enable? boolean +--rw enabled? boolean
| {intf-admin-enable}? | {intf-admin-enable}?
+--rw group-policy? +--rw group-policy?
| -> /acl:acls/acl/name | -> /acl:acls/acl/name
+--rw immediate-leave? empty +--rw immediate-leave? empty
| {intf-immediate-leave}? | {intf-immediate-leave}?
+--rw max-groups? uint32 +--rw max-groups? uint32
| {intf-max-groups}? | {intf-max-groups}?
+--rw max-group-sources? uint32 +--rw max-group-sources? uint32
| {intf-max-group-sources}? | {intf-max-group-sources}?
+--rw source-policy? +--rw source-policy?
| -> /acl:acls/acl/name {intf-source-policy}? | -> /acl:acls/acl/name {intf-source-policy}?
+--rw verify-source-subnet? empty +--rw verify-source-subnet? empty
| {intf-verify-source-subnet}? | {intf-verify-source-subnet}?
+--rw explicit-tracking? empty +--rw explicit-tracking? empty
| {intf-explicit-tracking}? | {intf-explicit-tracking}?
+--rw exclude-lite? empty +--rw lite-exclude-filter? empty
| {intf-exclude-lite}? | {intf-lite-exclude-filter}?
+--rw join-group* +--rw join-group*
| rt-types:ipv6-multicast-group-address | rt-types:ipv6-multicast-group-address
| {intf-join-group}? | {intf-join-group}?
+--rw ssm-map* +--rw ssm-map*
| | [ssm-map-source-addr ssm-map-group-policy] | [ssm-map-source-addr ssm-map-group-policy]
| | {intf-ssm-map}? | {intf-ssm-map}?
| +--rw ssm-map-source-addr ssm-map-ipv6-addr-type | +--rw ssm-map-source-addr ssm-map-ipv6-addr-type
| +--rw ssm-map-group-policy string | +--rw ssm-map-group-policy string
+--rw static-group* [group-addr source-addr] +--rw static-group* [group-addr source-addr]
| | {intf-static-group}? | {intf-static-group}?
| +--rw group-addr | +--rw group-addr
| | rt-types:ipv6-multicast-group-address | | rt-types:ipv6-multicast-group-address
| +--rw source-addr | +--rw source-addr
| rt-types:ipv6-multicast-source-address | rt-types:ipv6-multicast-source-address
+--ro oper-status enumeration +--ro oper-status enumeration
+--ro querier inet:ipv6-address +--ro querier inet:ipv6-address
+--ro joined-group* +--ro joined-group*
| rt-types:ipv6-multicast-group-address | rt-types:ipv6-multicast-group-address
| {intf-join-group}? | {intf-join-group}?
+--ro group* [group-address] +--ro group* [group-address]
skipping to change at page 13, line 10 skipping to change at line 585
+--ro up-time uint32 +--ro up-time uint32
+--ro last-reporter? inet:ipv6-address +--ro last-reporter? inet:ipv6-address
+--ro source* [source-address] +--ro source* [source-address]
+--ro source-address inet:ipv6-address +--ro source-address inet:ipv6-address
+--ro expire uint32 +--ro expire uint32
+--ro up-time uint32 +--ro up-time uint32
+--ro host-count? uint32 +--ro host-count? uint32
| {intf-explicit-tracking}? | {intf-explicit-tracking}?
+--ro last-reporter? inet:ipv6-address +--ro last-reporter? inet:ipv6-address
+--ro host* [host-address] +--ro host* [host-address]
| {intf-explicit-tracking}? {intf-explicit-tracking}?
+--ro host-address inet:ipv6-address +--ro host-address inet:ipv6-address
+--ro host-filter-mode enumeration +--ro host-filter-mode enumeration
3.3. IGMP and MLD Actions 3.3. IGMP and MLD Actions
IGMP and MLD each have one action which clears the group membership IGMP and MLD each have one action that clears the group membership
cache entries for that protocol. cache entries for that protocol.
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol: /rt:control-plane-protocol:
+--rw igmp {feature-igmp}? +--rw igmp {feature-igmp}?
+---x clear-groups {action-clear-groups}? +---x clear-groups {action-clear-groups}?
+---w input +---w input
+---w (interface) +---w (interface)
| +--:(name) | +--:(name)
| | +---w interface-name? leafref | | +---w interface-name? leafref
skipping to change at page 13, line 47 skipping to change at line 622
+---w input +---w input
+---w (interface) +---w (interface)
| +--:(name) | +--:(name)
| | +---w interface-name? leafref | | +---w interface-name? leafref
| +--:(all) | +--:(all)
| +---w all-interfaces? empty | +---w all-interfaces? empty
+---w group-address? union +---w group-address? union
+---w source-address? +---w source-address?
rt-types:ipv6-multicast-source-address rt-types:ipv6-multicast-source-address
4. IGMP and MLD YANG Module 4. IGMP and MLD YANG Module
This module references [RFC1112], [RFC2236], [RFC2710], [RFC3376], This module references [RFC1112], [RFC2236], [RFC2710], [RFC3376],
[RFC3810], [RFC5790], [RFC6636], [RFC6991], [RFC8294], [RFC8343], [RFC3810], [RFC5790], [RFC6636], [RFC6991], [RFC8294], [RFC8343],
[RFC8344], [RFC8349], and [RFC8519]. [RFC8344], [RFC8349], and [RFC8519].
<CODE BEGINS> file "ietf-igmp-mld@2019-06-12.yang" <CODE BEGINS> file "ietf-igmp-mld@2019-11-01.yang"
module ietf-igmp-mld { module ietf-igmp-mld {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld"; namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld";
prefix igmp-mld; prefix igmp-mld;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix inet;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix yang;
reference "RFC 6991: Common YANG Data Types"; reference
"RFC 6991: Common YANG Data Types";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix rt-types;
reference reference
"RFC 8294: Common YANG Data Types for the Routing Area"; "RFC 8294: Common YANG Data Types for the Routing Area";
} }
import ietf-access-control-list { import ietf-access-control-list {
prefix "acl"; prefix acl;
reference reference
"RFC 8519: YANG Data Model for Network Access Control Lists "RFC 8519: YANG Data Model for Network Access Control Lists
(ACLs)"; (ACLs)";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix rt;
reference reference
"RFC 8349: A YANG Data Model for Routing Management (NMDA "RFC 8349: A YANG Data Model for Routing Management (NMDA
Version)"; Version)";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix if;
reference "RFC 8343: A YANG Data Model for Interface Management"; reference
"RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-ip { import ietf-ip {
prefix ip; prefix ip;
reference "RFC 8344: A YANG Data Model for IP Management"; reference
"RFC 8344: A YANG Data Model for IP Management";
} }
organization organization
"IETF PIM Working Group"; "IETF PIM Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/pim/> "WG Web: <http://datatracker.ietf.org/wg/pim/>
WG List: <mailto:pim@ietf.org> WG List: <mailto:pim@ietf.org>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Feng Guo Editor: Feng Guo
<mailto:guofeng@huawei.com> <mailto:guofeng@huawei.com>
Editor: Mahesh Sivakumar Editor: Mahesh Sivakumar
<mailto:sivakumar.mahesh@gmail.com> <mailto:sivakumar.mahesh@gmail.com>
skipping to change at page 15, line 23 skipping to change at line 692
<mailto:guofeng@huawei.com> <mailto:guofeng@huawei.com>
Editor: Mahesh Sivakumar Editor: Mahesh Sivakumar
<mailto:sivakumar.mahesh@gmail.com> <mailto:sivakumar.mahesh@gmail.com>
Editor: Pete McAllister Editor: Pete McAllister
<mailto:pete.mcallister@metaswitch.com> <mailto:pete.mcallister@metaswitch.com>
Editor: Anish Peter Editor: Anish Peter
<mailto:anish.ietf@gmail.com>"; <mailto:anish.ietf@gmail.com>";
description description
"The module defines the configuration and operational state for "The module defines the configuration and operational state for
the Internet Group Management Protocol (IGMP) and Multicast the Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) protocols. Listener Discovery (MLD) protocols.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 8652; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove revision 2019-11-01 {
// this note
revision 2019-06-12 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for IGMP and MLD"; "RFC 8652: A YANG Data Model for the Internet Group Management
Protocol (IGMP) and Multicast Listener Discovery (MLD)";
} }
/* /*
* Features * Features
*/ */
feature feature-igmp { feature feature-igmp {
description description
"Support IGMP protocol for IPv4 group membership record."; "Support IGMP protocol for IPv4 group membership record.";
} }
skipping to change at page 17, line 46 skipping to change at line 820
"Support configuration of interface explicit-tracking hosts."; "Support configuration of interface explicit-tracking hosts.";
} }
feature intf-lite-exclude-filter { feature intf-lite-exclude-filter {
description description
"Support configuration of interface lite-exclude-filter."; "Support configuration of interface lite-exclude-filter.";
} }
feature per-interface-config { feature per-interface-config {
description description
"Support per interface configuration."; "Support per-interface configuration.";
} }
feature action-clear-groups { feature action-clear-groups {
description description
"Support actions to clear groups."; "Support actions to clear groups.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef ssm-map-ipv4-addr-type { typedef ssm-map-ipv4-addr-type {
type union { type union {
type enumeration { type enumeration {
enum 'policy' { enum policy {
description description
"Source address is specified in SSM map policy."; "Source address is specified in SSM map policy.";
} }
} }
type inet:ipv4-address; type inet:ipv4-address;
} }
description description
"Multicast source IP address type for SSM map."; "Multicast source IP address type for SSM map.";
} // source-ipv4-addr-type }
// source-ipv4-addr-type
typedef ssm-map-ipv6-addr-type { typedef ssm-map-ipv6-addr-type {
type union { type union {
type enumeration { type enumeration {
enum 'policy' { enum policy {
description description
"Source address is specified in SSM map policy."; "Source address is specified in SSM map policy.";
} }
} }
type inet:ipv6-address; type inet:ipv6-address;
} }
description description
"Multicast source IP address type for SSM map."; "Multicast source IP address type for SSM map.";
} // source-ipv6-addr-type }
// source-ipv6-addr-type
/* /*
* Identities * Identities
*/ */
identity igmp { identity igmp {
base "rt:control-plane-protocol"; if-feature "feature-igmp";
description "IGMP protocol."; base rt:control-plane-protocol;
description
"IGMP protocol.";
reference reference
"RFC 3376: Internet Group Management Protocol, Version 3."; "RFC 3376: Internet Group Management Protocol, Version 3";
} }
identity mld { identity mld {
base "rt:control-plane-protocol"; if-feature "feature-mld";
description "MLD protocol."; base rt:control-plane-protocol;
description
"MLD protocol.";
reference reference
"RFC 3810: Multicast Listener Discovery Version 2 (MLDv2) for "RFC 3810: Multicast Listener Discovery Version 2 (MLDv2) for
IPv6."; IPv6";
} }
/* /*
* Groupings * Groupings
*/ */
grouping global-config-attributes { grouping global-config-attributes {
description description
"This grouping is used in either IGMP schema or MLD schema. "This grouping is used in either IGMP schema or MLD schema.
When used in IGMP schema, this grouping contains the global When used in IGMP schema, this grouping contains the global
configuration for IGMP; configuration for IGMP;
when used in MLD schema, this grouping contains the global when used in MLD schema, this grouping contains the global
configuration for MLD."; configuration for MLD.";
leaf enabled {
leaf enable { if-feature "global-admin-enable";
if-feature global-admin-enable;
type boolean; type boolean;
default true; default "true";
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
whether IGMP is enabled ('true') or disabled ('false') whether IGMP is enabled ('true') or disabled ('false')
in the routing instance. in the routing instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
whether MLD is enabled ('true') or disabled ('false') whether MLD is enabled ('true') or disabled ('false')
in the routing instance."; in the routing instance.";
} }
leaf max-entries { leaf max-entries {
if-feature global-max-entries; if-feature "global-max-entries";
type uint32; type uint32;
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
the maximum number of entries in the IGMP instance. the maximum number of entries in the IGMP instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the maximum number of entries in the MLD instance. the maximum number of entries in the MLD instance.
If this leaf is not specified, the number of entries is not If this leaf is not specified, the number of entries is not
limited."; limited.";
} }
leaf max-groups { leaf max-groups {
if-feature global-max-groups; if-feature "global-max-groups";
type uint32; type uint32;
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
the maximum number of groups in the IGMP instance. the maximum number of groups in the IGMP instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the maximum number of groups in the MLD instance. the maximum number of groups in the MLD instance.
If this leaf is not specified, the number of groups is not If this leaf is not specified, the number of groups is not
limited."; limited.";
} }
} // global-config-attributes }
// global-config-attributes
grouping global-state-attributes { grouping global-state-attributes {
description description
"This grouping is used in either IGMP schema or MLD schema. "This grouping is used in either IGMP schema or MLD schema.
When used in IGMP schema, this grouping contains the global When used in IGMP schema, this grouping contains the global
IGMP state attributes; IGMP state attributes;
when used in MLD schema, this grouping contains the global when used in MLD schema, this grouping contains the global
MLD state attributes;"; MLD state attributes.";
leaf entries-count { leaf entries-count {
type uint32; type uint32;
config false; config false;
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
the number of entries in the IGMP instance. the number of entries in the IGMP instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the number of entries in the MLD instance."; the number of entries in the MLD instance.";
} }
leaf groups-count { leaf groups-count {
skipping to change at page 20, line 30 skipping to change at line 958
} }
leaf groups-count { leaf groups-count {
type uint32; type uint32;
config false; config false;
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
the number of existing groups in the IGMP instance. the number of existing groups in the IGMP instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the number of existing groups in the MLD instance."; the number of existing groups in the MLD instance.";
} }
container statistics { container statistics {
config false; config false;
description description
"When this grouping is used for IGMP, this container contains "When this grouping is used for IGMP, this container contains
the statistics for the IGMP instance. the statistics for the IGMP instance.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the statistics for the MLD instance."; the statistics for the MLD instance.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one "The time on the most recent occasion at which any one
or more of the statistic counters suffered a or more of the statistic counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local since the last re-initialization of the local
management subsystem, then this node contains the time management subsystem, then this node contains the time
the local management subsystem re-initialized itself."; the local management subsystem re-initialized itself.";
} }
container error { container error {
description "Statistics of errors."; description
"Statistics of errors.";
uses global-statistics-error; uses global-statistics-error;
} }
container received { container received {
description "Statistics of received messages."; description
"Statistics of received messages.";
uses global-statistics-sent-received; uses global-statistics-sent-received;
} }
container sent { container sent {
description "Statistics of sent messages."; description
"Statistics of sent messages.";
uses global-statistics-sent-received; uses global-statistics-sent-received;
} }
} // statistics }
} // global-state-attributes // statistics
}
// global-state-attributes
grouping global-statistics-error { grouping global-statistics-error {
description description
"A grouping defining statistics attributes for errors."; "A grouping defining statistics attributes for errors.";
uses global-statistics-sent-received; uses global-statistics-sent-received;
leaf checksum { leaf checksum {
type yang:counter64; type yang:counter64;
description description
"The number of checksum errors."; "The number of checksum errors.";
} }
leaf too-short { leaf too-short {
type yang:counter64; type yang:counter64;
description description
"The number of messages that are too short."; "The number of messages that are too short.";
skipping to change at page 21, line 30 skipping to change at line 1009
leaf checksum { leaf checksum {
type yang:counter64; type yang:counter64;
description description
"The number of checksum errors."; "The number of checksum errors.";
} }
leaf too-short { leaf too-short {
type yang:counter64; type yang:counter64;
description description
"The number of messages that are too short."; "The number of messages that are too short.";
} }
} // global-statistics-error }
// global-statistics-error
grouping global-statistics-sent-received { grouping global-statistics-sent-received {
description description
"A grouping defining statistics attributes."; "A grouping defining statistics attributes.";
leaf total { leaf total {
type yang:counter64; type yang:counter64;
description description
"The number of total messages."; "The number of total messages.";
} }
leaf query { leaf query {
type yang:counter64; type yang:counter64;
description description
"The number of query messages."; "The number of query messages.";
} }
skipping to change at page 22, line 7 skipping to change at line 1035
leaf report { leaf report {
type yang:counter64; type yang:counter64;
description description
"The number of report messages."; "The number of report messages.";
} }
leaf leave { leaf leave {
type yang:counter64; type yang:counter64;
description description
"The number of leave messages."; "The number of leave messages.";
} }
} // global-statistics-sent-received }
// global-statistics-sent-received
grouping interface-global-config-attributes { grouping interface-global-config-attributes {
description description
"Configuration attributes applied to the interface-global level "Configuration attributes applied to the interface-global level
whose per interface attributes are not configured."; whose per-interface attributes are not configured.";
leaf max-groups-per-interface { leaf max-groups-per-interface {
if-feature intf-max-groups; if-feature "intf-max-groups";
type uint32; type uint32;
description description
"The maximum number of groups associated with each interface. "The maximum number of groups associated with each interface.
If this leaf is not specified, the number of groups is not If this leaf is not specified, the number of groups is not
limited."; limited.";
} }
} //interface-global-config-attributes }
// interface-global-config-attributes
grouping interface-common-config-attributes { grouping interface-common-config-attributes {
description description
"Configuration attributes applied to both the interface-global "Configuration attributes applied to both the interface-global
level and interface level."; level and interface level.";
leaf last-member-query-interval { leaf last-member-query-interval {
type uint16 { type uint16 {
range "1..1023"; range "1..1023";
} }
units seconds; units "seconds";
description description
"When used in IGMP schema, this leaf indicates the Last "When used in IGMP schema, this leaf indicates the Last
Member Query Interval, which may be tuned to modify the Member Query Interval, which may be tuned to modify the
leave latency of the network; leave latency of the network;
when used in MLD schema, this leaf indicates the Last when used in MLD schema, this leaf indicates the Last
Listener Query Interval, which may be tuned to modify the Listener Query Interval, which may be tuned to modify the
leave latency of the network. leave latency of the network.
This leaf is not applicable for version 1 of the IGMP. For This leaf is not applicable for version 1 of the IGMP. For
version 2 and version 3 of the IGMP, and for all versions of version 2 and version 3 of the IGMP, and for all versions of
the MLD, the default value of this leaf is 1. the MLD, the default value of this leaf is 1.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference reference
"RFC 2236. Sec. 8.8. RFC 3376. Sec. 8.8. "Section 8.8 of RFC 2236: Internet Group Management Protocol,
RFC 2710. Sec. 7.8. RFC 3810. Sec. 9.8."; Version 2.
Section 8.8 of RFC 3376: Internet Group Management Protocol,
Version 3.
Section 7.8 of RFC 2710: Multicast Listener Discovery (MLD)
for IPv6.
Section 9.8 of RFC 3810: Multicast Listener Discovery
Version 2 (MLDv2) for IPv6.";
} }
leaf query-interval { leaf query-interval {
type uint16 { type uint16 {
range "1..31744"; range "1..31744";
} }
units seconds; units "seconds";
description description
"The Query Interval is the interval between General Queries "The Query Interval is the interval between General Queries
sent by the Querier. In RFC 3376, the Querier's Query sent by the Querier. In RFC 3376, the Querier's Query
Interval(QQI) is represented from the Querier's Query Interval (QQI) is represented from the Querier's Query
Interval Code in query message as follows: Interval Code (QQIC) in query message as follows:
If QQIC < 128, QQI = QQIC. If QQIC < 128, QQI = QQIC.
If QQIC >= 128, QQIC represents a floating-point value as If QQIC >= 128, QQIC represents a floating-point value as
follows: follows:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|1| exp | mant | |1| exp | mant |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
QQI = (mant | 0x10) << (exp + 3). QQI = (mant | 0x10) << (exp + 3).
The maximum value of QQI is 31744. The maximum value of QQI is 31744.
The default value is 125. The default value is 125.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference "RFC 3376. Sec. 4.1.7, 8.2, 8.14.2."; reference
"Sections 4.1.7, 8.2, and 8.14.2 of RFC 3376: Internet Group
Management Protocol, Version 3";
} }
leaf query-max-response-time { leaf query-max-response-time {
type uint16 { type uint16 {
range "1..1023"; range "1..1023";
} }
units seconds; units "seconds";
description description
"Query maximum response time specifies the maximum time "Query maximum response time specifies the maximum time
allowed before sending a responding report. allowed before sending a responding report.
The default value is 10. The default value is 10.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference "RFC 3376. Sec. 4.1.1, 8.3, 8.14.3."; reference
"Sections 4.1.1, 8.3, and 8.14.3 of RFC 3376: Internet Group
Management Protocol, Version 3";
} }
leaf require-router-alert { leaf require-router-alert {
if-feature intf-require-router-alert; if-feature "intf-require-router-alert";
type boolean; type boolean;
description description
"Protocol packets should contain router alert IP option. "Protocol packets should contain the router alert IP option.
When this leaf is not configured, the server uses the When this leaf is not configured, the server uses the
following rules to determine the operational value of this following rules to determine the operational value of this
leaf: leaf:
if this grouping is used in IGMP schema and the value of the if this grouping is used in IGMP schema and the value of the
leaf 'version' is 1, the value 'false' is operationally used leaf 'version' is 1, the value 'false' is operationally used
by the server; by the server;
if this grouping is used in IGMP schema and the value of the if this grouping is used in IGMP schema and the value of the
leaf 'version' is 2 or 3, the value 'true' is operationally leaf 'version' is 2 or 3, the value 'true' is operationally
used by the server; used by the server;
if this grouping is used in MLD schema, the value 'true' is if this grouping is used in MLD schema, the value 'true' is
operationally used by the server. operationally used by the server.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
} }
leaf robustness-variable { leaf robustness-variable {
type uint8 { type uint8 {
range "1..7"; range "1..7";
} }
description description
"Querier's Robustness Variable allows tuning for the "The Querier's Robustness Variable allows tuning for the
expected packet loss on a network. expected packet loss on a network.
The default value is 2. The default value is 2.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference "RFC 3376. Sec. 4.1.6, 8.1, 8.14.1."; reference
"Sections 4.1.6, 8.1, and 8.14.1 of RFC 3376: Internet Group
Management Protocol, Version 3";
} }
} // interface-common-config-attributes }
// interface-common-config-attributes
grouping interface-common-config-attributes-igmp { grouping interface-common-config-attributes-igmp {
description description
"Configuration attributes applied to both the interface-global "Configuration attributes applied to both the interface-global
level and interface level for IGMP."; level and interface level for IGMP.";
uses interface-common-config-attributes; uses interface-common-config-attributes;
leaf version { leaf version {
type uint8 { type uint8 {
range "1..3"; range "1..3";
} }
description description
"IGMP version. "IGMP version.
The default value is 2. The default value is 2.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
skipping to change at page 24, line 47 skipping to change at line 1185
uses interface-common-config-attributes; uses interface-common-config-attributes;
leaf version { leaf version {
type uint8 { type uint8 {
range "1..3"; range "1..3";
} }
description description
"IGMP version. "IGMP version.
The default value is 2. The default value is 2.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference "RFC 1112, RFC 2236, RFC 3376."; reference
"RFC 1112: Host Extensions for IP Multicasting,
RFC 2236: Internet Group Management Protocol, Version 2,
RFC 3376: Internet Group Management Protocol, Version 3.";
} }
} }
grouping interface-common-config-attributes-mld { grouping interface-common-config-attributes-mld {
description description
"Configuration attributes applied to both the interface-global "Configuration attributes applied to both the interface-global
level and interface level for MLD."; level and interface level for MLD.";
uses interface-common-config-attributes; uses interface-common-config-attributes;
leaf version { leaf version {
type uint8 { type uint8 {
range "1..2"; range "1..2";
} }
description description
"MLD version. "MLD version.
The default value is 2. The default value is 2.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
skipping to change at page 25, line 19 skipping to change at line 1208
uses interface-common-config-attributes; uses interface-common-config-attributes;
leaf version { leaf version {
type uint8 { type uint8 {
range "1..2"; range "1..2";
} }
description description
"MLD version. "MLD version.
The default value is 2. The default value is 2.
This leaf may be configured at the interface level or the This leaf may be configured at the interface level or the
interface-global level, with precedence given to the value interface-global level, with precedence given to the value
at the interface level. If the leaf is not configured at at the interface level. If the leaf is not configured at
either level, the default value is used."; either level, the default value is used.";
reference "RFC 2710, RFC 3810."; reference
"RFC 2710: Multicast Listener Discovery (MLD) for IPv6,
RFC 3810: Multicast Listener Discovery Version 2 (MLDv2)
for IPv6.";
} }
} }
grouping interfaces-config-attributes-igmp { grouping interfaces-config-attributes-igmp {
description description
"Configuration attributes applied to the interface-global "Configuration attributes applied to the interface-global
level for IGMP."; level for IGMP.";
uses interface-common-config-attributes-igmp; uses interface-common-config-attributes-igmp;
uses interface-global-config-attributes; uses interface-global-config-attributes;
} }
grouping interfaces-config-attributes-mld { grouping interfaces-config-attributes-mld {
description description
"Configuration attributes applied to the interface-global "Configuration attributes applied to the interface-global
level for MLD."; level for MLD.";
uses interface-common-config-attributes-mld; uses interface-common-config-attributes-mld;
uses interface-global-config-attributes; uses interface-global-config-attributes;
} }
grouping interface-level-config-attributes { grouping interface-level-config-attributes {
description description
"This grouping is used in either IGMP schema or MLD schema. "This grouping is used in either IGMP schema or MLD schema.
When used in IGMP schema, this grouping contains the IGMP When used in IGMP schema, this grouping contains the IGMP
configuration attributes that are defined at the interface configuration attributes that are defined at the interface
level but are not defined at the interface-global level; level but are not defined at the interface-global level;
skipping to change at page 26, line 4 skipping to change at line 1242
grouping interface-level-config-attributes { grouping interface-level-config-attributes {
description description
"This grouping is used in either IGMP schema or MLD schema. "This grouping is used in either IGMP schema or MLD schema.
When used in IGMP schema, this grouping contains the IGMP When used in IGMP schema, this grouping contains the IGMP
configuration attributes that are defined at the interface configuration attributes that are defined at the interface
level but are not defined at the interface-global level; level but are not defined at the interface-global level;
when used in MLD schema, this grouping contains the MLD when used in MLD schema, this grouping contains the MLD
configuration attributes that are defined at the interface configuration attributes that are defined at the interface
level but are not defined at the interface-global level."; level but are not defined at the interface-global level.";
leaf enabled {
leaf enable { if-feature "intf-admin-enable";
if-feature intf-admin-enable;
type boolean; type boolean;
default true; default "true";
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
whether IGMP is enabled ('true') or disabled ('false') whether IGMP is enabled ('true') or disabled ('false')
on the interface. on the interface.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
whether MLD is enabled ('true') or disabled ('false') whether MLD is enabled ('true') or disabled ('false')
on the interface."; on the interface.";
} }
leaf group-policy { leaf group-policy {
type leafref { type leafref {
path "/acl:acls/acl:acl/acl:name"; path "/acl:acls/acl:acl/acl:name";
} }
description description
"When this grouping is used for IGMP, this leaf specifies "When this grouping is used for IGMP, this leaf specifies
the name of the access policy used to filter the the name of the access policy used to filter the
IGMP membership. IGMP membership.
When this grouping is used for MLD, this leaf specifies When this grouping is used for MLD, this leaf specifies
the name of the access policy used to filter the the name of the access policy used to filter the
MLD membership. MLD membership.
The value space of this leaf is restricted to the existing The value space of this leaf is restricted to the existing
policy instances defined by the referenced schema RFC 8519. policy instances defined by the referenced schema in
RFC 8519.
As specified by RFC 8519, the length of the name is between As specified by RFC 8519, the length of the name is between
1 and 64; a device MAY further restrict the length of this 1 and 64; a device MAY further restrict the length of this
name; space and special characters are not allowed. name; space and special characters are not allowed.
If this leaf is not specified, no policy is applied, and If this leaf is not specified, no policy is applied, and
all packets received from this interface are accepted."; all packets received from this interface are accepted.";
reference reference
"RFC 8519: YANG Data Model for Network Access Control Lists "RFC 8519: YANG Data Model for Network Access Control Lists
(ACLs)"; (ACLs)";
} }
leaf immediate-leave { leaf immediate-leave {
if-feature intf-immediate-leave; if-feature "intf-immediate-leave";
type empty; type empty;
description description
"When this grouping is used for IGMP, the presence of this "When this grouping is used for IGMP, the presence of this
leaf requests IGMP to perform an immediate leave upon leaf requests IGMP to perform an immediate leave upon
receiving an IGMPv2 leave message. receiving an IGMPv2 leave message.
If the router is IGMP-enabled, it sends an IGMP last member If the router is IGMP-enabled, it sends an IGMP last member
query with a last member query response time. However, the query with a last member query response time. However, the
router does not wait for the response time before it prunes router does not wait for the response time before it prunes
the group. the group.
When this grouping is used for MLD, the presence of this When this grouping is used for MLD, the presence of this
leaf requests MLD to perform an immediate leave upon leaf requests MLD to perform an immediate leave upon
receiving an MLDv1 leave message. receiving an MLDv1 leave message.
If the router is MLD-enabled, it sends an MLD last member If the router is MLD-enabled, it sends an MLD last member
query with a last member query response time. However, the query with a last member query response time. However, the
router does not wait for the response time before it prunes router does not wait for the response time before it prunes
the group."; the group.";
} }
leaf max-groups { leaf max-groups {
if-feature intf-max-groups; if-feature "intf-max-groups";
type uint32; type uint32;
description description
"When this grouping is used for IGMP, this leaf indicates "When this grouping is used for IGMP, this leaf indicates
the maximum number of groups associated with the IGMP the maximum number of groups associated with the IGMP
interface. interface.
When this grouping is used for MLD, this leaf indicates When this grouping is used for MLD, this leaf indicates
the maximum number of groups associated with the MLD the maximum number of groups associated with the MLD
interface. interface.
If this leaf is not specified, the number of groups is not If this leaf is not specified, the number of groups is not
limited."; limited.";
} }
leaf max-group-sources { leaf max-group-sources {
if-feature intf-max-group-sources; if-feature "intf-max-group-sources";
type uint32; type uint32;
description description
"The maximum number of group sources. "The maximum number of group sources.
If this leaf is not specified, the number of group sources If this leaf is not specified, the number of group sources
is not limited."; is not limited.";
} }
leaf source-policy { leaf source-policy {
if-feature intf-source-policy; if-feature "intf-source-policy";
type leafref { type leafref {
path "/acl:acls/acl:acl/acl:name"; path "/acl:acls/acl:acl/acl:name";
} }
description description
"Name of the access policy used to filter sources. "Name of the access policy used to filter sources.
The value space of this leaf is restricted to the existing The value space of this leaf is restricted to the existing
policy instances defined by the referenced schema RFC 8519. policy instances defined by the referenced schema in
RFC 8519.
As specified by RFC 8519, the length of the name is between As specified by RFC 8519, the length of the name is between
1 and 64; a device MAY further restrict the length of this 1 and 64; a device MAY further restrict the length of this
name; space and special characters are not allowed. name; space and special characters are not allowed.
If this leaf is not specified, no policy is applied, and If this leaf is not specified, no policy is applied, and
all packets received from this interface are accepted."; all packets received from this interface are accepted.";
} }
leaf verify-source-subnet { leaf verify-source-subnet {
if-feature intf-verify-source-subnet; if-feature "intf-verify-source-subnet";
type empty; type empty;
description description
"If present, the interface accepts packets with matching "If present, the interface accepts packets with matching
source IP subnet only."; source IP subnet only.";
} }
leaf explicit-tracking { leaf explicit-tracking {
if-feature intf-explicit-tracking; if-feature "intf-explicit-tracking";
type empty; type empty;
description description
"When this grouping is used for IGMP, the presence of this "When this grouping is used for IGMP, the presence of this
leaf enables IGMP-based explicit membership tracking leaf enables an IGMP-based explicit membership tracking
function for multicast routers and IGMP proxy devices function for multicast routers and IGMP proxy devices
supporting IGMPv3. supporting IGMPv3.
When this grouping is used for MLD, the presence of this When this grouping is used for MLD, the presence of this
leaf enables MLD-based explicit membership tracking leaf enables an MLD-based explicit membership tracking
function for multicast routers and MLD proxy devices function for multicast routers and MLD proxy devices
supporting MLDv2. supporting MLDv2.
The explicit membership tracking function contributes to The explicit membership tracking function contributes to
saving network resources and shortening leave latency."; saving network resources and shortening leave latency.";
reference reference
"RFC 6636. Sec 3."; "Section 3 of RFC 6636: Tuning the Behavior of the Internet
Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) for Routers in Mobile and Wireless
Networks";
} }
leaf lite-exclude-filter { leaf lite-exclude-filter {
if-feature intf-lite-exclude-filter; if-feature "intf-lite-exclude-filter";
type empty; type empty;
description description
"When this grouping is used for IGMP, the presence of this "When this grouping is used for IGMP, the presence of this
leaf enables the support of the simplified EXCLUDE filter leaf enables the support of the simplified EXCLUDE filter
in the Lightweight IGMPv3 protocol, which simplifies the in the Lightweight IGMPv3 protocol, which simplifies the
standard versions of IGMPv3. standard versions of IGMPv3.
When this grouping is used for MLD, the presence of this When this grouping is used for MLD, the presence of this
leaf enables the support of the simplified EXCLUDE filter leaf enables the support of the simplified EXCLUDE filter
in the Lightweight MLDv2 protocol, which simplifies the in the Lightweight MLDv2 protocol, which simplifies the
standard versions of MLDv2."; standard versions of MLDv2.";
reference "RFC 5790"; reference
"RFC 5790: Lightweight Internet Group Management Protocol
Version 3 (IGMPv3) and Multicast Listener Discovery
Version 2 (MLDv2) Protocols";
} }
} // interface-level-config-attributes }
// interface-level-config-attributes
grouping interface-config-attributes-igmp { grouping interface-config-attributes-igmp {
description description
"Per interface configuration attributes for IGMP."; "Per-interface configuration attributes for IGMP.";
uses interface-common-config-attributes-igmp; uses interface-common-config-attributes-igmp;
uses interface-level-config-attributes; uses interface-level-config-attributes;
leaf-list join-group { leaf-list join-group {
if-feature intf-join-group; if-feature "intf-join-group";
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
description description
"The router joins this multicast group on the interface."; "The router joins this multicast group on the interface.";
} }
list ssm-map { list ssm-map {
if-feature intf-ssm-map; if-feature "intf-ssm-map";
key "ssm-map-source-addr ssm-map-group-policy"; key "ssm-map-source-addr ssm-map-group-policy";
description "The policy for (*,G) mapping to (S,G)."; description
"The policy for (*,G) mapping to (S,G).";
leaf ssm-map-source-addr { leaf ssm-map-source-addr {
type ssm-map-ipv4-addr-type; type ssm-map-ipv4-addr-type;
description description
"Multicast source IPv4 address."; "Multicast source IPv4 address.";
} }
leaf ssm-map-group-policy { leaf ssm-map-group-policy {
type string; type string;
description description
"Name of the policy used to define ssm-map rules. "Name of the policy used to define ssm-map rules.
A device can restrict the length A device can restrict the length
and value of this name, possibly space and special and value of this name, possibly space and special
characters are not allowed. "; characters are not allowed.";
} }
} }
list static-group { list static-group {
if-feature intf-static-group; if-feature "intf-static-group";
key "group-addr source-addr"; key "group-addr source-addr";
description description
"A static multicast route, (*,G) or (S,G). "A static multicast route, (*,G) or (S,G).
The version of IGMP must be 3 to support (S,G)."; The version of IGMP must be 3 to support (S,G).";
leaf group-addr { leaf group-addr {
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
description description
"Multicast group IPv4 address."; "Multicast group IPv4 address.";
} }
leaf source-addr { leaf source-addr {
type rt-types:ipv4-multicast-source-address; type rt-types:ipv4-multicast-source-address;
description description
"Multicast source IPv4 address."; "Multicast source IPv4 address.";
} }
skipping to change at page 29, line 35 skipping to change at line 1427
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
description description
"Multicast group IPv4 address."; "Multicast group IPv4 address.";
} }
leaf source-addr { leaf source-addr {
type rt-types:ipv4-multicast-source-address; type rt-types:ipv4-multicast-source-address;
description description
"Multicast source IPv4 address."; "Multicast source IPv4 address.";
} }
} }
} // interface-config-attributes-igmp }
// interface-config-attributes-igmp
grouping interface-config-attributes-mld { grouping interface-config-attributes-mld {
description description
"Per interface configuration attributes for MLD."; "Per-interface configuration attributes for MLD.";
uses interface-common-config-attributes-mld; uses interface-common-config-attributes-mld;
uses interface-level-config-attributes; uses interface-level-config-attributes;
leaf-list join-group { leaf-list join-group {
if-feature intf-join-group; if-feature "intf-join-group";
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
description description
"The router joins this multicast group on the interface."; "The router joins this multicast group on the interface.";
} }
list ssm-map { list ssm-map {
if-feature intf-ssm-map; if-feature "intf-ssm-map";
key "ssm-map-source-addr ssm-map-group-policy"; key "ssm-map-source-addr ssm-map-group-policy";
description "The policy for (*,G) mapping to (S,G)."; description
"The policy for (*,G) mapping to (S,G).";
leaf ssm-map-source-addr { leaf ssm-map-source-addr {
type ssm-map-ipv6-addr-type; type ssm-map-ipv6-addr-type;
description description
"Multicast source IPv6 address."; "Multicast source IPv6 address.";
} }
leaf ssm-map-group-policy { leaf ssm-map-group-policy {
type string; type string;
description description
"Name of the policy used to define ssm-map rules. "Name of the policy used to define ssm-map rules.
A device can restrict the length A device can restrict the length
and value of this name, possibly space and special and value of this name, possibly space and special
characters are not allowed."; characters are not allowed.";
} }
} }
list static-group { list static-group {
if-feature intf-static-group; if-feature "intf-static-group";
key "group-addr source-addr"; key "group-addr source-addr";
description description
"A static multicast route, (*,G) or (S,G). "A static multicast route, (*,G) or (S,G).
The version of MLD must be 2 to support (S,G)."; The version of MLD must be 2 to support (S,G).";
leaf group-addr { leaf group-addr {
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
description description
"Multicast group IPv6 address."; "Multicast group IPv6 address.";
} }
leaf source-addr { leaf source-addr {
type rt-types:ipv6-multicast-source-address; type rt-types:ipv6-multicast-source-address;
description description
"Multicast source IPv6 address."; "Multicast source IPv6 address.";
} }
skipping to change at page 30, line 36 skipping to change at line 1477
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
description description
"Multicast group IPv6 address."; "Multicast group IPv6 address.";
} }
leaf source-addr { leaf source-addr {
type rt-types:ipv6-multicast-source-address; type rt-types:ipv6-multicast-source-address;
description description
"Multicast source IPv6 address."; "Multicast source IPv6 address.";
} }
} }
} // interface-config-attributes-mld }
// interface-config-attributes-mld
grouping interface-state-attributes { grouping interface-state-attributes {
description description
"Per interface state attributes for both IGMP and MLD."; "Per-interface state attributes for both IGMP and MLD.";
leaf oper-status { leaf oper-status {
type enumeration { type enumeration {
enum up { enum up {
description description
"Ready to pass packets."; "Ready to pass packets.";
} }
enum down { enum down {
description description
"The interface does not pass any packets."; "The interface does not pass any packets.";
} }
skipping to change at page 31, line 4 skipping to change at line 1493
leaf oper-status { leaf oper-status {
type enumeration { type enumeration {
enum up { enum up {
description description
"Ready to pass packets."; "Ready to pass packets.";
} }
enum down { enum down {
description description
"The interface does not pass any packets."; "The interface does not pass any packets.";
} }
} }
config false; config false;
mandatory true; mandatory true;
description description
"Indicates whether the operational state of the interface "Indicates whether the operational state of the interface
is up or down."; is up or down.";
} }
} // interface-state-attributes }
// interface-state-attributes
grouping interface-state-attributes-igmp { grouping interface-state-attributes-igmp {
description description
"Per interface state attributes for IGMP."; "Per-interface state attributes for IGMP.";
uses interface-state-attributes; uses interface-state-attributes;
leaf querier { leaf querier {
type inet:ipv4-address; type inet:ipv4-address;
config false; config false;
mandatory true; mandatory true;
description "The querier address in the subnet"; description
"The querier address in the subnet.";
} }
leaf-list joined-group { leaf-list joined-group {
if-feature intf-join-group; if-feature "intf-join-group";
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
config false; config false;
description description
"The routers that joined this multicast group."; "The routers that joined this multicast group.";
} }
list group { list group {
key "group-address"; key "group-address";
config false; config false;
description description
"Multicast group membership information "Multicast group membership information
skipping to change at page 31, line 38 skipping to change at line 1527
config false; config false;
description description
"The routers that joined this multicast group."; "The routers that joined this multicast group.";
} }
list group { list group {
key "group-address"; key "group-address";
config false; config false;
description description
"Multicast group membership information "Multicast group membership information
that joined on the interface."; that joined on the interface.";
leaf group-address { leaf group-address {
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
description description
"Multicast group address."; "Multicast group address.";
} }
uses interface-state-group-attributes; uses interface-state-group-attributes;
leaf last-reporter { leaf last-reporter {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The IPv4 address of the last host which has sent the "The IPv4 address of the last host that has sent the
report to join the multicast group."; report to join the multicast group.";
} }
list source { list source {
key "source-address"; key "source-address";
description description
"List of multicast source information "List of multicast source information
of the multicast group."; of the multicast group.";
leaf source-address { leaf source-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Multicast source address in group record."; "Multicast source address in group record.";
} }
uses interface-state-source-attributes; uses interface-state-source-attributes;
leaf last-reporter { leaf last-reporter {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The IPv4 address of the last host which has sent the "The IPv4 address of the last host that has sent the
report to join the multicast source and group."; report to join the multicast source and group.";
} }
list host { list host {
if-feature intf-explicit-tracking; if-feature "intf-explicit-tracking";
key "host-address"; key "host-address";
description description
"List of hosts with the membership for the specific "List of hosts with the membership for the specific
multicast source-group."; multicast source-group.";
leaf host-address { leaf host-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"The IPv4 address of the host."; "The IPv4 address of the host.";
} }
uses interface-state-host-attributes; uses interface-state-host-attributes;
}// list host }
} // list source // list host
} // list group }
} // interface-state-attributes-igmp // list source
}
// list group
}
// interface-state-attributes-igmp
grouping interface-state-attributes-mld { grouping interface-state-attributes-mld {
description description
"Per interface state attributes for MLD."; "Per-interface state attributes for MLD.";
uses interface-state-attributes; uses interface-state-attributes;
leaf querier { leaf querier {
type inet:ipv6-address; type inet:ipv6-address;
config false; config false;
mandatory true; mandatory true;
description description
"The querier address in the subnet."; "The querier address in the subnet.";
} }
leaf-list joined-group { leaf-list joined-group {
if-feature intf-join-group; if-feature "intf-join-group";
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
config false; config false;
description description
"The routers that joined this multicast group."; "The routers that joined this multicast group.";
} }
list group { list group {
key "group-address"; key "group-address";
config false; config false;
description description
"Multicast group membership information "Multicast group membership information
skipping to change at page 33, line 13 skipping to change at line 1601
config false; config false;
description description
"The routers that joined this multicast group."; "The routers that joined this multicast group.";
} }
list group { list group {
key "group-address"; key "group-address";
config false; config false;
description description
"Multicast group membership information "Multicast group membership information
that joined on the interface."; that joined on the interface.";
leaf group-address { leaf group-address {
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
description description
"Multicast group address."; "Multicast group address.";
} }
uses interface-state-group-attributes; uses interface-state-group-attributes;
leaf last-reporter { leaf last-reporter {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The IPv6 address of the last host which has sent the "The IPv6 address of the last host that has sent the
report to join the multicast group."; report to join the multicast group.";
} }
list source { list source {
key "source-address"; key "source-address";
description description
"List of multicast sources of the multicast group."; "List of multicast sources of the multicast group.";
leaf source-address { leaf source-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Multicast source address in group record"; "Multicast source address in group record.";
} }
uses interface-state-source-attributes; uses interface-state-source-attributes;
leaf last-reporter { leaf last-reporter {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The IPv6 address of the last host which has sent the "The IPv6 address of the last host that has sent the
report to join the multicast source and group."; report to join the multicast source and group.";
} }
list host { list host {
if-feature intf-explicit-tracking; if-feature "intf-explicit-tracking";
key "host-address"; key "host-address";
description description
"List of hosts with the membership for the specific "List of hosts with the membership for the specific
multicast source-group."; multicast source-group.";
leaf host-address { leaf host-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"The IPv6 address of the host."; "The IPv6 address of the host.";
} }
uses interface-state-host-attributes; uses interface-state-host-attributes;
}// list host }
} // list source // list host
} // list group }
} // interface-state-attributes-mld // list source
}
// list group
}
// interface-state-attributes-mld
grouping interface-state-group-attributes { grouping interface-state-group-attributes {
description description
"Per interface state attributes for both IGMP and MLD "Per-interface state attributes for both IGMP and MLD
groups."; groups.";
leaf expire { leaf expire {
type uint32; type uint32;
units seconds; units "seconds";
mandatory true; mandatory true;
description description
"The time left before multicast group state expires."; "The time left before the multicast group state expires.";
} }
leaf filter-mode { leaf filter-mode {
type enumeration { type enumeration {
enum "include" { enum include {
description description
"In include mode, reception of packets sent "In include mode, reception of packets sent
to the specified multicast address is requested to the specified multicast address is requested
only from those IP source addresses listed in the only from those IP source addresses listed in the
source-list parameter"; source-list parameter";
} }
enum "exclude" { enum exclude {
description description
"In exclude mode, reception of packets sent "In exclude mode, reception of packets sent
to the given multicast address is requested to the given multicast address is requested
from all IP source addresses except those from all IP source addresses except those
listed in the source-list parameter."; listed in the source-list parameter.";
} }
} }
mandatory true; mandatory true;
description description
"Filter mode for a multicast group, "Filter mode for a multicast group,
may be either include or exclude."; may be either include or exclude.";
} }
leaf up-time { leaf up-time {
type uint32; type uint32;
units seconds; units "seconds";
mandatory true; mandatory true;
description description
"The elapsed time since the device created multicast group "The elapsed time since the device created multicast group
record."; record.";
} }
} // interface-state-group-attributes }
// interface-state-group-attributes
grouping interface-state-source-attributes { grouping interface-state-source-attributes {
description description
"Per interface state attributes for both IGMP and MLD "Per-interface state attributes for both IGMP and MLD
source-group records."; source-group records.";
leaf expire { leaf expire {
type uint32; type uint32;
units seconds; units "seconds";
mandatory true; mandatory true;
description description
"The time left before multicast source-group state expires."; "The time left before multicast source-group state expires.";
} }
leaf up-time { leaf up-time {
type uint32; type uint32;
units seconds; units "seconds";
mandatory true; mandatory true;
description description
"The elapsed time since the device created multicast "The elapsed time since the device created multicast
source-group record."; source-group record.";
} }
leaf host-count { leaf host-count {
if-feature intf-explicit-tracking; if-feature "intf-explicit-tracking";
type uint32; type uint32;
description description
"The number of host addresses."; "The number of host addresses.";
} }
} // interface-state-source-attributes }
// interface-state-source-attributes
grouping interface-state-host-attributes { grouping interface-state-host-attributes {
description description
"Per interface state attributes for both IGMP and MLD "Per-interface state attributes for both IGMP and MLD
hosts of source-group records."; hosts of source-group records.";
leaf host-filter-mode { leaf host-filter-mode {
type enumeration { type enumeration {
enum "include" { enum include {
description description
"In include mode"; "In include mode.";
} }
enum "exclude" { enum exclude {
description description
"In exclude mode."; "In exclude mode.";
} }
} }
mandatory true; mandatory true;
description description
"Filter mode for a multicast membership "Filter mode for a multicast membership
host may be either include or exclude."; host may be either include or exclude.";
} }
} // interface-state-host-attributes }
// interface-state-host-attributes
/* /*
* Configuration and Operational state data nodes (NMDA version) * Configuration and Operational state data nodes (NMDA version)
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'igmp-mld:igmp')" { when "derived-from-or-self(rt:type, 'igmp-mld:igmp')" {
description description
"This augmentation is only valid for a control-plane "This augmentation is only valid for a control-plane
protocol instance of IGMP (type 'igmp')."; protocol instance of IGMP (type 'igmp').";
} }
description description
"IGMP augmentation to routing control plane protocol "IGMP augmentation to routing control-plane protocol
configuration and state."; configuration and state.";
container igmp { container igmp {
if-feature feature-igmp; if-feature "feature-igmp";
description description
"IGMP configuration and operational state data."; "IGMP configuration and operational state data.";
container global { container global {
description description
"Global attributes."; "Global attributes.";
uses global-config-attributes; uses global-config-attributes;
uses global-state-attributes; uses global-state-attributes;
} }
container interfaces { container interfaces {
description description
"Containing a list of interfaces."; "Containing a list of interfaces.";
uses interfaces-config-attributes-igmp { uses interfaces-config-attributes-igmp {
if-feature interface-global-config; if-feature "interface-global-config";
refine query-interval { refine "query-interval" {
default 125; default "125";
} }
refine query-max-response-time { refine "query-max-response-time" {
default 10; default "10";
} }
refine robustness-variable { refine "robustness-variable" {
default 2; default "2";
} }
refine version { refine "version" {
default 2; default "2";
} }
} }
list interface { list interface {
key "interface-name"; key "interface-name";
description description
"List of IGMP interfaces."; "List of IGMP interfaces.";
leaf interface-name { leaf interface-name {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]/" must
+ "ip:ipv4" { '/if:interfaces/if:interface[if:name = current()]/'
+ 'ip:ipv4' {
error-message error-message
"The interface must have IPv4 configured, either " "The interface must have IPv4 configured, either "
+ "enabled or disabled."; + "enabled or disabled.";
} }
description description
"Reference to an entry in the global interface list."; "Reference to an entry in the global interface list.";
} }
uses interface-config-attributes-igmp { uses interface-config-attributes-igmp {
if-feature per-interface-config; if-feature "per-interface-config";
refine last-member-query-interval { refine "last-member-query-interval" {
must "../version != 1 or " must '../version != 1 or '
+ "(not(../version) and " + '(not(../version) and '
+ "(../../version != 1 or not(../../version)))" { + '(../../version != 1 or not(../../version)))' {
error-message error-message "IGMPv1 does not support "
"IGMPv1 does not support " + "last-member-query-interval.";
+ "last-member-query-interval.";
} }
} }
refine max-group-sources { refine "max-group-sources" {
must "../version = 3 or " must '../version = 3 or '
+ "(not(../version) and (../../version = 3))" { + '(not(../version) and (../../version = 3))' {
error-message error-message
"The version of IGMP must be 3 to support the " "The version of IGMP must be 3 to support the "
+ "source specific parameters."; + "source-specific parameters.";
} }
} }
refine source-policy { refine "source-policy" {
must "../version = 3 or " must '../version = 3 or '
+ "(not(../version) and (../../version = 3))" { + '(not(../version) and (../../version = 3))' {
error-message error-message
"The version of IGMP must be 3 to support the " "The version of IGMP must be 3 to support the "
+ "source specific parameters."; + "source-specific parameters.";
} }
} }
refine explicit-tracking { refine "explicit-tracking" {
must "../version = 3 or " must '../version = 3 or '
+ "(not(../version) and (../../version = 3))" { + '(not(../version) and (../../version = 3))' {
error-message error-message
"The version of IGMP must be 3 to support the " "The version of IGMP must be 3 to support the "
+ "explicit tracking function."; + "explicit tracking function.";
} }
} }
refine lite-exclude-filter { refine "lite-exclude-filter" {
must "../version = 3 or " must '../version = 3 or '
+ "(not(../version) and (../../version = 3))" { + '(not(../version) and (../../version = 3))' {
error-message error-message
"The version of IGMP must be 3 to support the " "The version of IGMP must be 3 to support the "
+ "simplified EXCLUDE filter in the Lightweight " + "simplified EXCLUDE filter in the Lightweight "
+ "IGMPv3 protocol."; + "IGMPv3 protocol.";
} }
} }
} }
uses interface-state-attributes-igmp; uses interface-state-attributes-igmp;
} // interface }
} // interfaces // interface
}
// interfaces
/* /*
* Actions * Actions
*/ */
action clear-groups { action clear-groups {
if-feature action-clear-groups; if-feature "action-clear-groups";
description description
"Clears the specified IGMP cache entries."; "Clears the specified IGMP cache entries.";
input { input {
choice interface { choice interface {
mandatory true; mandatory true;
description description
"Indicates the interface(s) from which the cache "Indicates the interface(s) from which the cache
entries are cleared."; entries are cleared.";
case name { case name {
leaf interface-name { leaf interface-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
skipping to change at page 38, line 39 skipping to change at line 1870
input { input {
choice interface { choice interface {
mandatory true; mandatory true;
description description
"Indicates the interface(s) from which the cache "Indicates the interface(s) from which the cache
entries are cleared."; entries are cleared.";
case name { case name {
leaf interface-name { leaf interface-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/" + "rt:control-plane-protocol/"
+ "igmp-mld:igmp/igmp-mld:interfaces/" + "igmp-mld:igmp/igmp-mld:interfaces/"
+ "igmp-mld:interface/igmp-mld:interface-name"; + "igmp-mld:interface/igmp-mld:interface-name";
} }
description description
"Name of the IGMP interface."; "Name of the IGMP interface.";
} }
} }
case all { case all {
leaf all-interfaces { leaf all-interfaces {
type empty; type empty;
description description
"IGMP groups from all interfaces are cleared."; "IGMP groups from all interfaces are cleared.";
skipping to change at page 39, line 4 skipping to change at line 1884
description description
"Name of the IGMP interface."; "Name of the IGMP interface.";
} }
} }
case all { case all {
leaf all-interfaces { leaf all-interfaces {
type empty; type empty;
description description
"IGMP groups from all interfaces are cleared."; "IGMP groups from all interfaces are cleared.";
} }
} }
} }
leaf group-address { leaf group-address {
type union { type union {
type enumeration { type enumeration {
enum '*' { enum * {
description description
"Any group address."; "Any group address.";
} }
} }
type rt-types:ipv4-multicast-group-address; type rt-types:ipv4-multicast-group-address;
} }
mandatory true; mandatory true;
description description
"Multicast group IPv4 address. "Multicast group IPv4 address.
If the value '*' is specified, all IGMP group entries If the value '*' is specified, all IGMP group entries
skipping to change at page 39, line 32 skipping to change at line 1911
} }
leaf source-address { leaf source-address {
type rt-types:ipv4-multicast-source-address; type rt-types:ipv4-multicast-source-address;
mandatory true; mandatory true;
description description
"Multicast source IPv4 address. "Multicast source IPv4 address.
If the value '*' is specified, all IGMP source-group If the value '*' is specified, all IGMP source-group
entries are cleared."; entries are cleared.";
} }
} }
} // action clear-groups }
} // igmp // action clear-groups
} //augment }
// igmp
}
// augment
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'igmp-mld:mld')" { when "derived-from-or-self(rt:type, 'igmp-mld:mld')" {
description description
"This augmentation is only valid for a control-plane "This augmentation is only valid for a control-plane
protocol instance of IGMP (type 'mld')."; protocol instance of IGMP (type 'mld').";
} }
description description
"MLD augmentation to routing control plane protocol "MLD augmentation to routing control-plane protocol
configuration and state."; configuration and state.";
container mld { container mld {
if-feature feature-mld; if-feature "feature-mld";
description description
"MLD configuration and operational state data."; "MLD configuration and operational state data.";
container global { container global {
description description
"Global attributes."; "Global attributes.";
uses global-config-attributes; uses global-config-attributes;
uses global-state-attributes; uses global-state-attributes;
} }
container interfaces { container interfaces {
description description
"Containing a list of interfaces."; "Containing a list of interfaces.";
uses interfaces-config-attributes-mld { uses interfaces-config-attributes-mld {
if-feature interface-global-config; if-feature "interface-global-config";
refine last-member-query-interval { refine "last-member-query-interval" {
default 1; default "1";
} }
refine query-interval { refine "query-interval" {
default 125; default "125";
} }
refine query-max-response-time { refine "query-max-response-time" {
default 10; default "10";
} }
refine require-router-alert { refine "require-router-alert" {
default true; default "true";
} }
refine robustness-variable { refine "robustness-variable" {
default 2; default "2";
} }
refine version { refine "version" {
default 2; default "2";
} }
} }
list interface { list interface {
key "interface-name"; key "interface-name";
description description
"List of MLD interfaces."; "List of MLD interfaces.";
leaf interface-name { leaf interface-name {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]/" must
+ "ip:ipv6" { '/if:interfaces/if:interface[if:name = current()]/'
+ 'ip:ipv6' {
error-message error-message
"The interface must have IPv6 configured, either " "The interface must have IPv6 configured, either "
+ "enabled or disabled."; + "enabled or disabled.";
} }
description description
"Reference to an entry in the global interface list."; "Reference to an entry in the global interface list.";
} }
uses interface-config-attributes-mld { uses interface-config-attributes-mld {
if-feature per-interface-config; if-feature "per-interface-config";
refine max-group-sources { refine "max-group-sources" {
must "../version = 2 or " must '../version = 2 or '
+ "(not(../version) and " + '(not(../version) and '
+ "(../../version = 2 or not(../../version)))" { + '(../../version = 2 or not(../../version)))' {
error-message error-message
"The version of MLD must be 2 to support the " "The version of MLD must be 2 to support the "
+ "source specific parameters."; + "source-specific parameters.";
} }
} }
refine source-policy { refine "source-policy" {
must "../version = 2 or " must '../version = 2 or '
+ "(not(../version) and " + '(not(../version) and '
+ "(../../version = 2 or not(../../version)))" { + '(../../version = 2 or not(../../version)))' {
error-message error-message
"The version of MLD must be 2 to support the " "The version of MLD must be 2 to support the "
+ "source specific parameters."; + "source-specific parameters.";
} }
} }
refine explicit-tracking { refine "explicit-tracking" {
must "../version = 2 or " must '../version = 2 or '
+ "(not(../version) and " + '(not(../version) and '
+ "(../../version = 2 or not(../../version)))" { + '(../../version = 2 or not(../../version)))' {
error-message error-message
"The version of MLD must be 2 to support the " "The version of MLD must be 2 to support the "
+ "explicit tracking function."; + "explicit tracking function.";
} }
} }
refine lite-exclude-filter { refine "lite-exclude-filter" {
must "../version = 2 or " must '../version = 2 or '
+ "(not(../version) and " + '(not(../version) and '
+ "(../../version = 2 or not(../../version)))" { + '(../../version = 2 or not(../../version)))' {
error-message error-message
"The version of MLD must be 2 to support the " "The version of MLD must be 2 to support the "
+ "simplified EXCLUDE filter in the Lightweight " + "simplified EXCLUDE filter in the Lightweight "
+ "MLDv2 protocol."; + "MLDv2 protocol.";
} }
} }
} }
uses interface-state-attributes-mld; uses interface-state-attributes-mld;
} // interface }
} // interfaces // interface
}
// interfaces
/* /*
* Actions * Actions
*/ */
action clear-groups { action clear-groups {
if-feature action-clear-groups; if-feature "action-clear-groups";
description description
"Clears the specified MLD cache entries."; "Clears the specified MLD cache entries.";
input { input {
choice interface { choice interface {
mandatory true; mandatory true;
description description
"Indicates the interface(s) from which the cache "Indicates the interface(s) from which the cache
entries are cleared."; entries are cleared.";
case name { case name {
leaf interface-name { leaf interface-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
skipping to change at page 42, line 15 skipping to change at line 2041
input { input {
choice interface { choice interface {
mandatory true; mandatory true;
description description
"Indicates the interface(s) from which the cache "Indicates the interface(s) from which the cache
entries are cleared."; entries are cleared.";
case name { case name {
leaf interface-name { leaf interface-name {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/" + "rt:control-plane-protocol/"
+ "igmp-mld:mld/igmp-mld:interfaces/" + "igmp-mld:mld/igmp-mld:interfaces/"
+ "igmp-mld:interface/igmp-mld:interface-name"; + "igmp-mld:interface/igmp-mld:interface-name";
} }
description description
"Name of the MLD interface."; "Name of the MLD interface.";
} }
} }
case all { case all {
leaf all-interfaces { leaf all-interfaces {
type empty; type empty;
description description
"MLD groups from all interfaces are cleared."; "MLD groups from all interfaces are cleared.";
} }
} }
} }
leaf group-address { leaf group-address {
type union { type union {
type enumeration { type enumeration {
enum '*' { enum * {
description description
"Any group address."; "Any group address.";
} }
} }
type rt-types:ipv6-multicast-group-address; type rt-types:ipv6-multicast-group-address;
} }
description description
"Multicast group IPv6 address. "Multicast group IPv6 address.
If the value '*' is specified, all MLD group entries If the value '*' is specified, all MLD group entries
are cleared."; are cleared.";
} }
leaf source-address { leaf source-address {
type rt-types:ipv6-multicast-source-address; type rt-types:ipv6-multicast-source-address;
description description
"Multicast source IPv6 address. "Multicast source IPv6 address.
If the value '*' is specified, all MLD source-group If the value '*' is specified, all MLD source-group
entries are cleared."; entries are cleared.";
} }
} }
}
} // action clear-mld-groups // action clear-mld-groups
} // mld }
} // augment // mld
}
// augment
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. 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 that is designed to be accessed via network management protocols such
such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
layer is the secure transport layer, and the mandatory-to-implement is the secure transport layer, and the mandatory-to-implement secure
secure transport is Secure Shell (SSH) [RFC6242]. The lowest transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
RESTCONF layer is HTTPS, and the mandatory-to-implement secure is HTTPS, and the mandatory-to-implement secure transport is TLS
transport is TLS [RFC8446]. [RFC8446].
The Network Configuration Access Control Model (NACM) [RFC8341] The Network Configuration Access Control Model (NACM) [RFC8341]
provides the means to restrict access for particular NETCONF or provides the means to restrict access for particular NETCONF or
RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or
RESTCONF protocol operations and content. RESTCONF protocol operations and content.
There are a number of data nodes defined in this YANG module that There are a number of data nodes defined in this YANG module that are
are writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
Under /rt:routing/rt:control-plane-protocols Under /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmp-mld:igmp, /rt:control-plane-protocol/igmp-mld:igmp,
igmp-mld:global igmp-mld:global
This subtree specifies the configuration for the IGMP attributes
This subtree specifies the configuration for the IGMP attributes at the global level on an IGMP instance. Modifying the
at the global level on an IGMP instance. Modifying the configuration can cause IGMP membership to be deleted or
configuration can cause IGMP membership to be deleted or reconstructed on all the interfaces of an IGMP instance.
reconstructed on all the interfaces of an IGMP instance.
igmp-mld:interfaces igmp-mld:interfaces
This subtree specifies the configuration for the IGMP attributes
This subtree specifies the configuration for the IGMP attributes at the interface-global level on an IGMP instance. Modifying the
at the interface-global level on a IGMP instance. Modifying the configuration can cause IGMP membership to be deleted or
configuration can cause IGMP membership to be deleted or reconstructed on all the interfaces of an IGMP instance.
reconstructed on all the interfaces of an IGMP instance.
igmp-mld:interfaces/interface igmp-mld:interfaces/interface
This subtree specifies the configuration for the IGMP attributes This subtree specifies the configuration for the IGMP attributes
at the interface level on an IGMP instance. Modifying the at the interface level on an IGMP instance. Modifying the
configuration can cause IGMP membership to be deleted or configuration can cause IGMP membership to be deleted or
reconstructed on a specific interface of an IGMP instance. reconstructed on a specific interface of an IGMP instance.
Under /rt:routing/rt:control-plane-protocols Under /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmp-mld:mld, /rt:control-plane-protocol/igmp-mld:mld,
igmp-mld:global igmp-mld:global
This subtree specifies the configuration for the MLD attributes at
This subtree specifies the configuration for the MLD attributes at the global level on an MLD instance. Modifying the configuration
the global level on an MLD instance. Modifying the configuration can cause MLD membership to be deleted or reconstructed on all the
can cause MLD membership to be deleted or reconstructed on all the interfaces of an MLD instance.
interfaces of an MLD instance.
igmp-mld:interfaces igmp-mld:interfaces
This subtree specifies the configuration for the MLD attributes at
This subtree specifies the configuration for the MLD attributes at the interface-global level on an MLD instance. Modifying the
the interface-global level on an MLD instance. Modifying the configuration can cause MLD membership to be deleted or
configuration can cause MLD membership to be deleted or reconstructed on all the interfaces of an MLD instance.
reconstructed on all the interfaces of an MLD instance.
igmp-mld:interfaces/interface igmp-mld:interfaces/interface
This subtree specifies the configuration for the MLD attributes at
This subtree specifies the configuration for the MLD attributes at the interface level on a device. Modifying the configuration can
the interface level on a device. Modifying the configuration can cause MLD membership to be deleted or reconstructed on a specific
cause MLD membership to be deleted or reconstructed on a specific interface of an MLD instance.
interface of an MLD instance.
Unauthorized access to any data node of these subtrees can adversely Unauthorized access to any data node of these subtrees can adversely
affect the membership records of multicast routing subsystem on the affect the membership records of multicast routing subsystem on the
local device. This may lead to network malfunctions, delivery of local device. This may lead to network malfunctions, delivery of
packets to inappropriate destinations, and other problems. packets to inappropriate destinations, and other problems.
Some of the readable data nodes in this YANG module may be Some of the readable data nodes in this YANG module may be considered
considered sensitive or vulnerable in some network environments. It sensitive or vulnerable in some network environments. It is thus
is thus important to control read access (e.g., via get, get-config, important to control read access (e.g., via get, get-config, or
or notification) to these data nodes. These are the subtrees and notification) to these data nodes. These are the subtrees and data
data nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/rt:routing/rt:control-plane-protocols /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmmp-mld:igmp /rt:control-plane-protocol/igmmp-mld:igmp
/rt:routing/rt:control-plane-protocols /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmp-mld:mld /rt:control-plane-protocol/igmp-mld:mld
Unauthorized access to any data node of the above subtree can Unauthorized access to any data node of the above subtree can
disclose the operational state information of IGMP or MLD on this disclose the operational state information of IGMP or MLD on this
device. device.
Some of the action operations in this YANG module may be considered Some of the action operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the important to control access to these operations. These are the
operations and their sensitivity/vulnerability: operations and their sensitivity/vulnerability:
/rt:routing/rt:control-plane-protocols /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmmp-mld:igmp/igmmp-mld:clear-groups /rt:control-plane-protocol/igmmp-mld:igmp/igmmp-mld:clear-groups
/rt:routing/rt:control-plane-protocols /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/igmp-mld:mld/igmp-mld:clear-groups /rt:control-plane-protocol/igmp-mld:mld/igmp-mld:clear-groups
Unauthorized access to any of the above action operations can delete Unauthorized access to any of the above action operations can delete
the IGMP or MLD membership records on this device. the IGMP or MLD membership records on this device.
6. IANA Considerations 6. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld
URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
-------------------------------------------------------------------- Registrant Contact: The IESG.
This document registers the following YANG modules in the YANG Module XML: N/A; the requested URI is an XML namespace.
Names registry [RFC6020]:
-------------------------------------------------------------------- This document registers the following YANG modules in the YANG Module
Names registry [RFC6020]:
name: ietf-igmp-mld Name: ietf-igmp-mld
namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld Namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld
prefix: igmp-mld Prefix: igmp-mld
reference: RFC XXXX Reference: RFC 8652
--------------------------------------------------------------------
7. Acknowledgments 7. References
The authors would like to thank Steve Baillargeon, Hu Fangwei, 7.1. Normative References
Robert Kebler, Tanmoy Kundu, and Stig Venaas for their valuable
contributions.
8. Contributing Authors [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, DOI 10.17487/RFC1112, August 1989,
<https://www.rfc-editor.org/info/rfc1112>.
Yisong Liu [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Huawei Technologies Requirement Levels", BCP 14, RFC 2119,
Huawei Bldg., No.156 Beiqing Rd. DOI 10.17487/RFC2119, March 1997,
Beijing 100095 <https://www.rfc-editor.org/info/rfc2119>.
China
Email: liuyisong@huawei.com [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, DOI 10.17487/RFC2236, November 1997,
<https://www.rfc-editor.org/info/rfc2236>.
9. References [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710,
DOI 10.17487/RFC2710, October 1999,
<https://www.rfc-editor.org/info/rfc2710>.
9.1. Normative References [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, DOI 10.17487/RFC3376, October 2002,
<https://www.rfc-editor.org/info/rfc3376>.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
RFC 1112, August 1989. DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC3810] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener
Requirement Levels", BCP 14, RFC 2119, March 1997. Discovery Version 2 (MLDv2) for IPv6", RFC 3810,
DOI 10.17487/RFC3810, June 2004,
<https://www.rfc-editor.org/info/rfc3810>.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
2", RFC 2236, November 1997. IP", RFC 4607, DOI 10.17487/RFC4607, August 2006,
<https://www.rfc-editor.org/info/rfc4607>.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Listener Discovery (MLD) for IPv6", RFC 2710, October the Network Configuration Protocol (NETCONF)", RFC 6020,
1999. DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
Thyagarajan, "Internet Group Management Protocol, Version and A. Bierman, Ed., "Network Configuration Protocol
3", RFC 3376, October 2002. (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
2004. Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
IP", RFC 4607, August 2006. RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
the Network Configuration Protocol (NETCONF)", RFC 6020, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
October 2010. <https://www.rfc-editor.org/info/rfc8040>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
and A. Bierman, Ed., "Network Configuration Protocol 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
(NETCONF)", RFC 6241, June 2011. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
Shell (SSH)", RFC 6242, June 2011. "Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
RFC 6991, July 2013. Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
RFC 7950, August 2016. and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Protocol", RFC 8040, January 2017. Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
2119 Key Words", BCP 14, RFC 8174, May 2017. RFC 8344, DOI 10.17487/RFC8344, March 2018,
<https://www.rfc-editor.org/info/rfc8344>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
"Common YANG Data Types for the Routing Area", RFC 8294, Routing Management (NMDA Version)", RFC 8349,
December 2017. DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Access Control Model", STD 91, RFC 8341, March 2018. Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair,
and R. Wilton, "Network Management Datastore Architecture "YANG Data Model for Network Access Control Lists (ACLs)",
(NMDA)", RFC 8342, March 2018. RFC 8519, DOI 10.17487/RFC8519, March 2019,
<https://www.rfc-editor.org/info/rfc8519>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface 7.2. Informative References
Management", RFC 8343, March 2018.
[RFC8344] M. Bjorklund, "A YANG Data Model for IP Management", [RFC3569] Bhattacharyya, S., Ed., "An Overview of Source-Specific
RFC8344, March 2018. Multicast (SSM)", RFC 3569, DOI 10.17487/RFC3569, July
2003, <https://www.rfc-editor.org/info/rfc3569>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC4541] Christensen, M., Kimball, K., and F. Solensky,
Routing Management (NMDA Version)", RFC 8349, March 2018. "Considerations for Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) Snooping
Switches", RFC 4541, DOI 10.17487/RFC4541, May 2006,
<https://www.rfc-editor.org/info/rfc4541>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick,
Version 1.3", RFC 8446, August 2018. "Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding
("IGMP/MLD Proxying")", RFC 4605, DOI 10.17487/RFC4605,
August 2006, <https://www.rfc-editor.org/info/rfc4605>.
[RFC8519] M. Jethanandani, S. Agarwal, L. Huang and D. Blair, "YANG [RFC5790] Liu, H., Cao, W., and H. Asaeda, "Lightweight Internet
Data Model for Network Access Control Lists (ACLs)", RFC Group Management Protocol Version 3 (IGMPv3) and Multicast
8519, March 2019. Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790,
DOI 10.17487/RFC5790, February 2010,
<https://www.rfc-editor.org/info/rfc5790>.
9.2. Informative References [RFC6636] Asaeda, H., Liu, H., and Q. Wu, "Tuning the Behavior of
the Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) for Routers in Mobile
and Wireless Networks", RFC 6636, DOI 10.17487/RFC6636,
May 2012, <https://www.rfc-editor.org/info/rfc6636>.
[RFC3569] Bhattacharyya, S., Ed., "An Overview of Source-Specific [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
Multicast (SSM)", RFC 3569, July 2003. BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC4541] M. Christensen, K. Kimball and F. Solensky, [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of
"Considerations for Internet Group Management Protocol Documents Containing YANG Data Models", BCP 216, RFC 8407,
(IGMP) and Multicast Listener Discovery (MLD) Snooping DOI 10.17487/RFC8407, October 2018,
Switches", RFC 4541, May 2006. <https://www.rfc-editor.org/info/rfc8407>.
[RFC4605] B. Fenner, H. He, B. Haberman, and H. Sandick, "Internet [RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
Group Management Protocol (IGMP) / Multicast Listener E., and A. Tripathy, "Subscription to YANG Notifications",
Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD RFC 8639, DOI 10.17487/RFC8639, September 2019,
Proxying")", RFC 4605, August 2006. <https://www.rfc-editor.org/info/rfc8639>.
[RFC5790] H. Liu, W. Cao and H. Asaeda, "Lightweight Internet Group [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
Management Protocol Version 3 (IGMPv3) and Multicast for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790, September 2019, <https://www.rfc-editor.org/info/rfc8641>.
February 2010.
[RFC6636] H. Asaeda, H. Liu and Q. Wu, "Tuning the Behavior of the Acknowledgments
Internet Group Management Protocol (IGMP) and Multicast
Listener Discovery (MLD) for Routers in Mobile and
Wireless Networks", RFC 6636, May 2012.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", The authors would like to thank Steve Baillargeon, Hu Fangwei, Robert
BCP 215, RFC 8340, March 2018. Kebler, Tanmoy Kundu, and Stig Venaas for their valuable
contributions.
[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of Contributors
Documents Containing YANG Data Models", RFC 8407, October
2018.
[I-D.ietf-netconf-subscribed-notifications] Yisong Liu
Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and Huawei Technologies
A. Tripathy, "Customized Subscriptions to a Publisher's China
Event Streams", draft-ietf-netconf-subscribed-
notifications-26 (work in progress), May 2019.
[I-D.ietf-netconf-yang-push] Email: liuyisong@huawei.com
Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-
Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore
Subscription", draft-ietf-netconf-yang-push-25 (work in
progress), May 2019.
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
Email: xufeng.liu.ietf@gmail.com Email: xufeng.liu.ietf@gmail.com
Feng Guo Feng Guo
Huawei Technologies
Huawei Bldg., No.156 Beiqing Rd.
Beijing 100095
China China
100095
Beijing
Huawei Bldg., No. 156 Beiqing Rd., Haidian District
Huawei Technologies
Email: guofeng@huawei.com Email: guofeng@huawei.com
Mahesh Sivakumar Mahesh Sivakumar
Juniper Networks Juniper Networks
1133 Innovation Way 1133 Innovation Way
Sunnyvale, California Sunnyvale, California
USA United States of America
Email: sivakumar.mahesh@gmail.com Email: sivakumar.mahesh@gmail.com
Pete McAllister Pete McAllister
Metaswitch Networks Metaswitch Networks
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield
UK EN2 6BQ
United Kingdom
Email: pete.mcallister@metaswitch.com Email: pete.mcallister@metaswitch.com
Anish Peter Anish Peter
Individual IP Infusion India
RMZ Centennial, Block D 401
Kundanahalli Main Road, Mahadevapura Post
Bangalore
India
Email: anish.ietf@gmail.com Email: anish.ietf@gmail.com
 End of changes. 391 change blocks. 
718 lines changed or deleted 761 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/