Ericsson (China) Communications Company Ltd.

Ericsson Tower, No. 5 Lize East Street Beijing 100102 China hongji.zhao@ericsson.com

Alef Edge

United States of America xufeng.liu.ietf@gmail.com

China Mobile

China liuyisong@chinamobile.com

Cisco Systems, Inc.

3625 Cisco Way San Jose CA United States of America mapancha@cisco.com

Juniper Networks

1133 Innovation Way Sunnyvale CA United States of America sivakumar.mahesh@gmail.com

rtg pim IGMP Proxy MLD Proxy YANG 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) Proxy devices. The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA).

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
  • .  Terminology
  • .  Tree Diagrams
  • .  Prefixes in Data Node Names
• .  Design of Data Model
  • .  Overview
  • .  Optional Features
  • .  Position of Address Family in Hierarchy
• .  Module Structure
  • .  IGMP Proxy Configuration and Operational State
  • .  MLD Proxy Configuration and Operational State
• .  IGMP/MLD Proxy YANG Module
• .  Security Considerations
• .  IANA Considerations
  • .  IETF XML Registry
  • .  YANG Module Names Registry
• .  References
  • .  Normative References
  • .  Informative References
• .  Data Tree Example
• Authors' Addresses

Introduction This document defines a YANG data model for the management of Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) Proxy devices . The YANG module in this document conforms to the Network Management Datastore Architecture as defined in .

Terminology The terminology for describing YANG data models is found in and , including:

• augment
• data model
• data node
• identity
• module

The following abbreviations are used in this document and in the defined YANG data model:

IGMP:

Internet Group Management Protocol .

MLD:

Multicast Listener Discovery .

PIM:

Protocol Independent Multicast .

Tree Diagrams Tree diagrams used in this document follow the notation defined in .

Prefixes in Data Node Names In this document, names of data nodes and other data model objects are often used without a prefix, as long as the context clearly 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 in . Prefixes and Corresponding YANG Modules

Prefix	YANG Module	Reference
inet	ietf-inet-types
if	ietf-interfaces
rt	ietf-routing
rt-types	ietf-routing-types
pim-base	ietf-pim-base

Design of Data Model The model covers forwarding based on IGMP and MLD proxying . One goal of this document is to define a data model that provides a common user interface for IGMP/MLD Proxy devices.

Overview The model defined in this document has all the common building blocks for IGMP/MLD Proxy devices and can be used to configure those devices. The operational state data and statistics can also be retrieved via this model.

Optional Features This model is designed to represent the basic capability subsets of IGMP/MLD Proxies. The main design goals of this document are that (1) the basic capabilities described in the model will be supported by any major implementations that exist at the time of this writing and (2) the configuration of all implementations meeting the specifications will be easy to express through some combination of the optional features in the model and simple vendor augmentations. This model declares two features representing capabilities that not all deployed devices support. One feature is called "igmp-proxy", and the other feature is called "mld-proxy". Either or both features could be implemented; this would provide more choices for vendors.

Position of Address Family in Hierarchy IGMP Proxies only support IPv4, while MLD Proxies only support IPv6. The data model defined in this document can be used for both IPv4 and IPv6 address families. This document defines IGMP Proxies and MLD Proxies in separate schema branches in the structure. The benefits of this technique are as follows:

• The model can support IGMP Proxies (IPv4), MLD Proxies (IPv6), or both, optionally and independently. Such flexibility cannot be achieved cleanly with a combined branch.
• The structure is consistent with other YANG data models such as the model defined in , which uses separate branches for IPv4 and IPv6.
• Having separate branches for IGMP Proxies and MLD Proxies allows minor differences in their behavior to be modeled more simply and cleanly. The two branches can better support different features and node types.

Module Structure This model augments the core routing data model specified in . +--rw routing +--rw router-id? +--rw control-plane-protocols | +--rw control-plane-protocol* [type name] | +--rw type | +--rw name | +--rw igmp-proxy <= Augmented by this model ... | +--rw mld-proxy <= Augmented by this model The "igmp-proxy" container instantiates an IGMP Proxy. The "mld-proxy" container instantiates an MLD Proxy.

IGMP Proxy Configuration and Operational State The YANG module augments /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol to add the igmp-proxy container. All attributes 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. The igmp-version parameter represents the IGMP protocol version; the default value is 2. If the value of the "enabled" parameter is "true", it means that the IGMP Proxy is enabled. The interface list under igmp-proxy contains upstream interfaces for an IGMP Proxy. A constraint is provided to make sure that the upstream interface for the IGMP Proxy is not configured to use PIM. To configure a downstream interface for an IGMP Proxy, the ability to enable IGMP on that interface is needed. This is defined in "" . 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

