The Pseudowire (PW) & Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results
draft-delregno-pw-vccv-impl-survey-results-00

Document Type Expired Internet-Draft (individual)
Last updated 2011-03-08
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-delregno-pw-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

Nick Regno (nick.delregno@verizon.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)