EVPN-VPWS Seamless Integration with Legacy VPWS
draft-brissette-bess-evpn-vpws-seamless-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-10-31
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
BESS Working Group P. Brissette, Ed.
Internet-Draft A. Sajassi
Intended status: Standards Track L. Burdet
Expires: May 3, 2020 Cisco Systems
J. Uttaro
ATT
October 31, 2019
EVPN-VPWS Seamless Integration with Legacy VPWS
draft-brissette-bess-evpn-vpws-seamless-00
Abstract
This document specifies mechanisms for backward compatibility of
Ethernet VPN Virtual Private Wire Service (EVPN-VPWS) solutions with
legacy Virtual Private Wire Service (VPWS). It provides mechanisms
for seamless integration in the same MPLS/IP network on a per-
pseudowire or per-flexible-crossconnect basis. Implementation of
this document enables service providers to introduce EVPN-VPWS PEs in
their brown-field deployments of leagcy VPWS networks. This document
specifies control-plane and forwarding behavior needed for auto-
discovery of a pseudowire in order to enable seamless integration
between EVPN-VPWS and VPWS PEs.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on May 3, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Brissette, et al. Expires May 3, 2020 [Page 1]
Internet-Draft Abbreviated Title October 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Terms and Abbreviations . . . . . . . . . . . . . . . . . . . 4
3. Solution Requirements . . . . . . . . . . . . . . . . . . . . 5
4. Seamless Integration . . . . . . . . . . . . . . . . . . . . 6
5. Capability Discovery . . . . . . . . . . . . . . . . . . . . 6
6. Forwarding and Control Plane Operations . . . . . . . . . . . 6
6.1. Multi-homed Operations . . . . . . . . . . . . . . . . . 8
6.1.1. Operations with Port-Active MH PEs . . . . . . . . . 8
6.1.2. Operation with Single-Active MH PEs . . . . . . . . . 9
6.1.3. Operation with All-Active MH PEs . . . . . . . . . . 9
6.1.3.1. Falling back to port-active . . . . . . . . . . . 9
6.1.3.2. All-active procedures . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Virtual Private Wire Service (VPWS) is a widely-deployed Layer-2 VPN
(L2VPN) technology. Many service providers, who are looking at
adopting Ethernet VPN Virtual Private Wire Service (EVPN-VPWS), want
to preserve their investment in the VPWS networks. Hence, they
require mechanisms by which EVPN-VPWS can be introduced into their
brown-field legacy VPWS networks without requiring any upgrades
(software or hardware) to these networks. This document specifies
procedures for the seamless integration of the two technologies
(EVPN-VPWS and legacy VPWS) in the same MPLS/IP network. This
document specifies control-plane and forwarding behaviour needed for
auto-discovery of a pseudowire in order to enable seamless
Show full document text