datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

MVPN: Using Bidirectional P-Tunnels
draft-ietf-l3vpn-mvpn-bidir-05

Active Internet-Draft (l3vpn WG)
Document Stream: IETF
Last updated: 2013-04-10
Replaces: draft-rosen-l3vpn-mvpn-bidir
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (l3vpn)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

L3VPN Working Group                               Eric C. Rosen (Editor)
Internet Draft                                         IJsbrand Wijnands
Intended Status: Standards Track                     Cisco Systems, Inc.
Expires: October 10, 2013
Updates: 6513,6625
                                                               Yiqun Cai
                                                               Microsoft

                                                             Arjen Boers

                                                          April 10, 2013

                  MVPN: Using Bidirectional P-Tunnels

                   draft-ietf-l3vpn-mvpn-bidir-05.txt

Abstract

   A set of prior RFCs specify procedures for supporting multicast in
   BGP/MPLS IP VPNs.  These procedures allow customer multicast data to
   travel across a service provider's backbone network through a set of
   multicast tunnels.  The tunnels are advertised in certain BGP "auto-
   discovery" routes, by means of a BGP attribute known as the "Provider
   Multicast Service Interface (PMSI) Tunnel attribute".  Encodings have
   been defined that allow the PMSI Tunnel attribute to identify
   bidirectional (multipoint-to-multipoint) multicast distribution
   trees.  However, the prior RFCs do not provide all the necessary
   procedures for using bidirectional tunnels to support multicast VPNs.
   This document updates RFCs 6513 and 6625 by specifying those
   procedures.  In particular, it specifies the procedures for assigning
   customer multicast flows (unidirectional or bidirectional) to
   specific bidirectional tunnels in the provider backbone, for
   advertising such assignments, and for determining which flows have
   been assigned to which tunnels.

Status of this Memo

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

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

Rosen, et al.                                                   [Page 1]



Internet Draft     draft-ietf-l3vpn-mvpn-bidir-05.txt         April 2013

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Copyright and License Notice

   Copyright (c) 2013 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.

Rosen, et al.                                                   [Page 2]



Internet Draft     draft-ietf-l3vpn-mvpn-bidir-05.txt         April 2013

Table of Contents

 1          Introduction  ..........................................   4
 1.1        Terminology  ...........................................   4
 1.2        Overview  ..............................................   8
 1.2.1      Bidirectional P-tunnel Technologies  ...................   9
 1.2.2      Reasons for Using Bidirectional P-tunnels  .............   9
 1.2.3      Knowledge of Group-to-RP and/or Group-to-RPA Mappings  .  11
 1.2.4      PMSI Instantiation Methods  ............................  11
 2          The All BIDIR-PIM Wild Card  ...........................  13
 3          Using Bidirectional P-Tunnels  .........................  14
 3.1        Procedures Specific to the Tunneling Technology  .......  14
 3.1.1      BIDIR-PIM P-Tunnels  ...................................  14
 3.1.2      MP2MP LSPs  ............................................  15
 3.2        Procedures Specific to the PMSI Instantiation Method  ..  15
 3.2.1      Flat Partitioning  .....................................  15
 3.2.1.1    When an S-PMSI is a 'Match for Transmission'  ..........  17
 3.2.1.2    When an I-PMSI is a 'Match for Transmission'  ..........  19
 3.2.1.3    When an S-PMSI is a 'Match for Reception'  .............  19