Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile
RFC 6428
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Continuity Check, Proactive Connectivity Verification, and Remote Defect Indication functionalities are required for MPLS Transport Profile … Received changes through RFC Editor sync (changed abstract to 'Continuity Check, Proactive Connectivity Verification, and Remote Defect Indication functionalities are required for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM). Continuity Check monitors a Label Switched Path for any loss of continuity defect. Connectivity Verification augments Continuity Check in order to provide confirmation that the desired source is connected to the desired sink. Remote Defect Indication enables an end point to report, to its associated end point, a fault or defect condition that it detects on a pseudowire, Label Switched Path, or Section. This document specifies specific extensions to Bidirectional Forwarding Detection (BFD) and methods for proactive Continuity Check, Continuity Verification, and Remote Defect Indication for MPLS-TP pseudowires, Label Switched Paths, and Sections using BFD as extended by this memo. [STANDARDS-TRACK]') |
2017-05-16
|
(System) | Changed document authors from "David Allan" to "David Allan, George Swallow, John Drake" |
2015-10-14
|
(System) | Notify list changed from mpls-chairs@ietf.org, draft-ietf-mpls-tp-cc-cv-rdi@ietf.org to (None) |
2011-11-16
|
Cindy Morgan | State changed to RFC Published from RFC Ed Queue. |
2011-11-16
|
(System) | RFC published |