BGP Extended Community for Virtual Private Wire Service Support in Ethernet VPN
draft-ssm-bess-bgp-ec-evpn-vpws-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                         R. Srikanth
Internet-Draft                                            R. Satishkumar
Intended status: Standards Track                              M. Perumal
Expires: September 8, 2019                                      Ericsson
                                                           March 7, 2019

   BGP Extended Community for Virtual Private Wire Service Support in
                              Ethernet VPN
                  draft-ssm-bess-bgp-ec-evpn-vpws-00

Abstract

   This document describes an optional BGP extended community for use in
   Ethernet VPN (EVPN) Virtual Private Wire Service (VPWS).  It helps in
   avoiding the situation where the EVPN VPWS instance is declared 'up'
   on one side but remains 'down' on the other side.

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 September 8, 2019.

Copyright Notice

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

Srikanth, et al.        Expires September 8, 2019               [Page 1]
Internet-Draft      draft-ssm-bess-bgp-ec-evpn-vpws-00         March 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Description . . . . . . . . . . . . . . . . . . . . .   3
   4.  Remote VPWS Instance Identifier Extended Community  . . . . .   3
   5.  Usage of the Extended Community . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerationss  . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In EVPN, a VPWS service instance is identified by a pair of per-EVI
   Ethernet A-D routes as described in [RFC8214].  Each Provider Edge
   (PE) node that wants to instantiate a VPWS service instance encodes
   the VPWS service instance identifier in the 32-bit Ethernet Tag ID
   field of the per-EVI Ethernet A-D route.

   The pair of PEs instantiating a VPWS service instance will each
   advertise a per-EVI Ethernet A-D route with its VPWS service instance
   identifier.  Each PE is also configured with the other PE's VPWS
   service instance identifier.  When each PE receives the other PE's
   per-EVI Ethernet A-D route with the VPWS service instance identifier
   of the other PE configured on each PE, the VPWS service instance is
   instantiated.

   However, if the VPWS service identifiers are misconfigured on either
   of the PEs, it can result in a situation where the EVPN VPWS service
   instance is declared 'up' on one PE but remains 'down' on the other
   PE.

   This document describes an optional BGP extended community for use in
   VPWS that can be used to avoid the above situation.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Srikanth, et al.        Expires September 8, 2019               [Page 2]
Internet-Draft      draft-ssm-bess-bgp-ec-evpn-vpws-00         March 2019

   o  EVPN: Ethernet VPN.

   o  PE: Provider Edge Node.

   o  VPWS: Virtual Private Wire Service defined in [RFC8214].

   o  LSI: Local VPWS service instance identifier.

   o  RSI: Remote VPWS service instance identifier.

   o  EC: Extended Community.
Show full document text