Re: [Pals] I-D Action: draft-ietf-pals-vpls-pim-snooping-04.txt

[Olivier Dornon <[e-mail]>]

Before the pals WG was created, this draft has been through last call in 
the l2vpn WG.  This resulted in added clarifications and a lot of 
editorial changes (mainly based on E. Rosen's feedback).

This was still work in progress when the pals WG was created.
We've now finalized the work and think this document is ready for last 
call in the pals WG.

Compared to the version that was last presented, you'll find that most 
changes are either editorial, rephrasing or added text for clarification.

Please review and pass on any comments.
Depending on the reactions, I'd then like to ask the chairs to start the 
last call proceedings.

Thanks,
Olivier.

On 01/04/2017 10:05 AM, [e-mail] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Pseudowire And LDP-enabled Services of the IETF.
>
>          Title           : Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
>          Authors         : Olivier Dornon
>                            Jayant Kotalwar
>                            Venu Hemige
>                            Ray Qiu
>                            Jeffrey Zhang
> 	Filename        : draft-ietf-pals-vpls-pim-snooping-04.txt
> 	Pages           : 40
> 	Date            : 2017-01-04
>
> 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 IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pals-vpls-pim-snooping/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-pals-vpls-pim-snooping-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-pals-vpls-pim-snooping-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Pals mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/pals