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

The information below is for an old version of the document
Document Type Active Internet-Draft (l2vpn WG)
Last updated 2012-07-16
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: January 17, 2013                                       J. Zhang
                                                  Juniper Networks, Inc.
                                                               V. Hemige
                                                          Alcatel-Lucent
                                                           July 16, 2012

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

Abstract

   In Virtual Private LAN Service (VPLS), as also in IEEE Bridged
   Networks, the switches simply flood multicast traffic on all ports in
   the LAN by default.  IGMP Snooping is commonly deployed to ensure
   multicast traffic is not forwarded on ports without IGMP receivers.
   The procedures and recommendations for IGMP Snooping are defined in
   [IGMP-SNOOP].  But when any protocol other than IGMP is used, the
   common practice is to simply flood multicast traffic to all ports.
   PIM-SM, PIM-SSM, PIM-BIDIR are widely deployed routing protocols.
   PIM Snooping procedures are important to restrict multicast traffic
   to only the routers interested in receiving such traffic.

   While most of the PIM Snooping procedures defined here also apply to
   IEEE Bridged Networks, VPLS demands certain special procedures due to
   the split-horizon rules that require the Provider Edge (PE) devices
   to co-operate.  This document describes the procedures and
   recommendations for PIM-Snooping in VPLS to facilitate replication to
   only those ports behind which there are interested PIM routers and/or
   IGMP hosts.  This document also describes procedures for PIM Proxy.
   PIM Proxy is required on PEs for VPLS Multicast to work correctly
   when Join suppression is enabled in the VPLS.  PIM Proxy also helps
   scale VPLS Multicast much better than just PIM Snooping.

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.

Dornon, et al.          Expires January 17, 2013                [Page 1]
Internet-Draft             l2vpn-pim-snooping                  July 2012

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   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 January 17, 2013.

Copyright Notice

   Copyright (c) 2012 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 January 17, 2013                [Page 2]
Internet-Draft             l2vpn-pim-snooping                  July 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Assumptions  . . . . . . . . . . . . . . . . . . . . . . .  6
     1.2.  PIM Snooping and PIM Proxy Complexity  . . . . . . . . . .  6
     1.3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  6
   2.  Multicast Traffic over VPLS  . . . . . . . . . . . . . . . . .  7
     2.1.  Constraining of IP Multicast in a VPLS . . . . . . . . . .  8
     2.2.  IPv6 Considerations  . . . . . . . . . . . . . . . . . . .  9
     2.3.  PIM-SM (*,*,RP) Considerations . . . . . . . . . . . . . .  9
     2.4.  PIM Packet Types to Snoop  . . . . . . . . . . . . . . . .  9
     2.5.  PIM Snooping vs PIM Proxy  . . . . . . . . . . . . . . . .  9
       2.5.1.  Differences between PIM Snooping and PIM Proxy . . . . 10
       2.5.2.  PIM Control Message Latency  . . . . . . . . . . . . . 11
       2.5.3.  When to Snoop and When to Proxy  . . . . . . . . . . . 11
Show full document text