RFC 10014: Guidelines for Characterizing the Term "OAM"
As the IETF continues to produce and standardize different Operations, Administration, and Maintenance (OAM) protocols and technologies, various qualifiers…
Read RFC 10014 on the RFC Editor
Outgoing relationships (15 related RFCs)
- Updates, Normative reference — RFC 6291: Guidelines for the Use of the "OAM" Acronym in the IETF
- Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
- Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
- Normative reference — RFC 7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between)
- Informative reference — RFC 5880: Bidirectional Forwarding Detection (BFD)
- Informative reference — RFC 5085: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires
- Informative reference — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
- Informative reference — RFC 6374: Packet Loss and Delay Measurement for MPLS Networks
- Informative reference — RFC 9197: Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)
- Informative reference — RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
- Informative reference — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
- Informative reference — RFC 9341: Alternate-Marking Method
- Informative reference — RFC 6669: An Overview of the Operations, Administration, and Maintenance (OAM) Toolset for MPLS-Based Transport Networks
- Informative reference — RFC 9551: Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)
- Informative reference — RFC 9232: Network Telemetry Framework