Data Fields for In-situ OAM

Document Type Replaced Internet-Draft (individual)
Authors Frank Brockners  , Shwetha Bhandari  , Carlos Pignataro  , Hannes Gredler  , John Leddy  , Stephen Youell  , Tal Mizrahi  , David Mozes  , Petr Lapukhov  , Remy Chang , Daniel Bernier 
Last updated 2017-07-03
Replaced by draft-ippm-ioam-data, draft-ietf-ippm-ioam-data
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ippm-ioam-data, draft-ietf-ippm-ioam-data
Telechat date
Responsible AD (None)
Send notices to (None)

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)
Daniel Bernier (

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