RFC 5885: Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)
In plain English — editorial summary, not part of the RFC
This document describes Connectivity Verification (CV) Types using Bidirectional Forwarding Detection (BFD) with Virtual Circuit Connectivity Verification (VCCV). VCCV 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5885
- Published
- June 2010
- Authors
- T. Nadeau; C. Pignataro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5542Definitions of Textual Conventions for Pseudowire (PW) ManagementCurrent
May 2009
- RFC 6310Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message MappingCurrent
July 2011
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 5254Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)Current
October 2008
- RFC 5087Time Division Multiplexing over IP (TDMoIP)Current
December 2007
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
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?