MS-PW based L2VPN provisioning, auto-discovery, signaling
draft-jounay-delord-l2vpn-ms-pw-provisioning-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Philippe Niger , Simon DeLord , Yuji Kamite , Mark Latham | ||
| Last updated | 2010-01-08 | ||
| 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
Service Providers (SPs) have described the requirements to allow them to extend the Pseudowires (PWs) across multiple domains via the use of multi-segment Pseudowires (MS-PWs). Several tools relating to provisioning, auto-discovery and signaling have been developed to allow the dynamic setup of MS-PWs. However there is no end to end view that describes how these tools can be used in carrier networks. This document aims at providing this view by describing the different stages required for an end to end L2VPN service setup relying on MS-PWs. These stages are VPN provisioning, auto-discovery (network and service), signaling and monitoring.
Authors
Philippe Niger
Simon DeLord
Yuji Kamite
Mark Latham
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)