draft-ietf-l2vpn-vpls-multihoming-02.txt   draft-ietf-l2vpn-vpls-multihoming-03.txt 
Network Working Group B. Kothari Network Working Group B. Kothari
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 4761 (if approved) K. Kompella Updates: 4761 (if approved) K. Kompella
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: April 28, 2011 W. Henderickx Expires: February 6, 2012 W. Henderickx
F. Balus F. Balus
Alcatel-Lucent Alcatel-Lucent
J. Uttaro J. Uttaro
AT&T AT&T
October 25, 2010 July 6, 2011
BGP based Multi-homing in Virtual Private LAN Service BGP based Multi-homing in Virtual Private LAN Service
draft-ietf-l2vpn-vpls-multihoming-02.txt draft-ietf-l2vpn-vpls-multihoming-03.txt
Abstract Abstract
Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private
Network (VPN) that gives its customers the appearance that their Network (VPN) that gives its customers the appearance that their
sites are connected via a Local Area Network (LAN). It is often sites are connected via a Local Area Network (LAN). It is often
required for the Service Provider (SP) to give the customer redundant required for the Service Provider (SP) to give the customer redundant
connectivity to some sites, often called "multi-homing". This memo connectivity to some sites, often called "multi-homing". This memo
shows how BGP-based multi-homing can be offered in the context of LDP shows how BGP-based multi-homing can be offered in the context of LDP
and BGP VPLS solutions. and BGP VPLS solutions.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 28, 2011. This Internet-Draft will expire on February 6, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 14 skipping to change at page 4, line 14
1. Introduction 1. Introduction
Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private
Network (VPN) that gives its customers the appearance that their Network (VPN) that gives its customers the appearance that their
sites are connected via a Local Area Network (LAN). It is often sites are connected via a Local Area Network (LAN). It is often
required for a Service Provider (SP) to give the customer redundant required for a Service Provider (SP) to give the customer redundant
connectivity to one or more sites, often called "multi-homing". connectivity to one or more sites, often called "multi-homing".
[RFC4761] explains how VPLS can be offered using BGP for auto- [RFC4761] explains how VPLS can be offered using BGP for auto-
discovery and signaling; section 3.5 of that document describes how discovery and signaling; section 3.5 of that document describes how
multi-homing can be achieved in this context. multi-homing can be achieved in this context. [RFC6074] explains how
[I-D.ietf-l2vpn-signaling] explains how VPLS can be offered using BGP VPLS can be offered using BGP for auto- discovery, (BGP-AD) and
for auto- discovery (BGP-AD) and [RFC4762] explains how VPLS can be [RFC4762] explains how VPLS can be offered using LDP for signaling.
offered using LDP for signaling. This document provides a BGP-based This document provides a BGP-based multi-homing solution applicable
multi-homing solution applicable to both BGP and LDP VPLS to both BGP and LDP VPLS technologies. Note that BGP MH can be used
technologies. Note that BGP MH can be used for LDP VPLS without the for LDP VPLS without the use of the BGP- AD solution.
use of the BGP- AD solution.
Section 2 lays out some of the scenarios for multi-homing, other ways Section 2 lays out some of the scenarios for multi-homing, other ways
that this can be achieved, and some of the expectations of BGP-based that this can be achieved, and some of the expectations of BGP-based
multi-homing. Section 3 defines the components of BGP-based multi- multi-homing. Section 3 defines the components of BGP-based multi-
homing, and the procedures required to achieve this. Section 7 may homing, and the procedures required to achieve this. Section 7 may
someday discuss security considerations. someday discuss security considerations.
1.1. General Terminology 1.1. General Terminology
Some general terminology is defined here; most is from [RFC4761], Some general terminology is defined here; most is from [RFC4761],
skipping to change at page 15, line 24 skipping to change at page 15, line 24
For backwards compatibility, if VPLS preference is used, then BGP For backwards compatibility, if VPLS preference is used, then BGP
Local Preference MUST be set to the value of VPLS preference. Note Local Preference MUST be set to the value of VPLS preference. Note
that a Local Preference value of zero for a MH-ID is not valid unless that a Local Preference value of zero for a MH-ID is not valid unless
'D' bit in the control flags is set (see 'D' bit in the control flags is set (see
[I-D.kothari-l2vpn-auto-site-id]). In addition, Local Preference [I-D.kothari-l2vpn-auto-site-id]). In addition, Local Preference
value greater than or equal to 2^16 for VPLS advertisements is not value greater than or equal to 2^16 for VPLS advertisements is not
valid. valid.
4.3. Use of BGP-MH attributes in Inter-AS Methods 4.3. Use of BGP-MH attributes in Inter-AS Methods
Section 3.4 in [RFC4761] and section 4 in [I-D.ietf-l2vpn-signaling] Section 3.4 in [RFC4761] and section 4 in [RFC6074] describe three
describe three methods (a, b and c) to connect sites in a VPLS to PEs methods (a, b and c) to connect sites in a VPLS to PEs that are
that are across multiple AS. Since VPLS advertisements in method (a) across multiple AS. Since VPLS advertisements in method (a) do
do not cross AS boundaries, multi-homing operations for method (a) not cross AS boundaries, multi-homing operations for method (a)
remain exactly the same as they are within as AS. However, for remain exactly the same as they are within as AS. However, for
method (b) and (c), VPLS advertisements do cross AS boundary. This method (b) and (c), VPLS advertisements do cross AS boundary. This
section describes the VPLS operations for method (b) and method (c). section describes the VPLS operations for method (b) and method (c).
Consider Figure 4 for inter-AS VPLS with multi-homed customer sites. Consider Figure 4 for inter-AS VPLS with multi-homed customer sites.
4.3.1. Inter-AS Method (b): EBGP Redistribution of VPLS Information 4.3.1. Inter-AS Method (b): EBGP Redistribution of VPLS Information
between ASBRs between ASBRs
AS1 AS2 AS1 AS2
........ ........ ........ ........
skipping to change at page 25, line 16 skipping to change at page 25, line 16
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service [RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service
(VPLS) Using BGP for Auto-Discovery and Signaling", (VPLS) Using BGP for Auto-Discovery and Signaling",
RFC 4761, January 2007. RFC 4761, January 2007.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. [RFC6074] Rosen, E., "Provisioning, Autodiscovery, and Signaling in
Heron, "Pseudowire Setup and Maintenance Using the Label L2VPNs", RFC 6074, January 2011.
Distribution Protocol (LDP)", RFC 4447, April 2006.
[RFC4446] Martini, L., "IANA Allocations for Pseudowire Edge to Edge
Emulation (PWE3)", BCP 116, RFC 4446, April 2006.
[I-D.ietf-l2vpn-signaling] 10.2. Informative References
Rosen, E., "Provisioning, Autodiscovery, and Signaling in
L2VPNs", draft-ietf-l2vpn-signaling-08 (work in progress),
May 2006.
[I-D.kothari-l2vpn-vpls-flush] [I-D.kothari-l2vpn-vpls-flush]
Kothari, B. and R. Fernando, "VPLS Flush in BGP-based Kothari, B. and R. Fernando, "VPLS Flush in BGP-based
Virtual Private LAN Service", Virtual Private LAN Service",
draft-kothari-l2vpn-vpls-flush-00 (work in progress), draft-kothari-l2vpn-vpls-flush-00 (work in progress),
October 2008. October 2008.
[I-D.kothari-l2vpn-auto-site-id] [I-D.kothari-l2vpn-auto-site-id]
Kothari, B., Kompella, K., and T. IV, "Automatic Kothari, B., Kompella, K., and T. IV, "Automatic
Generation of Site IDs for Virtual Private LAN Service", Generation of Site IDs for Virtual Private LAN Service",
draft-kothari-l2vpn-auto-site-id-01 (work in progress), draft-kothari-l2vpn-auto-site-id-01 (work in progress),
October 2008. October 2008.
[I-D.ietf-pwe3-redundancy-bit]
Muley, P., "May 14, 2010 Pseudowire Preferential
Forwarding Status Bit", draft-ietf-pwe3-redundancy-bit-03
(work in progress), May 2010.
10.2. Informative References
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, February 2006. Communities Attribute", RFC 4360, February 2006.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006. Networks (VPNs)", RFC 4364, February 2006.
[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route
Reflection: An Alternative to Full Mesh Internal BGP Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, April 2006. (IBGP)", RFC 4456, April 2006.
skipping to change at page 27, line 10 skipping to change at page 26, line 10
RFC 4762, January 2007. RFC 4762, January 2007.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
Authors' Addresses Authors' Addresses
Bhupesh Kothari Bhupesh Kothari
Cisco Systems Cisco Systems
3750 Cisco Way 3750 Cisco Way
San Jose, CA 95134 San Jose, CA 95134, US
US
Email: bhupesh@cisco.com Email: bhupesh@cisco.com
Kireeti Kompella Kireeti Kompella
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089 US
US
Email: kireeti@juniper.net Email: kireeti@juniper.net
Wim Henderickx Wim Henderickx
Alcatel-Lucent Alcatel-Lucent
Email: wim.henderickx@alcatel-lucent.be Email: wim.henderickx@alcatel-lucent.be
Florin Balus Florin Balus
Alcatel-Lucent Alcatel-Lucent
Email: florin.balus@alcatel-lucent.com Email: florin.balus@alcatel-lucent.com
James Uttaro James Uttaro
AT&T AT&T
200 S. Laurel Avenue 200 S. Laurel Avenue
Middletown, NJ 07748 Middletown, NJ 07748, US
US
Email: uttaro@att.com Email: uttaro@att.com
 End of changes. 15 change blocks. 
44 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/