Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
RFC 8395

Document Type RFC - Proposed Standard (June 2018; No errata)
Updates RFC 4761
Last updated 2018-06-26
Replaces draft-keyupate-bess-fat-pw-bgp
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Martin Vigoureux
Shepherd write-up Show (last changed 2017-08-24)
IESG IESG state RFC 8395 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to aretana.ietf@gmail.com
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          K. Patel
Request for Comments: 8395                                        Arrcus
Updates: 4761                                                 S. Boutros
Category: Standards Track                                         VMware
ISSN: 2070-1721                                                 J. Liste
                                                                   Cisco
                                                                  B. Wen
                                                                 Comcast
                                                              J. Rabadan
                                                                   Nokia
                                                               June 2018

               Extensions to BGP-Signaled Pseudowires to
                  Support Flow-Aware Transport Labels

Abstract

   This document defines protocol extensions required to synchronize
   flow label states among Provider Edges (PEs) when using the BGP-based
   signaling procedures.  These protocol extensions are equally
   applicable to point-to-point Layer 2 Virtual Private Networks
   (L2VPNs).  This document updates RFC 4761 by defining new flags in
   the Control Flags field of the Layer2 Info Extended Community.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8395.

Patel, et al.                Standards Track                    [Page 1]
RFC 8395               BGP-Signaled FAT PW Labels              June 2018

Copyright Notice

   Copyright (c) 2018 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
   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. Modifications to the Layer2 Info Extended Community .............4
   3. Signaling the Presence of the Flow Label ........................5
   4. IANA Considerations .............................................6
   5. Security Considerations .........................................6
   6. References ......................................................7
      6.1. Normative References .......................................7
      6.2. Informative References .....................................7
   Acknowledgements ...................................................8
   Contributors .......................................................8
   Authors' Addresses .................................................9

1.  Introduction

   The mechanism described in [RFC6391] uses an additional label (Flow
   Label) in the MPLS label stack to allow Label Switching Routers
   (LSRs) to balance flows within Pseudowires (PWs) at a finer
   granularity than the individual PWs across the Equal Cost Multiple
   Paths (ECMPs) that exists within the Packet Switched Network (PSN).

   Furthermore, [RFC6391] defines the LDP protocol extensions required
   to synchronize the flow label states between the ingress and egress
   PEs when using the signaling procedures defined in the [RFC8077].

   A PW [RFC3985] is transported over one single network path, even if
   ECMPs exist between the ingress and egress PW provider edge (PE)
   equipment.  This is required to preserve the characteristics of the
   emulated service.

Patel, et al.                Standards Track                    [Page 2]
RFC 8395               BGP-Signaled FAT PW Labels              June 2018

   This document introduces an optional mode of operation allowing a PW
   to be transported over ECMPs, for example when the use of ECMPs is
   known to be beneficial to the operation of the PW.  This
   specification uses the principles defined in [RFC6391] and augments
   the BGP-signaling procedures of [RFC4761] and [RFC6624].  The use of
   a single path to preserve the packet delivery order remains the
Show full document text