RFC 5085: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
In plain English — editorial summary, not part of the RFC
This document describes Virtual Circuit Connectivity Verification (VCCV), which provides a control channel that is associated with a pseudowire (PW), as well as the corresponding operations and management functions (such as connectivity verification) to be used over that control channel. VCCV applies to all supported access circuit and transport types currently defined for PWs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5085
- Published
- December 2007
- Authors
- T. Nadeau; C. Pignataro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 30
- Also known as
- —
- Updated by:
- RFC 5586
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4863Wildcard Pseudowire TypeCurrent
May 2007
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 2006
- RFC 5641Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status ValuesCurrent
August 2009
- RFC 4448Encapsulation Methods for Transport of Ethernet over MPLS NetworksUpdated
April 2006
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 7267Dynamic Placement of Multi-Segment PseudowiresCurrent
June 2014
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?