Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport Labels
draft-ietf-bess-fat-pw-bgp-02

Document Type Active Internet-Draft (bess WG)
Last updated 2017-03-27
Replaces draft-keyupate-bess-fat-pw-bgp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                                  K. Patel
Intended Status: Standard Track                                   Arrcus
                                                              S. Boutros
                                                                  VMware
                                                                J. Liste
                                                                   Cisco
                                                                  B. Wen
                                                                 Comcast
                                                              J. Rabadan
                                                                   Nokia

Expires: September 28, 2017                               March 27, 2017

 Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport
                                 Labels
                   draft-ietf-bess-fat-pw-bgp-02.txt

Abstract

   [RFC6391] describes a mechanism that uses an additional label (Flow
   Label) in the MPLS label stack that allows Label Switch Routers to
   balance flows within Pseudowires at a finer granularity than the
   individual Pseudowires 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 [RFC4447].

   This draft defines protocol extensions required to synchronize flow
   label states among PEs when using the BGP-based signaling procedures
   defined in [RFC4761].  These protocol extensions are equally
   applicable to point-to-point L2VPNs defined in [RFC6624].

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
 

Patel & Boutros, et al.Expires September 28, 2017               [Page 1]
INTERNET DRAFT         BGP Signaled FAT PW Labels         March 27, 2017

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Requirements Language . . . . . . . . . . . . . . . . . . .  3
   2. Modifications to Layer 2 Info Extended Community  . . . . . . .  4
   3.  Signaling the Presence of the Flow Label . . . . . . . . . . .  5
   4 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . .  6
   5 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  6
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  6
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     8.1.  Normative References . . . . . . . . . . . . . . . . . . .  7
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  8

 

Patel & Boutros, et al.Expires September 28, 2017               [Page 2]
INTERNET DRAFT         BGP Signaled FAT PW Labels         March 27, 2017

1  Introduction

   A pseudowire (PW)[RFC3985] is normally transported over one single
   network path, even if multiple Equal Cost Multiple Paths (ECMPs)
   exist between the ingress and egress PW provider edge (PE) equipment.

   This is required to preserve the characteristics of the emulated
Show full document text