[pim] RFC 9166 on A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping
rfc-editor@rfc-editor.org Tue, 01 February 2022 05:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 740D73A1563; Mon, 31 Jan 2022 21:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jnbg21YMSSvH; Mon, 31 Jan 2022 21:51:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1DAD3A1562; Mon, 31 Jan 2022 21:51:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 3E49BF5DAF; Mon, 31 Jan 2022 21:51:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pim@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220201055134.3E49BF5DAF@rfc-editor.org>
Date: Mon, 31 Jan 2022 21:51:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/DbL9wV-Vut9t8kYjRJgHZAXFYY0>
Subject: [pim] RFC 9166 on A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2022 05:51:42 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9166 Title: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Author: H. Zhao, X. Liu, Y. Liu, A. Peter, M. Sivakumar Status: Standards Track Stream: IETF Date: January 2022 Mailbox: hongji.zhao@ericsson.com, xufeng.liu.ietf@gmail.com, liuyisong@chinamobile.com, anish.ietf@gmail.com, sivakumar.mahesh@gmail.com Pages: 37 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pim-igmp-mld-snooping-yang-20.txt URL: https://www.rfc-editor.org/info/rfc9166 DOI: 10.17487/RFC9166 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) snooping devices. The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA). This document is a product of the Protocols for IP Multicast Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC