PIM Snooping over VPLS
draft-ietf-l2vpn-vpls-pim-snooping-05

The information below is for an old version of the document
Document Type Expired Internet-Draft (l2vpn WG)
Last updated 2014-04-11 (latest revision 2013-10-08)
Replaced by RFC 8220, RFC 8220
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-l2vpn-vpls-pim-snooping-05.txt

Abstract

This document describes the procedures and recommendations for VPLS PEs to facilitate replication of multicast traffic to only certain ports (behind which there are interested PIM routers and/or IGMP hosts) via PIM Snooping and PIM Proxy. With PIM Snooping, PEs passively listen to certain PIM control messages to build control and forwarding states while transparently flooding those messages. With PIM Proxy, 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 Proxy is required when PIM Join suppression is enabled on the 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 proxy, 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.

Authors

Olivier Dornon (olivier.dornon@alcatel-lucent.com)
Jayant Kotalwar (jayant.kotalwar@alcatel-lucent.com)
Venu Hemige (vhemige@gmail.com)
Ray Qiu (rqiu@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)