[pim] STD 83, RFC 7761 on Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
rfc-editor@rfc-editor.org Sat, 12 March 2016 00:06 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 2EBBD12DB98; Fri, 11 Mar 2016 16:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 SIVR6MSUVnhJ; Fri, 11 Mar 2016 16:06:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8118612DAAF; Fri, 11 Mar 2016 16:06:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 25C64180003; Fri, 11 Mar 2016 16:05:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160312000557.25C64180003@rfc-editor.org>
Date: Fri, 11 Mar 2016 16:05:57 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/oGjLJTHrBHrappgiQDh8sAgwo_k>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] STD 83, RFC 7761 on Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 12 Mar 2016 00:06:22 -0000
A new Request for Comments is now available in online RFC libraries. STD 83 RFC 7761 Title: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised) Author: B. Fenner, M. Handley, H. Holbrook, I. Kouvelas, R. Parekh, Z. Zhang, L. Zheng Status: Standards Track Stream: IETF Date: March 2016 Mailbox: fenner@arista.com, m.handley@cs.ucl.ac.uk, holbrook@arista.com, kouvelas@arista.com, riparekh@cisco.com, zzhang@juniper.net, vero.zheng@huawei.com Pages: 137 Characters: 295255 Obsoletes: RFC 4601 See Also: STD 83 I-D Tag: draft-ietf-pim-rfc4601bis-06.txt URL: https://www.rfc-editor.org/info/rfc7761 DOI: http://dx.doi.org/10.17487/RFC7761 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 is a product of the Protocols for IP Multicast Working Group of the IETF. This is now an Internet 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
- [pim] STD 83, RFC 7761 on Protocol Independent Mu… rfc-editor
- Re: [pim] STD 83, RFC 7761 on Protocol Independen… William Atwood
- Re: [pim] STD 83, RFC 7761 on Protocol Independen… Jeffrey (Zhaohui) Zhang
- Re: [pim] STD 83, RFC 7761 on Protocol Independen… Stig Venaas