Skip to main content

Data Fields for In-situ OAM
draft-brockners-inband-oam-data-07

Document Type Replaced Internet-Draft (individual)
Expired & archived
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
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ippm-ioam-data, draft-ippm-ioam-data
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

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.

Authors

Frank Brockners
Shwetha Bhandari
Carlos Pignataro
Hannes Gredler
John Leddy
Stephen Youell
Tal Mizrahi
David Mozes
Petr Lapukhov
Remy Chang
Daniel Bernier

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