[Pals] Last Call: <draft-ietf-pals-vpls-pim-snooping-05.txt> (Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)) to Informational RFC

The IESG <iesg-secretary@ietf.org> Fri, 05 May 2017 15:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: db3546@att.com, agmalis@gmail.com, pals-chairs@ietf.org, Andrew Malis <agmalis@gmail.com>, pals@ietf.org, draft-ietf-pals-vpls-pim-snooping@ietf.org
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149399847394.8410.10673558056567134419.idtracker@ietfa.amsl.com>
Date: Fri, 05 May 2017 08:34:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/jaTDXPreYajaMCkZFgeyjPmiiVc>
Subject: [Pals] Last Call: <draft-ietf-pals-vpls-pim-snooping-05.txt> (Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)) to Informational RFC

The IESG has received a request from the Pseudowire And LDP-enabled
Services WG (pals) to consider the following document:
- 'Protocol Independent Multicast (PIM) over Virtual Private LAN Service
   (VPLS)'
  <draft-ietf-pals-vpls-pim-snooping-05.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-05-19. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   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 Protocol
   Independent Multicast (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, Provider Edges (PEs) do
   not flood PIM Join/Prune messages but only generate their own and
   send 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 Equipment (CE) devices
   and useful to reduce PIM control traffic in a VPLS domain.

   The document also describes PIM relay, which can be viewed as light-
   weight proxying, where all downstream Join/Prune messages are simply
   forwarded out of certain ports but not flooded to avoid triggering
   PIM Join suppression on CE devices.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pals-vpls-pim-snooping/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pals-vpls-pim-snooping/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2366/

[Pals] Last Call: <draft-ietf-pals-vpls-pim-snoop… The IESG