Data Fields for In-situ OAM

The information below is for an old version of the document
Document Type None Internet-Draft (ippm WG)
Last updated 2019-09-11 (latest revision 2019-07-04)
Replaces draft-ippm-ioam-data, draft-brockners-inband-oam-data
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Additional URLs
- Mailing list discussion
Stream WG state (None)
Document shepherd Al Morton
IESG IESG state Unknown state
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Al Morton <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for in-situ OAM. In-situ OAM data fields can be embedded into a variety of transports such as NSH, Segment Routing, Geneve, native IPv6 (via extension header), or IPv4. In-situ OAM can be used to complement OAM mechanisms based on e.g. ICMP or other types of probe packets.


Frank Brockners (
Shwetha Bhandari (
Carlos Pignataro (
Hannes Gredler (
John Leddy (
Stephen Youell (
Tal Mizrahi (
David Mozes (
Petr Lapukhov (
Remy Chang (unknown-email-Remy-Chang) (
John Lemon (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)