RFC 9359: Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities

This document describes a generic format for use in echo request/reply mechanisms, which can be used within an IOAM-Domain, allowing the IOAM encapsulating…

Read RFC 9359 on the RFC Editor

Outgoing relationships (13 related RFCs)

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 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 9197: Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)
Normative reference — RFC 9326: In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
Informative reference — RFC 4303: IP Encapsulating Security Payload (ESP)
Informative reference — RFC 4302: IP Authentication Header
Informative reference — RFC 4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Informative reference — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
Informative reference — RFC 4884: Extended ICMP to Support Multi-Part Messages
Informative reference — RFC 8799: Limited Domains and Internet Protocols
Informative reference — RFC 4620: IPv6 Node Information Queries
Informative reference — RFC 8335: PROBE: A Utility for Probing Interfaces

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9378: In Situ Operations, Administration, and Maintenance (IOAM) Deployment