Mandatory Use of Control Word for PWE3 Encapsulations
draft-delregno-pwe3-mandatory-control-word-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nick Del Regno , Thomas Nadeau , Vishwas Manral , David Ward | ||
| Last updated | 2010-10-18 | ||
| 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
Of the many variations of PWE3 Encapsulations and Modes (e.g. Ethernet, Port Mode, VLAN Mode, etc), only five have the Control Word (CW) as being optional. As a result, this causes an issue with VCCV Control Channel selection. This draft endeavors to resolve the issue going forward by making the Control Word, and subsequently the CW- based VCCV Control Channel, mandatory for all PWE3 Encapsulations.
Authors
Nick Del Regno
Thomas Nadeau
Vishwas Manral
David Ward
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)