MLD Proxy Configuration and Operational State The YANG module augments /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol to add the mld-proxy container. All attributes 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. The mld-version parameter represents the MLD protocol version; the default value is 2. If the value of the "enabled" parameter is "true", it means that the MLD Proxy is enabled. The interface list under mld-proxy contains upstream interfaces for an MLD Proxy. A constraint is provided to make sure that the upstream interface for the MLD Proxy is not configured to use PIM. To configure a downstream interface for an MLD Proxy, enable MLD on that interface. This is defined in "" . 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

IGMP/MLD Proxy YANG Module This module references , , , , , and . module ietf-igmp-mld-proxy { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy"; prefix 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: YANG Data Model for Protocol Independent Multicast (PIM)"; } organization "IETF PIM Working Group"; contact "WG Web: <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>"; description "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) 2023 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 (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 9398; see the RFC itself for full legal notices."; revision 2023-05-30 { description "Initial revision."; reference "RFC 9398: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy Devices"; } /* * Features */ feature igmp-proxy { description "Support for the IGMP Proxy protocol."; reference "RFC 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 "RFC 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 Proxy protocol."; } identity mld-proxy { base rt:control-plane-protocol; description "MLD Proxy protocol."; } /* * Groupings */ grouping per-interface-config-attributes { description "'config' attributes as listed under an interface entry."; leaf enabled { type boolean; default "true"; description "Set the value to 'true' to enable the IGMP/MLD Proxy."; } } // per-interface-config-attributes grouping state-group-attributes { description "State group attributes."; leaf up-time { type uint32; units "seconds"; description "The elapsed time for (S,G) or (*,G)."; } leaf filter-mode { type enumeration { enum include { description "In 'include' mode, reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in the 'source' list parameter."; } enum exclude { description "In 'exclude' mode, reception of packets sent to the given multicast address is requested from all IP source addresses except those listed in the 'source' list parameter."; } } mandatory true; description "Filter mode for a multicast group. May be either 'include' or 'exclude'."; } } // state-group-attributes /* augments */ augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol" { when "derived-from-or-self(rt:type, " + "'igmp-mld-proxy:igmp-proxy')" { description "This augmentation is only valid for IGMP 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 "Contains a list of upstream interfaces."; list interface { key "name"; description "List of upstream interfaces."; leaf name { type if:interface-ref; must 'not( current() = /rt:routing' + '/rt:control-plane-protocols/pim-base:pim' + '/pim-base:interfaces/pim-base:interface' + '/pim-base:name )' { description "The upstream interface for the IGMP Proxy must not be configured to use PIM."; } description "The upstream interface name."; } leaf igmp-version { type uint8 { range "1..3"; } default "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 "List of the multicast groups in the membership database built on this 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 "Multicast source information for the multicast group."; leaf source-address { type inet:ipv4-address-no-zone; description "Multicast source address."; } leaf up-time { type uint32; units "seconds"; description "The elapsed time for (S,G) or (*,G)."; } list downstream-interface { key "name"; description "List of downstream interfaces."; leaf name { type if:interface-ref; description "Downstream interfaces for each upstream interface."; } } } // list source } // list group } // interface } // interfaces } } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol" { when "derived-from-or-self(rt:type, " + "'igmp-mld-proxy:mld-proxy')" { description "This augmentation is only valid for MLD 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 "Contains a list of upstream interfaces."; list interface { key "name"; description "List of upstream interfaces."; leaf name { type if:interface-ref; must 'not( current() = /rt:routing' + '/rt:control-plane-protocols/pim-base:pim' + '/pim-base:interfaces/pim-base:interface' + '/pim-base:name )' { description "The upstream interface for the MLD Proxy must not be configured to use PIM."; } description "The upstream interface name."; } leaf mld-version { type uint8 { range "1..2"; } default "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 "List of the multicast groups in the membership database built on this 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 "Multicast source information for the multicast group."; leaf source-address { type inet:ipv6-address-no-zone; description "Multicast source address."; } leaf up-time { type uint32; units "seconds"; description "The elapsed time for (S,G) or (*,G)."; } list downstream-interface { key "name"; description "List of downstream interfaces."; leaf name { type if:interface-ref; description "Downstream interfaces for each upstream interface."; } } } // list source } // list group } // interface } // interfaces } } }

Security Considerations 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 or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/ igmp-mld-proxy:igmp-proxy:

igmp-mld-proxy:interfaces

This subtree specifies the interface list for an IGMP Proxy. Modifying the configuration may cause the IGMP Proxy interface to be deleted or changed.

igmp-mld-proxy:interfaces/interface

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 specific interface.

Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/ igmp-mld-proxy:mld-proxy:

igmp-mld-proxy:interfaces

This subtree specifies the interface list for an MLD Proxy. Modifying the configuration may cause the MLD Proxy interface to be deleted or changed.

igmp-mld-proxy:interfaces/interface

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 specific interface.

Unauthorized access to any data nodes in these subtrees can adversely affect the IGMP/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. 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: Under /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:/ igmp-mld-proxy:igmp-proxy igmp-mld-proxy:mld-proxy Unauthorized access to any data nodes in these subtrees can disclose operational state information about the IGMP/MLD Proxy on this device. Group information or source information may expose multicast group memberships.

IANA Considerations

IETF XML Registry This document registers the following namespace URIs in the "IETF XML Registry" :

URI:

urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy

Registrant Contact:

The IESG.

XML:

N/A; the requested URI is an XML namespace.

YANG Module Names Registry This document registers the following YANG module in the "YANG Module Names" registry :

Name:

ietf-igmp-mld-proxy

Namespace:

urn:ietf:params:xml:ns:yang:ietf-igmp-mld-proxy

Prefix:

igmp-mld-proxy

Reference:

RFC 9398

References Normative References This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. This document updates RFC 2710, and it specifies Version 2 of the ulticast Listener Discovery Protocol (MLDv2). MLD is used by an IPv6 router to discover the presence of multicast listeners on directly attached links, and to discover which multicast addresses are of interest to those neighboring nodes. MLDv2 is designed to be interoperable with MLDv1. MLDv2 adds the ability for a node to report interest in listening to packets with a particular multicast address only from specific source addresses or from all sources except for specific source addresses. [STANDARDS-TRACK] In certain topologies, it is not necessary to run a multicast routing protocol. It is sufficient for a device to learn and proxy group membership information and simply forward multicast packets based upon that information. This document describes a mechanism for forwarding based solely upon Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) membership information. [STANDARDS-TRACK] YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics). The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342. This document obsoletes RFC 7223. This document specifies three YANG modules and one submodule. Together, they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). This document obsoletes RFC 8022. This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) devices. This document defines a YANG data model that can be used to configure and manage devices supporting Protocol Independent Multicast (PIM). The model covers the PIM protocol configuration, operational state, and event notifications data. Informative References This document specifies Protocol Independent Multicast - Sparse Mode (PIM-SM). PIM-SM is a multicast routing protocol that can use the underlying unicast routing information base or a separate multicast-capable routing information base. It builds unidirectional shared trees rooted at a Rendezvous Point (RP) per group, and it optionally creates shortest-path trees per source. This document obsoletes RFC 4601 by replacing it, addresses the errata filed against it, removes the optional (*,*,RP), PIM Multicast Border Router features and authentication using IPsec that lack sufficient deployment experience (see Appendix A), and moves the PIM specification to Internet Standard. This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.

Data Tree Example This section contains an example for the IGMP Proxy, shown in JSON encoding and containing both configuration and state data. In the example, the IGMP Proxy is enabled on interface eth1/1. The ability to enable IGMP on eth1/2 and eth1/3 is also needed. The configuration details are omitted here because this document is focused on IGMP/MLD Proxies. +-----------+ + Source + +-----+-----+ | -----------------+---------------------------- |eth1/1 +---+----+ + R1 + +-+----+-+ eth1/2 | \ eth1/3 | \ | \ | \ ---------------+---------+-------------------- | \ | \ +---------+--+ +---+--------+ + Receiver 1 + + Receiver 2 + +------------+ +------------+ The configuration data for R1 in the above figure could be as follows: { "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 } ] } } } ] } } } The corresponding operational state data for R1 could be as follows: { "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" } ] } ] } ] } ] } } } ] } } }

Authors' Addresses Ericsson (China) Communications Company Ltd.

Ericsson Tower, No. 5 Lize East Street Beijing 100102 China hongji.zhao@ericsson.com

Alef Edge

United States of America xufeng.liu.ietf@gmail.com

China Mobile

China liuyisong@chinamobile.com

Cisco Systems, Inc.

3625 Cisco Way San Jose CA United States of America mapancha@cisco.com

Juniper Networks

1133 Innovation Way Sunnyvale CA United States of America sivakumar.mahesh@gmail.com