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

Document Type Replaced Internet-Draft (individual)
Last updated 2015-07-20 (latest revision 2015-04-29)
Replaces draft-keyupate-l2vpn-fat-pw-bgp
Replaced by draft-ietf-bess-fat-pw-bgp
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-bess-fat-pw-bgp
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-keyupate-bess-fat-pw-bgp-00.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].

Authors

Keyur Patel (keyupate@cisco.com)
Sami Boutros (sboutros@cisco.com)
Jose Liste (jliste@cisco.com)
Bin Wen (bin_wen@cable.comcast.com)
Jorge Rabadan (jorge.rabadan@alcatel-lucent.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)