datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Virtual Hub-and-Spoke in BGP/MPLS VPNs
RFC 7024

Internet Engineering Task Force (IETF)                           H. Jeng
Request for Comments: 7024                                     J. Uttaro
Category: Standards Track                                           AT&T
ISSN: 2070-1721                                                 L. Jalil
                                                                 Verizon
                                                             B. Decraene
                                                                  Orange
                                                              Y. Rekhter
                                                        Juniper Networks
                                                             R. Aggarwal
                                                                  Arktan
                                                            October 2013

                 Virtual Hub-and-Spoke in BGP/MPLS VPNs

Abstract

   With BGP/MPLS Virtual Private Networks (VPNs), providing any-to-any
   connectivity among sites of a given VPN would require each Provider
   Edge (PE) router connected to one or more of these sites to hold all
   the routes of that VPN.  The approach described in this document
   allows the VPN service provider to reduce the number of PE routers
   that have to maintain all these routes by requiring only a subset of
   these routers to maintain all these routes.

   Furthermore, when PE routers use ingress replication to carry the
   multicast traffic of VPN customers, the approach described in this
   document may, under certain circumstances, reduce bandwidth
   inefficiency associated with ingress replication and redistribute the
   replication load among PE routers.

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/rfc7024.

Jeng, et al.                 Standards Track                    [Page 1]
RFC 7024         Virtual Hub-and-Spoke in BGP/MPLS VPNs     October 2013

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

Table of Contents

   1. Overview ........................................................3
   2. Specification of Requirements ...................................4
   3. Routing Information Exchange ....................................5
   4. Forwarding Considerations .......................................7
   5. Internet Connectivity ...........................................9
   6. Deployment Considerations ......................................12
   7. Multicast Considerations .......................................13
      7.1. Terminology ...............................................14
      7.2. Eligible Upstream Multicast Hop (UMH) Routes ..............14
      7.3. Originating VPN-IP Default Route by a V-Hub ...............14
      7.4. Handling C-Multicast Routes ...............................15
      7.5. Originating I-PMSI/S-PMSI/SA A-D Routes by V-Spoke ........15
      7.6. Originating I-PMSI/S-PMSI/SA A-D Routes by V-Hub ..........16
      7.7. Receiving I-PMSI/S-PMSI/SA A-D Routes by V-Spoke ..........17
      7.8. Receiving I-PMSI/S-PMSI/SA A-D Routes by V-Hub ............17
           7.8.1. Case 1 .............................................17
           7.8.2. Case 2 .............................................18
      7.9. Use of Ingress Replication with I-PMSI A-D Routes .........20
   8. An Example of RT Provisioning ..................................21
      8.1. Unicast Routing ...........................................21
      8.2. Multicast Routing .........................................22
   9. Further Refinements ............................................23
   10. Security Considerations .......................................23

[include full document text]