The Pseudowire (PW) & Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results
draft-ietf-pwe3-vccv-impl-survey-results-00
| Document | Type | Expired Internet-Draft (pwe3 WG) | |
|---|---|---|---|
| Author | Nick Del Regno | ||
| Last updated | 2012-12-15 (Latest revision 2012-04-17) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
pdf
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Last Call review
(of
-02)
Almost Ready
|
||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Matthew Bocci | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Stewart Bryant | ||
| IESG note | The document shepherd is Matthew Bocci (matthew.bocci@alcatel-lucent.com). | ||
| Send notices to | pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-vccv-impl-survey-results@tools.ietf.org |
https://www.ietf.org/archive/id/draft-ietf-pwe3-vccv-impl-survey-results-00.txt
Abstract
Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate the use of the Control Word (CW) in order to better emulate the services for which the encapsulations have been defined. However, some encapulations treat the Control Word as optional. As a result, implementations of the CW, for encapsulations for which it is optional, vary by equipment manufacturer, equipment model and service provider network. Similarly, Virtual Circuit Connectivity Verification (VCCV) supports three Control Channel (CC) types and multiple Connectivity Verification (CV) Types. This flexibility has led to reports of interoperability issues within deployed networks and associated drafts to attempt to remedy the situation. This survey of the PW/VCCV user community was conducted to determine implementation trends. The survey and results is presented herein.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)