Label Sharing for Fast PE Protection
draft-zhang-bess-label-sharing-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mingui Zhang , Peng Zhou, Donald E. Eastlake 3rd , Russ White | ||
Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a method to be used by VPN (Virtual Private Network) Service Providers to provide multi-homed CEs with fast protection of egress PEs. Egress PEs in a redundant group always share the same label in distribution of VPN routes of a VRF. A virtual Next Hop (vNH) in the IGP/MPLS backbone is created as the common end of LSP tunnels which would otherwise terminate at each egress PE. Primary and backup LSP tunnels ended at the vNH are set up by MPLS on the basis of existing Interior Gateway Protocol (IGP) Fast ReRoute (FRR) mechanisms. If the primary egress PE fails, the backup egress PE can recognize the "shared" VPN route label carried by the data packets. Therefore, the failure affected data packets can be smoothly rerouted to the backup PE for delivery without changing their VPN route label.
Authors
Mingui Zhang
Peng Zhou
Donald E. Eastlake 3rd
Russ White
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)