< draft-ietf-pim-igmp-mld-yang-13.txt   draft-ietf-pim-igmp-mld-yang-14.txt >
PIM Working Group X. Liu PIM Working Group X. Liu
Internet-Draft Volta Networks Internet-Draft Volta Networks
Intended Status: Standard Track F. Guo Intended Status: Standard Track F. Guo
Expires: November 23, 2019 Huawei Expires: November 29, 2019 Huawei
M. Sivakumar M. Sivakumar
Juniper Juniper
P. McAllister P. McAllister
Metaswitch Networks Metaswitch Networks
A. Peter A. Peter
Individual Individual
May 23, 2019 May 29, 2019
A YANG Data Model for Internet Group Management Protocol (IGMP) and A YANG Data Model for Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) Multicast Listener Discovery (MLD)
draft-ietf-pim-igmp-mld-yang-13 draft-ietf-pim-igmp-mld-yang-14
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on November 23, 2019. This Internet-Draft will expire on November 29, 2019.
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 (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 16 skipping to change at page 2, line 16
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Abstract Abstract
This document defines a YANG data model that can be used to This document defines a YANG data model that can be used to
configure and manage Internet Group Management Protocol (IGMP) and configure and manage Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) devices. 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...................................................2 1. Introduction...................................................3
1.1. Terminology...............................................3 1.1. Terminology...............................................3
1.2. Tree Diagrams.............................................3 1.2. Tree Diagrams.............................................4
1.3. Prefixes in Data Node Names...............................3 1.3. Prefixes in Data Node Names...............................4
2. Design of Data model...........................................4 2. Design of Data model...........................................4
2.1. Scope of Model............................................4 2.1. Scope of Model............................................4
2.1.1. Parameters Not Covered at Global Level..................5 2.1.1. Parameters Not Covered at Global Level..................5
2.1.2. Parameters Not Covered at Interface Level...............5 2.1.2. Parameters Not Covered at Interface Level...............5
2.2. Optional Capabilities.....................................5 2.2. Optional Capabilities.....................................6
2.3. Position of Address Family in Hierarchy...................6 2.3. Position of Address Family in Hierarchy...................6
3. Module Structure...............................................7 3. Module Structure...............................................7
3.1. IGMP Configuration and Operational State..................7 3.1. IGMP Configuration and Operational State..................7
3.2. MLD Configuration and Operational State..................10 3.2. MLD Configuration and Operational State..................10
3.3. IGMP and MLD Actions.....................................13 3.3. IGMP and MLD Actions.....................................13
4. IGMP and MLD YANG Module......................................13 4. IGMP and MLD YANG Module......................................13
5. Security Considerations.......................................39 5. Security Considerations.......................................39
6. IANA Considerations...........................................42 6. IANA Considerations...........................................42
7. Acknowledgments...............................................42 7. Acknowledgments...............................................42
8. Contributing Authors..........................................43 8. Contributing Authors..........................................43
skipping to change at page 4, line 34 skipping to change at page 4, line 45
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 there is no protocol can be retrieved by this model. Even though no protocol specific
specific notifications are defined in this model, the subscription notifications are defined in this model, the subscription and push
and push mechanism defined in [I-D.ietf-netconf-subscribed- mechanism defined in [I-D.ietf-netconf-subscribed-notifications] and
notifications] and [I-D.ietf-netconf-yang-push] can be used by the [I-D.ietf-netconf-yang-push] can be used by the user to subscribe to
user to subscribe notifications on the data nodes in this model. notifications on the data nodes in this model.
The model contains all basic configuration parameters to operate the The model contains all the basic configuration parameters to operate
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 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 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 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
skipping to change at page 6, line 32 skipping to change at page 6, line 40
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 supports and only supports IPv4, while the The protocol IGMP only supports IPv4, while the protocol MLD only
protocol MLD supports and only supports IPv6. The data model defined supports IPv6. The data model defined in this document can be used
in this document can be used for both IPv4 and IPv6 address for both IPv4 and IPv6 address families.
families.
The current document defines IGMP and MLD as separate schema This document defines IGMP and MLD as separate schema branches in
branches in the structure. The benefits are: the structure. The benefits are:
o The model can support IGMP (IPv4), MLD (IPv6), or both o The model can support IGMP (IPv4), MLD (IPv6), or both
optionally and independently. Such flexibility cannot be optionally and independently. Such flexibility cannot be
achieved cleanly with a combined branch. achieved cleanly with a combined branch.
o The structure is consistent with other YANG models such as RFC o The structure is consistent with other YANG models such as RFC
8344, which uses separate branches for IPv4 and IPv6. 8344, which uses separate branches for IPv4 and IPv6.
o The separate branches for IGMP and MLD can accommodate their o 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
skipping to change at page 9, line 38 skipping to change at page 9, line 41
+--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 exclude-lite? empty
| {intf-exclude-lite}? | {intf-exclude-lite}?
+--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 19 skipping to change at page 10, line 22
+--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
skipping to change at page 12, line 27 skipping to change at page 12, line 29
+--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 exclude-lite? empty
| {intf-exclude-lite}? | {intf-exclude-lite}?
+--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 8 skipping to change at page 13, line 10
+--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 which 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:
skipping to change at page 13, line 47 skipping to change at page 13, line 49
| +--:(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],
[RFC3810], [RFC5790], [RFC6991], [RFC8294], [RFC8343], [RFC8344],
[RFC8349], and [RFC8519].
<CODE BEGINS> file "ietf-igmp-mld@2019-05-21.yang" <CODE BEGINS> file "ietf-igmp-mld@2019-05-21.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";
} }
skipping to change at page 14, line 51 skipping to change at page 15, line 9
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://tools.ietf.org/wg/pim/>
WG List: <mailto:pim@ietf.org> WG List: <mailto:pim@ietf.org>
WG Chair: Stig Venaas
<mailto:stig@venaas.com>
WG Chair: Mike McBride
<mailto:mmcbride7@gmail.com>
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>
Editor: Pete McAllister Editor: Pete McAllister
skipping to change at page 15, line 43 skipping to change at page 15, line 44
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 XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove // RFC Ed.: replace XXXX with actual RFC number and remove
// this note // this note
revision 2019-05-21 { revision 2019-05-29 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for IGMP and MLD"; "RFC XXXX: A YANG Data Model for IGMP and MLD";
} }
/* /*
* Features * Features
*/ */
skipping to change at page 18, line 45 skipping to change at page 18, line 45
"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"; base "rt:control-plane-protocol";
description "IGMP protocol."; description "IGMP protocol.";
reference reference
"RFC3376: Internet Group Management Protocol, Version 3."; "RFC 3376: Internet Group Management Protocol, Version 3.";
} }
identity mld { identity mld {
base "rt:control-plane-protocol"; base "rt:control-plane-protocol";
description "MLD protocol."; description "MLD protocol.";
reference reference
"RFC3810: 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.
skipping to change at page 22, line 38 skipping to change at page 22, line 38
leaf last-member-query-interval { leaf last-member-query-interval {
type uint16 { type uint16 {
range "1..1023"; range "1..1023";
} }
units seconds; units seconds;
default 1; default 1;
description description
"Last Member Query Interval, which may be tuned to modify the "Last Member Query Interval, which may be tuned to modify the
leave latency of the network."; leave latency of the network.";
reference "RFC3376. Sec. 8.8."; reference "RFC 3376. Sec. 8.8.";
} }
leaf query-interval { leaf query-interval {
type uint16 { type uint16 {
range "1..31744"; range "1..31744";
} }
units seconds; units seconds;
default 125; default 125;
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 RFC3376, 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 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.";
reference "RFC3376. Sec. 4.1.7, 8.2, 8.14.2."; reference "RFC 3376. Sec. 4.1.7, 8.2, 8.14.2.";
} }
leaf query-max-response-time { leaf query-max-response-time {
type uint16 { type uint16 {
range "1..1023"; range "1..1023";
} }
units seconds; units seconds;
default 10; default 10;
description description
"Query maximum response time specifies the maximum time "Query maximum response time specifies the maximum time
allowed before sending a responding report."; allowed before sending a responding report.";
reference "RFC3376. Sec. 4.1.1, 8.3, 8.14.3."; reference "RFC 3376. Sec. 4.1.1, 8.3, 8.14.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;
default false; default false;
description description
"Protocol packets should contain router alert IP option."; "Protocol packets should contain router alert IP option.";
} }
leaf robustness-variable { leaf robustness-variable {
type uint8 { type uint8 {
range "1..7"; range "1..7";
} }
default 2; default 2;
description description
"Querier's Robustness Variable allows tuning for the "Querier's Robustness Variable allows tuning for the
expected packet loss on a network."; expected packet loss on a network.";
reference "RFC3376. Sec. 4.1.6, 8.1, 8.14.1."; reference "RFC 3376. Sec. 4.1.6, 8.1, 8.14.1.";
} }
} // 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";
} }
default 2; default 2;
description "IGMP version."; description "IGMP version.";
reference "RFC1112, RFC2236, RFC3376."; reference "RFC 1112, RFC 2236, RFC 3376.";
} }
} }
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";
} }
default 2; default 2;
description "MLD version."; description "MLD version.";
reference "RFC2710, RFC3810."; reference "RFC 2710, RFC 3810.";
} }
} }
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;
skipping to change at page 27, line 28 skipping to change at page 27, line 28
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 "RFC5790"; reference "RFC 5790";
} }
} // 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 {
skipping to change at page 29, line 34 skipping to change at page 29, line 34
"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-igmp-mld { 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 {
skipping to change at page 30, line 6 skipping to change at page 30, line 6
"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-config-attributes-igmp-mld } // 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-igmp-mld; 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;
skipping to change at page 30, line 38 skipping to change at page 30, line 38
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-igmp-mld; 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 which 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-igmp-mld; 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 which 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 IPv6 address of the host."; "The IPv4 address of the host.";
} }
uses interface-state-host-attributes-igmp-mld; uses interface-state-host-attributes;
}// list host }// list host
} // list source } // list source
} // list group } // list group
} // interface-state-attributes-igmp } // 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-igmp-mld; 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;
skipping to change at page 32, line 13 skipping to change at page 32, line 13
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-igmp-mld; 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 which 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-igmp-mld; 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 which 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-igmp-mld; uses interface-state-host-attributes;
}// list host }// list host
} // list source } // list source
} // list group } // list group
} // interface-state-attributes-mld } // interface-state-attributes-mld
grouping interface-state-group-attributes-igmp-mld { 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 multicast group state expires.";
skipping to change at page 33, line 49 skipping to change at page 33, line 49
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-igmp-mld } // interface-state-group-attributes
grouping interface-state-source-attributes-igmp-mld { 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.";
skipping to change at page 34, line 27 skipping to change at page 34, line 27
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-igmp-mld } // interface-state-source-attributes
grouping interface-state-host-attributes-igmp-mld { 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-igmp-mld } // 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').";
skipping to change at page 39, line 51 skipping to change at page 39, line 51
<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 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
layer is the secure transport layer, and the mandatory-to-implement layer is the secure transport layer, and the mandatory-to-implement
secure transport is Secure Shell (SSH) [RFC6242]. The lowest secure transport is Secure Shell (SSH) [RFC6242]. The lowest
RESTCONF layer is HTTPS, and the mandatory-to-implement secure RESTCONF layer is HTTPS, and the mandatory-to-implement secure
transport is TLS [RFC 8446]. transport is TLS [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 writable/creatable/deletable (i.e., config true, which is the are 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)
skipping to change at page 40, line 25 skipping to change at page 40, line 25
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 deleted or reconstructed configuration can cause IGMP membership to be deleted or
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 a IGMP instance. Modifying the at the interface-global level on a IGMP instance. Modifying the
configuration can cause IGMP membership deleted or reconstructed configuration can cause IGMP membership to be deleted or
on all the interfaces of an IGMP instance. reconstructed on all the interfaces of an IGMP instance.
igmp-mold: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 deleted or reconstructed configuration can cause IGMP membership to be deleted or
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 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 deleted or reconstructed on configuration can cause MLD membership to be deleted or
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 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 sensitive or vulnerable in some network environments. It considered sensitive or vulnerable in some network environments. It
is thus important to control read access (e.g., via get, get-config, is thus important to control read access (e.g., via get, get-config,
skipping to change at page 43, line 22 skipping to change at page 43, line 22
Email: liuyisong@huawei.com Email: liuyisong@huawei.com
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989. RFC 1112, August 1989.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710, October Listener Discovery (MLD) for IPv6", RFC 2710, October
1999. 1999.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC3569] Bhattacharyya, S., Ed., "An Overview of Source-Specific
Multicast (SSM)", RFC 3569, July 2003.
[RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January [RFC3688] Mealling, M., "The IETF XML Registry", RFC 3688, January
2004. 2004.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006. IP", RFC 4607, August 2006.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, June 2011. (NETCONF)", RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, June 2011.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, March
2012.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, July 2013. RFC 6991, July 2013.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, August 2016. RFC 7950, August 2016.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, January 2017. Protocol", RFC 8040, January 2017.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, May 2017.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294, "Common YANG Data Types for the Routing Area", RFC 8294,
December 2017. December 2017.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, March 2018.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018. (NMDA)", RFC 8342, March 2018.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, March 2018. Management", RFC 8343, March 2018.
[RFC8344] M. Bjorklund, "A YANG Data Model for IP Management", [RFC8344] M. Bjorklund, "A YANG Data Model for IP Management",
RFC8344, March 2018. RFC8344, March 2018.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, March 2018. Routing Management (NMDA Version)", RFC 8349, March 2018.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, August 2018.
[RFC8519] M. Jethanandani, S. Agarwal, L. Huang and D. Blair, "YANG [RFC8519] M. Jethanandani, S. Agarwal, L. Huang and D. Blair, "YANG
Data Model for Network Access Control Lists (ACLs)", RFC Data Model for Network Access Control Lists (ACLs)", RFC
8519, March 2019. 8519, March 2019.
9.2. Informative References 9.2. Informative References
[RFC3569] Bhattacharyya, S., Ed., "An Overview of Source-Specific
Multicast (SSM)", RFC 3569, July 2003.
[RFC4541] M. Christensen, K. Kimball and F. Solensky, [RFC4541] M. Christensen, K. Kimball and F. Solensky,
"Considerations for Internet Group Management Protocol "Considerations for Internet Group Management Protocol
(IGMP) and Multicast Listener Discovery (MLD) Snooping (IGMP) and Multicast Listener Discovery (MLD) Snooping
Switches", RFC 4541, May 2006. Switches", RFC 4541, May 2006.
[RFC4605] B. Fenner, H. He, B. Haberman, and H. Sandick, "Internet [RFC4605] B. Fenner, H. He, B. Haberman, and H. Sandick, "Internet
Group Management Protocol (IGMP) / Multicast Listener Group Management Protocol (IGMP) / Multicast Listener
Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD
Proxying")", RFC 4605, August 2006. Proxying")", RFC 4605, August 2006.
[RFC5790] H. Liu, W. Cao and H. Asaeda, "Lightweight Internet Group [RFC5790] H. Liu, W. Cao and H. Asaeda, "Lightweight Internet Group
Management Protocol Version 3 (IGMPv3) and Multicast Management Protocol Version 3 (IGMPv3) and Multicast
Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790, Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790,
February 2010. February 2010.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, March 2018 BCP 215, RFC 8340, March 2018.
[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of [RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of
Documents Containing YANG Data Models", RFC 8407, October Documents Containing YANG Data Models", RFC 8407, October
2018. 2018.
[I-D.ietf-netconf-subscribed-notifications]
Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and
A. Tripathy, "Customized Subscriptions to a Publisher's
Event Streams", draft-ietf-netconf-subscribed-
notifications-26 (work in progress), May 2019.
[I-D.ietf-netconf-yang-push]
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 Technologies
Huawei Bldg., No.156 Beiqing Rd. Huawei Bldg., No.156 Beiqing Rd.
 End of changes. 67 change blocks. 
88 lines changed or deleted 111 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/