Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
RFC 9359
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-07-08
|
(System) | IANA registries were updated to include RFC9359 |
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['IPv6', 'MPLS', 'SFC', 'BIER']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "L. Bo": changed name from "Lei Bo" to "L. Bo", cleared country (was "China") |
|
2026-05-20
|
(System) | Changed author "G. Mirsky": changed name from "Greg Mirsky" to "G. Mirsky", cleared country (was "United States of America") |
|
2026-05-20
|
(System) | Changed author "X. Min": changed name from "Xiao Min" to "X. Min", cleared country (was "China") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2025-03-28
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2024-04-23
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2023-04-07
|
(System) | Received changes through RFC Editor sync (created alias RFC 9359, changed title to 'Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities', changed abstract … Received changes through RFC Editor sync (created alias RFC 9359, changed title to 'Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities', changed abstract to '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 node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node. The generic format is intended to be used with a variety of data planes such as IPv6, MPLS, Service Function Chain (SFC), and Bit Index Explicit Replication (BIER).', changed pages to 17, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-04-07, changed IESG state to RFC Published) |
|
2023-04-07
|
(System) | RFC published |