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

The information below is for an old version of the document
Document Type Active Internet-Draft (l2vpn WG)
Last updated 2014-04-29
Replaced by RFC 8220, RFC 8220
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Layer 2 Virtual Private Networks                               O. Dornon
Internet-Draft                                               J. Kotalwar
Intended status: Informational                            Alcatel-Lucent
Expires: October 31, 2014                                      V. Hemige

                                                                  R. Qiu
                                                                Z. Zhang
                                                  Juniper Networks, Inc.
                                                          April 29, 2014

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute

Dornon, et al.          Expires October 31, 2014                [Page 1]
Internet-Draft             l2vpn-pim-snooping                 April 2014

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 31, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dornon, et al.          Expires October 31, 2014                [Page 2]
Internet-Draft             l2vpn-pim-snooping                 April 2014

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Multicast Snooping in VPLS . . . . . . . . . . . . . . . .  5
     1.2.  Assumptions  . . . . . . . . . . . . . . . . . . . . . . .  6
     1.3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  7
   2.  PIM Snooping for VPLS  . . . . . . . . . . . . . . . . . . . .  7
     2.1.  PIM protocol background  . . . . . . . . . . . . . . . . .  7
     2.2.  General Rules for PIM Snooping in VPLS . . . . . . . . . .  8
       2.2.1.  Preserving Assert Trigger  . . . . . . . . . . . . . .  8
     2.3.  Some Considerations for PIM Snooping . . . . . . . . . . .  9
       2.3.1.  Scaling  . . . . . . . . . . . . . . . . . . . . . . .  9
       2.3.2.  IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . 10
       2.3.3.  PIM-SM (*,*,RP)  . . . . . . . . . . . . . . . . . . . 10
     2.4.  PIM Snooping vs PIM Proxy  . . . . . . . . . . . . . . . . 10
       2.4.1.  Differences between PIM Snooping, Relay and Proxy  . . 10
       2.4.2.  PIM Control Message Latency  . . . . . . . . . . . . . 11
       2.4.3.  When to Snoop and When to Proxy  . . . . . . . . . . . 12
     2.5.  Discovering PIM Routers  . . . . . . . . . . . . . . . . . 13
     2.6.  PIM-SM and PIM-SSM . . . . . . . . . . . . . . . . . . . . 14
Show full document text