Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 6428

Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile,November 2011

File formats:
icon for text fileicon for PDFicon for HTMLicon for inline errata
Status:
PROPOSED STANDARD
Updated by:
RFC 7214
Authors:
D. Allan, Ed.
G. Swallow, Ed.
J. Drake, Ed.
Stream:
IETF
Source:
mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6428

Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6428


Abstract

Continuity Check, Proactive Connectivity Verification, and RemoteDefect Indication functionalities are required for MPLS TransportProfile (MPLS-TP) Operations, Administration, and Maintenance (OAM).

Continuity Check monitors a Label Switched Path for any loss of continuitydefect. Connectivity Verification augments Continuity Checkin order to provide confirmation that the desired source is connectedto the desired sink. Remote Defect Indication enables an end point toreport, to its associated end point, a fault or defect condition thatit detects on a pseudowire, Label Switched Path, or Section.

This document specifies specific extensions to BidirectionalForwarding Detection (BFD) and methods forproactive Continuity Check, Continuity Verification, and Remote DefectIndication for MPLS-TP pseudowires, Label Switched Paths, and Sectionsusing BFD as extended by this memo. [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp