Pseudo Wire Protection
draft-pan-pwe3-protection-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ping Pan | ||
| Last updated | 2006-07-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 mechanism that helps to protect and recover user traffic when carried over pseudo-wires. The mechanism requires some minor modification to the existing pseudo-wire setup procedure, and is fully backward compatible. The proposed mechanism allows the network operators to setup one or multiple backup pseudo-wires to protect a working pseudo-wire. Upon network failure, user traffic can be switched over to the next "best" pseudo-wire base on preference levels. This document first describes the motivation of the work base on the discussions with a number of carriers. Then we define the protocol extension itself.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)