Virtual Hub-and-Spoke in BGP/MPLS VPNs
draft-ietf-l3vpn-virtual-hub-07

The information below is for an old version of the document
Document Type Active Internet-Draft (l3vpn WG)
Last updated 2013-07-01
Replaces draft-rekhter-l3vpn-virtual-hub
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication Feb 2013
Doc Shepherd Follow-up Underway
Consensus Yes
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2013-04-03)
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs a YES. Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Stewart Bryant
Send notices to l3vpn-chairs@tools.ietf.org, draft-ietf-l3vpn-virtual-hub@tools.ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                        Huajin Jeng
Internet Draft                                                      AT&T
Intended status: Standards Track
Expires: January 2014                                       James Uttaro
                                                                    AT&T

                                                              Luay Jalil
                                                                 Verizon

                                                          Bruno Decraene
                                                          France Telecom

                                                           Yakov Rekhter
                                                        Juniper Networks

                                                          Rahul Aggarwal
                                                                  Arktan

                                                             July 1 2013

                 Virtual Hub-and-Spoke in BGP/MPLS VPNs

                  draft-ietf-l3vpn-virtual-hub-07.txt

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.

   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.

Jeng                                                            [Page 1]



Internet Draft     draft-ietf-l3vpn-virtual-hub-07.txt         July 2013

Copyright Notice

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

Abstract

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

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

Jeng                                                            [Page 2]



Internet Draft     draft-ietf-l3vpn-virtual-hub-07.txt         July 2013

Table of Contents

 1          Specification of requirements  .........................   4
 2          Overview  ..............................................   4
 3          Routing Information Exchange  ..........................   6
 4          Forwarding Considerations  .............................   8
 5          Internet Connectivity  .................................  10
 6          Deployment Considerations  .............................  13
 7          Multicast Considerations  ..............................  14
 7.1        Terminology  ...........................................  15
 7.2        Eligible Upstream Multicast Hop (UMH) routes  ..........  15
 7.3        Originating VPN-IP default route by a V-hub  ...........  15
 7.4        Handling C-multicast routes  ...........................  16
 7.5        Originating I-PMSI/S-PMSI/SA A-D routes by V-spoke  ....  16
 7.6        Originating I-PMSI/S-PMSI/SA A-D routes by V-hub  ......  17
 7.7        Receiving I-PMSI/S-PMSI/SA A-D routes by V-spoke  ......  18
 7.8        Receiving I-PMSI/S-PMSI/SA A-D routes by V-hub  ........  18
Show full document text