RFC 7455: Transparent Interconnection of Lots of Links (TRILL): Fault Management
In plain English — editorial summary, not part of the RFC
This document specifies Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) fault management. Methods in this document follow the CFM (Connectivity Fault Management) framework defined in IEEE 802.1 and reuse OAM tools where possible. Additional messages and TLVs are defined for TRILL-specific applications or for cases where a different set of information is required other than CFM as defined in IEEE 802.1. This document updates RFC 6325.
Document record
- Document ID
- RFC7455
- Published
- March 2015
- Authors
- T. Senevirathne; N. Finn; S. Salam; D. Kumar; D. Eastlake 3rd; S. Aldrin; Y. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 63
- Also known as
- —
- Updates:
- RFC 6325
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7174Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) FrameworkCurrent
May 2014
- RFC 7319IANA Considerations for Connectivity Fault Management (CFM) Code PointsCurrent
July 2014
- RFC 7784Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIBCurrent
February 2016
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7571GMPLS RSVP-TE Extensions for Lock Instruct and LoopbackCurrent
July 2015
- RFC 7759Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) PingCurrent
February 2016
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
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?