draft-ietf-bess-vpls-multihoming-03.txt   draft-ietf-bess-vpls-multihoming-04.txt 
Network Working Group B. Kothari Network Working Group B. Kothari
Internet-Draft Augtera Networks Internet-Draft Augtera Networks
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: September 27, 2019 W. Henderickx Expires: January 24, 2020 W. Henderickx
Nokia Nokia
F. Balus F. Balus
Cisco Cisco
J. Uttaro J. Uttaro
AT&T AT&T
Mar 26, 2019 July 23, 2019
BGP based Multi-homing in Virtual Private LAN Service BGP based Multi-homing in Virtual Private LAN Service
draft-ietf-bess-vpls-multihoming-03.txt draft-ietf-bess-vpls-multihoming-04.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. This document updates [RFC4761] by defining
new flags in the Control Flags field of the Layer2 Info Extended
Community.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 27, 2019. This Internet-Draft will expire on January 24, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 21 skipping to change at page 2, line 26
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. General Terminology . . . . . . . . . . . . . . . . . . . 3 1.1. General Terminology . . . . . . . . . . . . . . . . . . . 3
1.2. Conventions . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Conventions . . . . . . . . . . . . . . . . . . . . . . . 4
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. VPLS Multi-homing Considerations . . . . . . . . . . . . 5 2.2. VPLS Multi-homing Considerations . . . . . . . . . . . . 5
3. Multi-homing Operation . . . . . . . . . . . . . . . . . . . 6 3. Multi-homing Operation . . . . . . . . . . . . . . . . . . . 6
3.1. Customer Edge (CE) NLRI . . . . . . . . . . . . . . . . . 6 3.1. Customer Edge (CE) NLRI . . . . . . . . . . . . . . . . . 6
3.2. Deployment Considerations . . . . . . . . . . . . . . . . 7 3.2. Deployment Considerations . . . . . . . . . . . . . . . . 7
3.3. Designated Forwarder Election . . . . . . . . . . . . . . 8 3.3. Designated Forwarder Election . . . . . . . . . . . . . . 8
3.3.1. Attributes . . . . . . . . . . . . . . . . . . . . . 8 3.3.1. Attributes . . . . . . . . . . . . . . . . . . . . . 8
3.3.2. Variables Used . . . . . . . . . . . . . . . . . . . 9 3.3.2. Variables Used . . . . . . . . . . . . . . . . . . . 9
3.3.3. Election Procedures . . . . . . . . . . . . . . . . . 11 3.3.3. Election Procedures . . . . . . . . . . . . . . . . . 11
3.4. DF Election on PEs . . . . . . . . . . . . . . . . . . . 12 3.4. DF Election on PEs . . . . . . . . . . . . . . . . . . . 13
3.5. Pseudowire and Site-ID Binding Properties . . . . . . . . 13 3.5. Pseudowire and Site-ID Binding Properties . . . . . . . . 13
4. Multi-AS VPLS . . . . . . . . . . . . . . . . . . . . . . . . 13 4. Multi-AS VPLS . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. Route Origin Extended Community . . . . . . . . . . . . . 13 4.1. Route Origin Extended Community . . . . . . . . . . . . . 13
4.2. VPLS Preference . . . . . . . . . . . . . . . . . . . . . 13 4.2. VPLS Preference . . . . . . . . . . . . . . . . . . . . . 14
4.3. Use of BGP attributes in Inter-AS Methods . . . . . . . . 14 4.3. Use of BGP attributes in Inter-AS Methods . . . . . . . . 15
4.3.1. Inter-AS Method (b): EBGP Redistribution of VPLS 4.3.1. Inter-AS Method (b): EBGP Redistribution of VPLS
Information between ASBRs . . . . . . . . . . . . . . 15 Information between ASBRs . . . . . . . . . . . . . . 15
4.3.2. Inter-AS Method (c): Multi-Hop EBGP Redistribution of 4.3.2. Inter-AS Method (c): Multi-Hop EBGP Redistribution of
VPLS Information between ASes . . . . . . . . . 16 VPLS Information between ASes . . . . . . . . . 16
5. MAC Flush Operations . . . . . . . . . . . . . . . . . . . . 16 5. MAC Flush Operations . . . . . . . . . . . . . . . . . . . . 17
5.1. MAC Flush Indicators . . . . . . . . . . . . . . . . . . 16 5.1. MAC Flush Indicators . . . . . . . . . . . . . . . . . . 17
5.2. Minimizing the effects of fast link transitions . . . . . 17 5.2. Minimizing the effects of fast link transitions . . . . . 18
6. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 17 6. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 18
6.1. BGP based VPLS . . . . . . . . . . . . . . . . . . . . . 18 6.1. BGP based VPLS . . . . . . . . . . . . . . . . . . . . . 18
6.2. LDP VPLS with BGP Auto-discovery . . . . . . . . . . . . 18 6.2. LDP VPLS with BGP Auto-discovery . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Contributing Authors . . . . . . . . . . . . . . . . . . . . 19 9. Contributing Authors . . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 19 11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 20 11.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
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
 End of changes. 12 change blocks. 
21 lines changed or deleted 22 lines changed or added

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