RFC 6905: Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)

Operations, Administration, and Maintenance (OAM) is a general term used to identify functions and toolsets to troubleshoot and monitor networks. This…

Read RFC 6905 on the RFC Editor

Outgoing relationships (9 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 6291: Guidelines for the Use of the "OAM" Acronym in the IETF
Informative reference — RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
Informative reference — RFC 2679: A One-way Delay Metric for IPPM
Informative reference — RFC 2680: A One-way Packet Loss Metric for IPPM
Informative reference — RFC 2681: A Round-trip Delay Metric for IPPM
Informative reference — RFC 5860: Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks
Informative reference — RFC 4377: Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks
Informative reference — RFC 5960: MPLS Transport Profile Data Plane Architecture

Incoming relationships (4 related RFCs)

Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
Informatively referenced by — RFC 7455: Transparent Interconnection of Lots of Links (TRILL): Fault Management
Informatively referenced by — RFC 7456: Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)
Informatively referenced by — RFC 7784: Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIB