RFC 7079: The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results
In plain English — editorial summary, not part of the RFC
The IETF Pseudowire Emulation Edge-to-Edge (PWE3) working group has defined many encapsulations of various layer 1 and layer 2 service- specific PDUs and circuit data. In most of these encapsulations, use of the Pseudowire (PW) Control Word is required. However, there are several encapsulations for which the Control Word is optional, and this optionality has been seen in practice to possibly introduce interoperability concerns between multiple implementations of those encapsulations. This survey of the Pseudowire / Virtual Circuit Connectivity Verification (VCCV) user community was conducted to determine implementation trends and the possibility of always mandating the Control Word.
Document record
- Document ID
- RFC7079
- Published
- November 2013
- Authors
- N. Del Regno; A. Malis
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7080Virtual Private LAN Service (VPLS) Interoperability with Provider Backbone BridgesCurrent
December 2013
- RFC 7074Revised Definition of the GMPLS Switching Capability and Type FieldsCurrent
November 2013
- RFC 7087A Thesaurus for the Interpretation of Terminology Used in MPLS Transport Profile (MPLS-TP) Internet-Drafts and RFCs in the Context of the ITU-T's Transport Network RecommendationsCurrent
December 2013
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 7063Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and DeploymentsCurrent
December 2013
- RFC 7062Framework for GMPLS and PCE Control of G.709 Optical Transport NetworksCurrent
November 2013
- RFC 7096Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)Current
January 2014
- RFC 7060Using LDP Multipoint Extensions on Targeted LDP SessionsCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?