<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.pwe3-vccv-impl-survey-results" target="https://datatracker.ietf.org/doc/html/draft-pwe3-vccv-impl-survey-results-00">
   <front>
      <title>The Pseudowire (PW) &amp; Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results</title>
      <author initials="N. D." surname="Regno" fullname="Nick Del Regno">
         </author>
      <date month="September" day="20" year="2011" />
      <abstract>
	 <t>   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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-pwe3-vccv-impl-survey-results-00" />
   
</reference>
