datatracker.ietf.org
Sign in
Version 5.9.0, 2014-12-18
Report a bug

Wildcards in Multicast VPN Auto-Discovery Routes
RFC 6625

Internet Engineering Task Force (IETF)                     E. Rosen, Ed.
Request for Comments: 6625                           Cisco Systems, Inc.
Updates: 6514                                            Y. Rekhter, Ed.
Category: Standards Track                         Juniper Networks, Inc.
ISSN: 2070-1721                                            W. Henderickx
                                                          Alcatel-Lucent
                                                                  R. Qiu
                                                                  Huawei
                                                                May 2012

            Wildcards in Multicast VPN Auto-Discovery Routes

Abstract

   In Multicast Virtual Private Networks (MVPNs), customer multicast
   flows are carried in "tunnels" through a service provider's network.
   The base specifications for MVPN define BGP multicast VPN "auto-
   discovery routes" and specify how to use an auto-discovery route to
   advertise the fact that an individual customer multicast flow is
   being carried in a particular tunnel.  However, those specifications
   do not provide a way to specify, in a single such route, that
   multiple customer flows are being carried in a single tunnel.  Those
   specifications also do not provide a way to advertise that a
   particular tunnel is to be used by default to carry all customer
   flows, except in the case where that tunnel is joined by all the
   provider edge routers of the MVPN.  This document eliminates these
   restrictions by specifying the use of "wildcard" elements in the
   customer flow identifiers.  With wildcard elements, a single auto-
   discovery route can refer to multiple customer flows or even to all
   customer flows.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6625.

Rosen, et al.                Standards Track                    [Page 1]
RFC 6625              Wildcards in MVPN A-D Routes              May 2012

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.

Table of Contents

   1. Introduction ....................................................3
      1.1. Terminology ................................................3
      1.2. Wildcards in S-PMSI A-D Routes .............................5
      1.3. Use Cases ..................................................5
   2. Encoding of Wildcards ...........................................7
   3. Finding the Matching S-PMSI A-D Route ...........................8
      3.1. Finding the Match for Data Transmission ....................8
      3.2. Finding the Match for Data Reception .......................9
           3.2.1. Finding the Match for (C-S,C-G) .....................9
           3.2.2. Finding the Wildcard Match for (C-*,C-G) ............9
   4. Procedures for S-PMSI A-D Routes with Wildcards ................10
      4.1. Procedures for All Kinds of Wildcards .....................10
      4.2. Procedures for (C-*,C-G) S-PMSI A-D Routes ................11
      4.3. Procedures for (C-S,C-*) S-PMSI A-D Routes ................12
      4.4. Procedures for (C-*,C-*) S-PMSI A-D Routes ................13
   5. Security Considerations ........................................15
   6. Acknowledgments ................................................15
   7. Normative References ...........................................15

Rosen, et al.                Standards Track                    [Page 2]
RFC 6625              Wildcards in MVPN A-D Routes              May 2012

1.  Introduction

   In Multicast Virtual Private Networks (MVPNs), customer multicast

[include full document text]