[Pals] RFC 8220 on Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
rfc-editor@rfc-editor.org Tue, 12 September 2017 23:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9431B132969; Tue, 12 Sep 2017 16:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 HwZyUe0nkLI4; Tue, 12 Sep 2017 16:04:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E89301320DC; Tue, 12 Sep 2017 16:04:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 038BBB816E1; Tue, 12 Sep 2017 16:04:46 -0700 (PDT)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pals@ietf.org
Message-Id: <20170912230446.038BBB816E1@rfc-editor.org>
Date: Tue, 12 Sep 2017 16:04:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/0Mg9VvcBOncI8LDAoPyt1a9p9_o>
Subject: [Pals] RFC 8220 on Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2017 23:04:59 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8220
Title: Protocol Independent Multicast (PIM)
over Virtual Private LAN Service (VPLS)
Author: O. Dornon,
J. Kotalwar,
V. Hemige,
R. Qiu,
Z. Zhang
Status: Informational
Stream: IETF
Date: September 2017
Mailbox: olivier.dornon@nokia.com,
jayant.kotalwar@nokia.com,
vhemige@gmail.com,
ray@mistnet.io,
zzhang@juniper.net
Pages: 43
Characters: 88663
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pals-vpls-pim-snooping-06.txt
URL: https://www.rfc-editor.org/info/rfc8220
DOI: 10.17487/RFC8220
This document describes the procedures and recommendations for
Virtual Private LAN Service (VPLS) Provider Edges (PEs) to facilitate
replication of multicast traffic to only certain ports (behind which
there are interested Protocol Independent Multicast (PIM) routers
and/or Internet Group Management Protocol (IGMP) hosts) via PIM
snooping and proxying.
With PIM snooping, PEs passively listen to certain PIM control
messages to build control and forwarding states while transparently
flooding those messages. With PIM proxying, PEs do not flood PIM
Join/Prune messages but only generate their own and send them out of
certain ports, based on the control states built from downstream
Join/Prune messages. PIM proxying is required when PIM Join
suppression is enabled on the Customer Edge (CE) devices and is
useful for reducing PIM control traffic in a VPLS domain.
This document also describes PIM relay, which can be viewed as
lightweight proxying, where all downstream Join/Prune messages are
simply forwarded out of certain ports and are not flooded, thereby
avoiding the triggering of PIM Join suppression on CE devices.
This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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