<?xmlversion='1.0' encoding='utf-8'?>version="1.0" encoding="UTF-8"?> <!-- [CS] updated by Chris 01/19/23 --> <!DOCTYPE rfcSYSTEM "rfc2629.dtd"[ <!ENTITYRFC3376 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3376.xml"> <!ENTITY RFC3688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"> <!ENTITY RFC3810 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3810.xml"> <!ENTITY RFC4605 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4605.xml"> <!ENTITY RFC6020 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"> <!ENTITY RFC6241 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"> <!ENTITY RFC6242 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"> <!ENTITY RFC6991 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"> <!ENTITY RFC7950 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"> <!ENTITY RFC8040 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"> <!ENTITY RFC8294 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8294.xml"> <!ENTITY RFC8341 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"> <!ENTITY RFC8342 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"> <!ENTITY RFC8343 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"> <!ENTITY RFC8349 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"> <!ENTITY RFC8446 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml">nbsp " "> <!ENTITYRFC8652 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8652.xml">zwsp "​"> <!ENTITYRFC9128 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9128.xml">nbhy "‑"> <!ENTITYRFC7761 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7761.xml"> <!ENTITY RFC7951 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml"> <!ENTITY RFC8340 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"> <!ENTITY RFC8407 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml">wj "⁠"> ]> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF"docName="draft-ietf-pim-igmp-mld-proxy-yang-10"category="std"ipr="trust200902">consensus="true" docName="draft-ietf-pim-igmp-mld-proxy-yang-10" number="9398" ipr="trust200902" obsoletes="" updates="" xml:lang="en" symRefs="true" sortRefs="true" tocInclude="true" version="3"> <!-- xml2rfc v2v3 conversion 3.15.3 --> <!-- Generated by id2xml 1.5.0 on 2023-01-18T23:48:39Z --><?rfc strict="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?> <?rfc symrefs="yes"?> <?rfc sortrefs="no"?> <?rfc text-list-symbols="**o+-"?> <?rfc toc="yes"?><front><title>A<title abbrev="IGMP/MLD Proxy YANG Module">A YANG Data Model forIGMP/MLD Proxy</title>Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy Devices</title> <seriesInfo name="RFC" value="9398"/> <author initials="H." surname="Zhao" fullname="Hongji Zhao"> <organization abbrev="Ericsson">Ericsson (China) Communications Company Ltd.</organization><address><postal><address> <postal> <street>EricssonTower</street> <street>No.Tower, No. 5 Lize East Street</street><city>ChaoYANG District Beijing</city><city>Beijing</city> <code>100102</code> <country>China</country> </postal> <email>hongji.zhao@ericsson.com</email> </address> </author> <author initials="X." surname="Liu" fullname="Xufeng Liu"><organization>IBM Corporation</organization> <address><postal> <street>2300 Dulles Station Blvd.</street> <city>Herndon</city> <region>VA</region> <code>20171</code><organization>Alef Edge</organization> <address> <postal> <street></street> <city></city> <region></region> <code></code> <country>United States of America</country> </postal><email>Xufeng.liu.ietf@gmail.com</email><email>xufeng.liu.ietf@gmail.com</email> </address> </author> <author initials="Y." surname="Liu" fullname="Yisong Liu"> <organization>China Mobile</organization><address><postal> <street></street> <city></city> <region></region> <code></code><address> <postal> <street/> <city/> <region/> <code/> <country>China</country> </postal> <email>liuyisong@chinamobile.com</email> </address> </author> <author initials="M." surname="Panchanathan" fullname="Mani Panchanathan"> <organization>CiscoSystems</organization> <address><postal> <street></street> <city></city> <region></region> <code></code> <country>India</country>Systems, Inc.</organization> <address> <postal> <street>3625 Cisco Way</street> <city>San Jose</city> <region>CA</region> <code/> <country>United States of America</country> </postal> <email>mapancha@cisco.com</email> </address> </author> <author initials="M." surname="Sivakumar" fullname="Mahesh Sivakumar"> <organization abbrev="Juniper">Juniper Networks</organization><address><postal><address> <postal> <street>1133 Innovation Way</street> <city>Sunnyvale</city><region>California</region> <country>USA</country><region>CA</region> <country>United States of America</country> </postal> <email>sivakumar.mahesh@gmail.com</email> </address> </author> <date year="2023"month="January"/>month="May"/> <area>rtg</area> <workgroup>pim</workgroup><!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> <keyword>example</keyword><keyword>IGMP Proxy</keyword> <keyword>MLD Proxy</keyword> <keyword>YANG</keyword> <abstract> <t>This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD)proxyProxy devices. The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA).</t> </abstract> </front> <middle> <sectiontitle="Introduction" anchor="sect-1"><t>anchor="sect-1" numbered="true" toc="default"> <name>Introduction</name> <t> This document defines a YANG<xref target="RFC7950"/>data model <xref target="RFC7950" format="default"/> for the management of Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) Proxy devices <xreftarget="RFC4605"/> devices.target="RFC4605" format="default"/>. The YANG module in this document conforms to the Network Management Datastore Architecture as defined in <xreftarget="RFC8342"/>.</t>target="RFC8342" format="default"/>.</t> <sectiontitle="Terminology" anchor="sect-1.1"><t>anchor="sect-1.1" numbered="true" toc="default"> <name>Terminology</name> <t> The terminology for describing YANG data models is found in <xreftarget="RFC6020"/>target="RFC6020" format="default"/> and <xreftarget="RFC7950"/>,target="RFC7950" format="default"/>, including:<list style="symbols"> <t>augment</t> <t>data model</t> <t>data node</t> <t>identity</t> <t>module</t> </list></t></t> <ul spacing="normal"> <li>augment</li> <li>data model</li> <li>data node</li> <li>identity</li> <li>module</li> </ul> <t>The following abbreviations are used in this document and in the defined YANG data model:<list> <t>IGMP: Internet</t> <dl spacing="normal"> <dt>IGMP:</dt><dd>Internet Group Management Protocol <xreftarget="RFC3376"/>.</t> <t>MLD: Multicasttarget="RFC3376" format="default"/>.</dd> <dt>MLD:</dt><dd>Multicast Listener Discovery <xreftarget="RFC3810"/>.</t> <t>PIM: Protocoltarget="RFC3810" format="default"/>.</dd> <dt>PIM:</dt><dd>Protocol Independent Multicast <xreftarget="RFC7761"/>.</t> </list></t>target="RFC7761" format="default"/>.</dd> </dl> </section> <sectiontitle="Tree Diagrams" anchor="sect-1.2"><t>anchor="sect-1.2" numbered="true" toc="default"> <name>Tree Diagrams</name> <t> Tree diagrams used in this document follow the notation defined in <xreftarget="RFC8340"/>.</t>target="RFC8340" format="default"/>.</t> </section> <sectiontitle="Prefixesanchor="sect-1.3" numbered="true" toc="default"> <name>Prefixes in Data NodeNames" anchor="sect-1.3"><t>Names</name> <t> In this document, names of datanodes,nodes and other data model objects are often used without a prefix, as long asit is clear fromthe contextin whichclearly indicates the YANG module in which each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown inTable 1.</t> <!-- Please review id2xml Warning: Unexpected title: expected 'Figure ...', found 'Table 1: Prefixes and Corresponding YANG Modules'. This looks like a figure that has been entered as a texttable. The generated XML will need adjustment. --> <figure title="Prefixes<xref target="tab-1"/>.</t> <table anchor="tab-1"> <name>Prefixes and Corresponding YANGModules" anchor="fig1"><artwork><![CDATA[ +----------+-----------------------+--------------------------------+ | Prefix | YANG module | Reference | +==========+=======================+================================+ | inet | ietf-inet-types | [RFC6991] | +----------+-----------------------+--------------------------------+ | if | ietf-interfaces | [RFC8343] | +----------+-----------------------+--------------------------------+ | rt | ietf-routing | [RFC8349] | +----------+-----------------------+--------------------------------+ | rt-types | ietf-routing-types | [RFC8294] | +----------+-----------------------+--------------------------------+ | pim-base | ietf-pim-base | [RFC9128] | +----------+-----------------------+--------------------------------+ ]]></artwork> </figure>Modules</name> <thead> <tr> <th>Prefix</th> <th>YANG Module</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td>inet</td> <td>ietf-inet-types</td> <td><xref target="RFC6991"/></td> </tr> <tr> <td>if</td> <td>ietf-interfaces</td> <td><xref target="RFC8343"/></td> </tr> <tr> <td>rt</td> <td>ietf-routing</td> <td><xref target="RFC8349"/></td> </tr> <tr> <td>rt-types</td> <td>ietf-routing-types</td> <td><xref target="RFC8294"/></td> </tr> <tr> <td>pim-base</td> <td>ietf-pim-base</td> <td><xref target="RFC9128"/></td> </tr> </tbody> </table> </section> </section> <sectiontitle="Designanchor="sect-2" numbered="true" toc="default"> <name>Design of DataModel" anchor="sect-2"><t>Model</name> <t> The model coversInternet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD) - Based Multicast Forwarding ("IGMP/MLD Proxying")forwarding based on IGMP and MLD proxying <xreftarget="RFC4605"/>. Thetarget="RFC4605" format="default"/>. One goal of this document is to define a data model that provides a common user interfacetofor IGMP/MLDProxy.</t>Proxy devices.</t> <sectiontitle="Overview" anchor="sect-2.1"><t>anchor="sect-2.1" numbered="true" toc="default"> <name>Overview</name> <t> The model defined in this document has all the common building blocks fortheIGMP/MLD Proxydevices. Itdevices and can be used to configureIGMP/MLD Proxy.those devices. The operational state data and statistics can also be retrievedby it.</t>via this model.</t> </section> <sectiontitle="Optional Features" anchor="sect-2.2"><t>anchor="sect-2.2" numbered="true" toc="default"> <name>Optional Features</name> <t> This model is designed to represent the basic capability subsets of IGMP/MLDProxy.Proxies. The main design goals of this document are that (1) the basic capabilities described in the modelarewill be supported by any majornow-existing implementation, andimplementations that exist at the time of this writing and (2) the configuration of all implementations meeting the specificationsiswill be easy to express through some combination of the optional features in the model and simple vendor augmentations.</t> <t> This model declares two features representing capabilities that not all deployed devices support. One feature isigmp-proxy,called "igmp-proxy", and the other feature ismld-proxy.called "mld-proxy". Either or both features could beimplemented, which couldimplemented; this would provide more choices for vendors.</t> </section> <sectiontitle="Positionanchor="sect-2.3" numbered="true" toc="default"> <name>Position of Address Family inHierarchy" anchor="sect-2.3"><t>Hierarchy</name> <t> IGMPProxyProxies onlysupportssupport IPv4, while MLDProxyProxies onlysupportssupport IPv6. The data model defined in this document can be used for both IPv4 and IPv6 address families.</t> <t> This document defines IGMPProxyProxies and MLDProxy asProxies in separate schema branches in the structure. The benefitsare: <list style="symbols"> <t>Theof this technique are as follows: </t> <ul spacing="normal"> <li>The model can support IGMPProxyProxies (IPv4), MLDProxyProxies (IPv6), orbothboth, optionally and independently. Such flexibility cannot be achieved cleanly with a combinedbranch.</t> <t>Thebranch.</li> <li>The structure is consistent with other YANG data models such as the model defined in <xreftarget="RFC8652"/>,target="RFC8652" format="default"/>, which uses separate branches for IPv4 andIPv6.</t> <t>HavingIPv6.</li> <li>Having separate branches for IGMPProxyProxies and MLDProxyProxies allows minor differences in their behavior to bemodelledmodeled more simply and cleanly. The two branches can better support different features and nodetypes.</t> </list></t>types.</li> </ul> </section> </section> <sectiontitle="Module Structure" anchor="sect-3"><t>Thisanchor="sect-3" numbered="true" toc="default"> <name>Module Structure</name> <t>This model augments the core routing data model specified in[RFC8349].</t> <figure><artwork><![CDATA[<xref target="RFC8349"/>.</t> <sourcecode name="" type="yangtree"><![CDATA[ +--rw routing +--rw router-id? +--rw control-plane-protocols | +--rw control-plane-protocol* [type name] | +--rw type | +--rw name | +--rw igmp-proxy <= Augmented by thisModelmodel ... | +--rw mld-proxy <= Augmented by thisModel ]]></artwork> </figure>model ]]></sourcecode> <t> The "igmp-proxy" container instantiates an IGMP Proxy. The "mld-proxy" container instantiates an MLD Proxy.</t> <sectiontitle="IGMPanchor="sect-3.1" numbered="true" toc="default"> <name>IGMP Proxy Configuration and OperationalState" anchor="sect-3.1"><t>State</name> <t> The YANG module augments /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol to add the igmp-proxy container.</t> <t> Allthe IGMP Proxy relatedattributes related to IGMP Proxies are defined in the igmp-proxy container. The read-write attributes represent configurable data. The read-only attributes represent state data.</t> <t> The igmp-version parameter represents theversion ofIGMPprotocol, andprotocol version; the default value is 2. If the value ofenabledthe "enabled" parameter istrue,"true", it means that the IGMP Proxy is enabled.</t> <t> The interface list under igmp-proxy contains upstream interfaces for an IGMPproxy. There is also aProxy. A constraint is provided to make sure that the upstream interface for the IGMPproxyProxy is not configured to use PIM.</t> <t> To configure a downstream interface for an IGMPproxy, it is neededProxy, the ability to enable IGMP on thatinterface.interface is needed. This is defined inthe YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) <xref target="RFC8652"/>.</t> <figure><artwork><![CDATA["<xref target="RFC8652" format="title"/>" <xref target="RFC8652" format="default"/>.</t> <sourcecode name="" type="yangtree"><![CDATA[ augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol: +--rw igmp-proxy! {igmp-proxy}? +--rw interfaces +--rw interface* [name] +--rw name if:interface-ref +--rw igmp-version? uint8 +--rw enabled? boolean +--rw sender-source-address? inet:ipv4-address-no-zone +--ro group* [group-address] +--ro group-address | rt-types:ipv4-multicast-group-address +--ro up-time? uint32 +--ro filter-mode enumeration +--ro source* [source-address] +--ro source-address | inet:ipv4-address-no-zone +--ro up-time? uint32 +--ro downstream-interface* [name] +--ro name if:interface-ref]]></artwork> </figure>]]></sourcecode> </section> <sectiontitle="MLDanchor="sect-3.2" numbered="true" toc="default"> <name>MLD Proxy Configuration and OperationalState" anchor="sect-3.2"><t>State</name> <t> The YANG module augments /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol to add the mld-proxy container.</t> <t> Allthe MLD Proxy relatedattributes related to MLD Proxies are defined in the mld-proxy container. The read-write attributes represent configurable data. The read-only attributes represent state data.</t> <t> The mld-version parameter represents theversion ofMLDprotocol, andprotocol version; the default value is 2. If the value ofenabledthe "enabled" parameter istrue,"true", it means that the MLD Proxy is enabled.</t> <t> The interface list under mld-proxy contains upstream interfaces for an MLDproxy. There is also aProxy. A constraint is provided to make sure that the upstream interface for the MLDproxyProxy is not configured to use PIM.</t> <t> To configure a downstream interface for an MLDproxy,Proxy, enable MLD on that interface. This is defined inthe YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) <xref target="RFC8652"/>.</t> <figure><artwork><![CDATA["<xref target="RFC8652" format="title"/>" <xref target="RFC8652" format="default"/>.</t> <sourcecode name="" type="yangtree"><![CDATA[ augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol: +--rw mld-proxy! {mld-proxy}? +--rw interfaces +--rw interface* [name] +--rw name if:interface-ref +--rw mld-version? uint8 +--rw enabled? boolean +--rw sender-source-address? inet:ipv6-address-no-zone +--ro group* [group-address] +--ro group-address | rt-types:ipv6-multicast-group-address +--ro up-time? uint32 +--ro filter-mode enumeration +--ro source* [source-address] +--ro source-address | inet:ipv6-address-no-zone +--ro up-time? uint32 +--ro downstream-interface* [name] +--ro name if:interface-ref]]></artwork> </figure>]]></sourcecode> </section> </section> <sectiontitle="IGMP/MLDanchor="sect-4" numbered="true" toc="default"> <name>IGMP/MLD Proxy YANGModule" anchor="sect-4"><t>Module</name> <t> This module references <xreftarget="RFC4605"/>,target="RFC4605" format="default"/>, <xreftarget="RFC6991"/>,target="RFC6991" format="default"/>, <xreftarget="RFC8294"/>,target="RFC8294" format="default"/>, <xreftarget="RFC8343"/>,target="RFC8343" format="default"/>, <xreftarget="RFC8349"/>target="RFC8349" format="default"/>, and <xreftarget="RFC9128"/>.</t> <figure><artwork><![CDATA[ <CODE BEGINS> file ietf-igmp-mld-proxy@2022-12-07.yangtarget="RFC9128" format="default"/>.</t> <sourcecode name="ietf-igmp-mld-proxy@2023-04-25.yang" type="yang" markers="true"><![CDATA[ module ietf-igmp-mld-proxy { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy";// replace with IANA namespace when assignedprefix igmp-mld-proxy; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-interfaces { prefix if; reference "RFC 8343: A YANG Data Model for Interface Management"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-pim-base { prefix pim-base; reference "RFC 9128:AYANG Data Model for Protocol Independent Multicast (PIM)"; } organization "IETF PIM Working Group"; contact "WG Web:<https://datatracker.ietf.org/wg/pim/about/><https://datatracker.ietf.org/wg/pim/> WG List: <mailto:pim@ietf.org> Editors: Hongji Zhao <mailto:hongji.zhao@ericsson.com> Xufeng Liu <mailto:xufeng.liu.ietf@gmail.com> Yisong Liu <mailto:liuyisong@chinamobile.com> Mani Panchanathan <mailto:mapancha@cisco.com> Mahesh Sivakumar<mailto:sivakumar.mahesh@gmail.com> ";<mailto:sivakumar.mahesh@gmail.com>"; description"The"This module defines a collection of YANG definitions common for all Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy devices. Copyright (c)20222023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents(http://trustee.ietf.org/license-info).(https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCXXXX;9398; see the RFC itself for full legal notices."; revision2022-12-072023-04-25 { description "Initial revision."; reference "RFCXXXX:9398: A YANG Data Model forIGMPInternet Group Management Protocol (IGMP) andMLD Proxy";Multicast Listener Discovery (MLD) Proxy Devices"; } /* * Features */ feature igmp-proxy { description "Support for the IGMP Proxy protocol."; reference "RFC4605";4605: Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ('IGMP/MLD Proxying')"; } feature mld-proxy { description "Support for the MLD Proxy protocol."; reference "RFC4605";4605: Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ('IGMP/MLD Proxying')"; } /* * Identities */ identity igmp-proxy { base rt:control-plane-protocol; description "IGMP Proxyprotocol";protocol."; } identity mld-proxy { base rt:control-plane-protocol; description "MLD Proxyprotocol";protocol."; } /* * Groupings */ grouping per-interface-config-attributes { description"Config"'config' attributes as listed under an interfaceview";entry."; leaf enabled { type boolean; defaulttrue;"true"; description "Set the value totrue'true' to enable the IGMP/MLDproxy";Proxy."; } } // per-interface-config-attributes grouping state-group-attributes { description "State groupattributes";attributes."; leaf up-time { type uint32; unitsseconds;"seconds"; description "The elapsed time for (S,G) or (*,G)."; } leaf filter-mode { type enumeration { enum"include"include { description "Ininclude'include' mode, reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in thesource-list parameter";'source' list parameter."; } enum"exclude"exclude { description "Inexclude'exclude' mode, reception of packets sent to the given multicast address is requested from all IP source addresses except those listed in thesource-list'source' list parameter."; } } mandatory true; description "Filter mode for a multicastgroup, maygroup. May be eitherinclude'include' orexclude.";'exclude'."; } } // state-group-attributes /* augments */ augment"/rt:routing/rt:control-plane-protocols"+"/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol" { when "derived-from-or-self(rt:type,'igmp-mld-proxy:igmp-proxy')"" + "'igmp-mld-proxy:igmp-proxy')" { description "This augmentation is only valid for IGMPProxy.";Proxies."; } description "IGMP Proxy augmentation to routing control plane protocol configuration and state."; container igmp-proxy { if-feature "igmp-proxy"; presence "IGMP Proxy configuration."; description "IGMP Proxy instance configuration."; container interfaces { description"Containing"Contains a list of upstream interfaces."; list interface { key "name"; description "List of upstream interfaces."; leaf name { type if:interface-ref; must"not('not( current() =/rt:routing"+ "/rt:control-plane-protocols/pim-base:pim"+ "/pim-base:interfaces/pim-base:interface"+ "/pim-base:name )"/rt:routing' + '/rt:control-plane-protocols/pim-base:pim' + '/pim-base:interfaces/pim-base:interface' + '/pim-base:name )' { description "The upstream interface for the IGMPproxyProxy must not be configured to use PIM."; } description "The upstream interface name."; } leaf igmp-version { type uint8 { range "1..3"; } default2;"2"; description "IGMP version."; } uses per-interface-config-attributes; leaf sender-source-address { type inet:ipv4-address-no-zone; description "The sender source address of an IGMP membership report message or leave message."; } list group { key "group-address"; config false; description"Multicast group"List of the multicast groups in the membershipinformation that joineddatabase built onthethis upstream interface."; leaf group-address { type rt-types:ipv4-multicast-group-address; description "Multicast group address."; } uses state-group-attributes; list source { key "source-address"; description"List of multicast"Multicast source informationoffor the multicast group."; leaf source-address { type inet:ipv4-address-no-zone; description "Multicast sourceaddress";address."; } leaf up-time { type uint32; unitsseconds;"seconds"; description "The elapsed time for (S,G) or (*,G)."; } list downstream-interface { key "name"; description"The"List of downstreaminterfaces list.";interfaces."; leaf name { type if:interface-ref; description "Downstream interfaces for eachupstream-interface";upstream interface."; } } } // list source } // list group } // interface } // interfaces } } augment"/rt:routing/rt:control-plane-protocols"+"/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol" { when "derived-from-or-self(rt:type,'igmp-mld-proxy:mld-proxy')"" + "'igmp-mld-proxy:mld-proxy')" { description "This augmentation is only valid for MLDProxy.";Proxies."; } description "MLD Proxy augmentation to routing control plane protocol configuration and state."; container mld-proxy { if-feature "mld-proxy"; presence "MLD Proxy configuration."; description "MLD Proxy instance configuration."; container interfaces { description"Containing"Contains a list of upstream interfaces."; list interface { key "name"; description "List of upstream interfaces."; leaf name { type if:interface-ref; must"not('not( current() =/rt:routing"+ "/rt:control-plane-protocols/pim-base:pim"+ "/pim-base:interfaces/pim-base:interface"+ "/pim-base:name )"/rt:routing' + '/rt:control-plane-protocols/pim-base:pim' + '/pim-base:interfaces/pim-base:interface' + '/pim-base:name )' { description "The upstream interface for the MLDproxyProxy must not be configured to use PIM."; } description "The upstream interface name."; } leaf mld-version { type uint8 { range "1..2"; } default2;"2"; description "MLD version."; } uses per-interface-config-attributes; leaf sender-source-address { type inet:ipv6-address-no-zone; description "The sender source address of an MLD membership report message or leave message."; } list group { key "group-address"; config false; description"Multicast group"List of the multicast groups in the membershipinformation that joineddatabase built onthethis upstream interface."; leaf group-address { type rt-types:ipv6-multicast-group-address; description "Multicast group address."; } uses state-group-attributes; list source { key "source-address"; description"List of multicast"Multicast source informationoffor the multicast group."; leaf source-address { type inet:ipv6-address-no-zone; description "Multicast sourceaddress";address."; } leaf up-time { type uint32; unitsseconds;"seconds"; description "The elapsed time for (S,G) or (*,G)."; } list downstream-interface { key "name"; description"The"List of downstreaminterfaces list.";interfaces."; leaf name { type if:interface-ref; description "Downstream interfaces for eachupstream-interface";upstream interface."; } } } // list source } // list group } // interface } // interfaces } } }<CODE ENDS> ]]></artwork> </figure>]]></sourcecode> </section> <sectiontitle="Security Considerations" anchor="sect-5"><t> Theanchor="sect-5" numbered="true" toc="default"> <name>Security Considerations</name> <t>The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF <xref target="RFC6241"/> or RESTCONF <xref target="RFC8040"/>. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <xref target="RFC6242"/>. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <xref target="RFC8446"/>.</t><t> The<t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.</t><t> There<t>There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability:</t> <t>Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/igmp-mld-proxy:igmp-proxy,</t> <t>igmp-mld-proxy:interfaces <list> <t>Thisigmp-mld-proxy:igmp-proxy:</t> <dl newline="true"> <dt>igmp-mld-proxy:interfaces</dt> <dd>This subtree specifies the interface list for an IGMP Proxy. Modifying the configuration may cause the IGMP Proxy interface to be deleted orchanged.</t> </list></t> <t>igmp-mld-proxy:interfaces/interface <list> <t>Thischanged.</dd> <dt>igmp-mld-proxy:interfaces/interface</dt> <dd>This subtree specifies the configuration for the IGMP Proxy attributes at the interface level. Modifying the configuration may cause the IGMP Proxy to be deleted or changed on a specificinterface.</t> </list></t>interface.</dd> </dl> <t>Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/igmp-mld-proxy:mld-proxy,</t> <t>igmp-mld-proxy:interfaces <list> <t>Thisigmp-mld-proxy:mld-proxy:</t> <dl newline="true"> <dt>igmp-mld-proxy:interfaces</dt> <dd>This subtree specifies the interface list for an MLD Proxy. Modifying the configuration may cause the MLD Proxy interface to be deleted orchanged.</t> </list></t> <t>igmp-mld-proxy:interfaces/interface <list> <t>Thischanged.</dd> <dt>igmp-mld-proxy:interfaces/interface</dt> <dd>This subtree specifies the configuration for the MLD Proxy attributes at the interface level. Modifying the configuration may cause the MLD Proxy to be deleted or changed on a specificinterface.</t> </list></t>interface.</dd> </dl> <t> Unauthorized access to any datanode ofnodes in these subtrees can adversely affect theIGMP / MLDIGMP/MLD Proxy subsystem of both the local device and the network. This may lead to network malfunctions, delivery of packets to inappropriate destinations, and other problems.</t><t> Some<t>Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:</t><figure><artwork><![CDATA[<artwork name="" type="" align="left" alt=""><![CDATA[ Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/ igmp-mld-proxy:igmp-proxy igmp-mld-proxy:mld-proxy ]]></artwork></figure><t> Unauthorized access to any datanode ofnodes in these subtrees can disclosetheoperational state informationof IGMP / MLDabout the IGMP/MLD Proxy on this device.The group/sourceGroup information or source information may expose multicast group memberships.</t> </section> <sectiontitle="IANA Considerations" anchor="sect-6"><t> RFC Ed.: In this section, replace all occurrences of 'XXXX' with the actual RFC number (and remove this note).</t>anchor="sect-6" numbered="true" toc="default"> <name>IANA Considerations</name> <sectiontitle="XML Registry" anchor="sect-6.1"><t>anchor="sect-6.1" numbered="true" toc="default"> <name>IETF XML Registry</name> <t> This document registers the following namespace URIs in theIETF"IETF XMLregistryRegistry" <xreftarget="RFC3688"/>:</t> <figure><artwork><![CDATA[ -------------------------------------------------------------------- URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy Registrant Contact: The IESG. XML: N/A,target="RFC3688" format="default"/>:</t> <dl spacing="compact"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace. -------------------------------------------------------------------- ]]></artwork> </figure>namespace.</dd> </dl> </section> <sectiontitle="YANGanchor="sect-6.2" numbered="true" toc="default"> <name>YANG Module NamesRegistry" anchor="sect-6.2">Registry</name> <t>This document registers the following YANGmodulesmodule in theYANG"YANG ModuleNamesNames" registry[RFC7950]:</t> <figure><artwork><![CDATA[ -------------------------------------------------------------------- name: ietf-igmp-mld-proxy namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy prefix: igmp-mld-proxy reference: RFC XXXX -------------------------------------------------------------------- ]]></artwork> </figure><xref target="RFC6020"/>:</t> <dl spacing="compact"> <dt>Name:</dt><dd>ietf-igmp-mld-proxy</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy</dd> <dt>Prefix:</dt><dd>igmp-mld-proxy</dd> <dt>Reference:</dt><dd>RFC 9398</dd> </dl> </section> </section> </middle> <back><references title="Normative References"> &RFC3376; &RFC3688; &RFC3810; &RFC4605; &RFC6020; &RFC6241; &RFC6242; &RFC6991; &RFC7950; &RFC8040; &RFC8294; &RFC8341; &RFC8342; &RFC8343; &RFC8349; &RFC8446; &RFC8652; &RFC9128;<references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3376.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3810.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4605.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8294.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8343.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8349.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8652.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9128.xml"/> </references> <references> <name>Informative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7761.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> </references><references title="Informative References"> &RFC7761; &RFC7951; &RFC8340; &RFC8407;</references> <sectiontitle="Dataanchor="sect-appendix" numbered="true" toc="default"> <name>Data TreeExample" anchor="sect-appendix"><t>Example</name> <t> This section contains an example for the IGMPProxyProxy, shown intheJSON encoding <xreftarget="RFC7951"/>,target="RFC7951" format="default"/> and containing both configuration and state data. In theexampleexample, the IGMP Proxy is enabled on interface eth1/1.</t> <t>It is also neededThe ability to enable IGMP on eth1/2 andeth1/3.eth1/3 is also needed. The configuration details are omitted here because this document is focused on IGMP/MLDProxy.</t> <figure><artwork><![CDATA[Proxies.</t> <artwork name="" type="" align="left" alt=""><![CDATA[ +-----------+ + Source + +-----+-----+ | -----------------+---------------------------- |eth1/1 +---+----+ + R1 + +-+----+-+ eth1/2 | \ eth1/3 | \ | \ | \---------------+---------+----------------------------------+---------+-------------------- | \ | \+--------+--++---------+--+ +---+--------+ +Receiver1Receiver 1 + +Receiver2Receiver 2 ++-----------++------------+ +------------+ ]]></artwork></figure><t>The configuration data for R1 in the above figure could be as follows:</t><figure><artwork><![CDATA[<sourcecode name="" type="json"><![CDATA[ { "ietf-interfaces:interfaces": { "interface": [ { "name": "eth1/1", "type": "iana-if-type:ipForward", "ietf-ip:ipv4": { "address": [ { "ip": "203.0.113.1", "prefix-length": 24 } ] } } ] }, "ietf-routing:routing": { "control-plane-protocols": { "control-plane-protocol": [ { "type": "ietf-igmp-mld-proxy:igmp-proxy", "name": "proxy1", "ietf-igmp-mld-proxy:igmp-proxy": { "interfaces": { "interface": [ { "name": "eth1/1", "igmp-version": 3, "enabled": true } ] } } } ] } } }]]></artwork> </figure>]]></sourcecode> <t>The corresponding operational state data for R1 could be as follows:</t><figure><artwork><![CDATA[<sourcecode name="" type="json"><![CDATA[ { "ietf-interfaces:interfaces": { "interface": [ { "name": "eth1/1", "type": "iana-if-type:ipForward", "admin-status": "up", "oper-status": "up", "if-index": 25678136, "statistics": { "discontinuity-time": "2021-05-23T10:34:56-06:00" }, "ietf-ip:ipv4": { "address": [ { "ip": "203.0.113.1", "prefix-length": 24 } ] } } ] }, "ietf-routing:routing": { "control-plane-protocols": { "control-plane-protocol": [ { "type": "ietf-igmp-mld-proxy:igmp-proxy", "name": "proxy1", "ietf-igmp-mld-proxy:igmp-proxy": { "interfaces": { "interface": [ { "name": "eth1/1", "igmp-version": 3, "enabled": true, "group": [ { "group-address": "233.252.0.23", "filter-mode": "include", "source": [ { "source-address": "192.0.2.1", "downstream-interface": [ { "name": "eth1/2" }, { "name": "eth1/3" } ] } ] } ] } ] } } } ] } } }]]></artwork> </figure>]]></sourcecode> </section> </back> </rfc>