Usage of Layer 2 Attributes Extended Community in EVPN
draft-yu-bess-evpn-l2-attributes-03

Document Type Active Internet-Draft (individual)
Last updated 2019-01-21
Stream (None)
Intended RFC status (None)
Formats plain text xml 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 Workgroup                                                     T. Yu
Internet-Draft
Intended status: Standards Track                                 H. Wang
Expires: July 25, 2019                               Huawei Technologies
                                                        January 21, 2019

         Usage of Layer 2 Attributes Extended Community in EVPN
                  draft-yu-bess-evpn-l2-attributes-03

Abstract

   This document adopts Layer 2 Attributes Extended Community defined in
   [RFC8214] to EVPN allowing signalling L2 information in control
   plane.

   An interoperability mechanism of control word is described for EVPN
   and VPWS in this document.

   Also flow label signalling mechanism is described for EVPN and VPWS.

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 July 25, 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

Yu & Wang                 Expires July 25, 2019                 [Page 1]
Internet-Draft       Usage of L2 Attributes in EVPN         January 2019

   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
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  EVPN Layer 2 Attributes Extended Community  . . . . . . . . .   3
   5.  Usage of Control Word . . . . . . . . . . . . . . . . . . . .   5
     5.1.  EVPN ELAN . . . . . . . . . . . . . . . . . . . . . . . .   5
       5.1.1.  Deterministic mode  . . . . . . . . . . . . . . . . .   5
       5.1.2.  Interoperable mode  . . . . . . . . . . . . . . . . .   6
     5.2.  EVPN VPWS . . . . . . . . . . . . . . . . . . . . . . . .   7
       5.2.1.  Deterministic mode  . . . . . . . . . . . . . . . . .   7
       5.2.2.  Interoperable mode  . . . . . . . . . . . . . . . . .   8
     5.3.  EVPN E-Tree . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Usage of Flow Label . . . . . . . . . . . . . . . . . . . . .   9
   7.  L2 MTU Processing . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Instructions on Using Control Word and Flow Label . . . . . .  10
   9.  Other Considerations  . . . . . . . . . . . . . . . . . . . .  10
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   EVPN [RFC7432] lacks of a negotiation mechanism on L2 capabilities.
   If the L2 capabilities between PE devices are different, they are not
   able to communicate properly.  [RFC8214] defines Layer 2 Attributes
   Extended Community but there is no description on how to be used in
   EVPN ELAN.  This document describes how Layer 2 Attributes Extended
   Community is used in EVPN ELAN.

   Considering some devices have no capability to support control word
   and there are legacy devices without control word function supported,
   an interoperability mechanism on control word is described.

   To achieve better load balancing on EVPN ELAN and VPWS services, flow
   label function in EVPN is described in this document.

Yu & Wang                 Expires July 25, 2019                 [Page 2]
Internet-Draft       Usage of L2 Attributes in EVPN         January 2019

2.  Specification of Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
Show full document text