Additional data fields for IOAM Trace Option Types
draft-gafni-ippm-ioam-additional-data-fields-00

Document Type Expired Internet-Draft (individual)
Authors Barak Gafni  , Hongqiang Liu  , Rui Miao  , Mickey Spiegel 
Last updated 2021-05-06 (latest revision 2020-11-02)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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
https://www.ietf.org/archive/id/draft-gafni-ippm-ioam-additional-data-fields-00.txt

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 additional data fields and associated data types to be added to the IOAM data fileds described in [I-D.ietf-ippm-ioam-data]. In-situ OAM data fields can be encapsulated into a variety of protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension header), or IPv4.

Authors

Barak Gafni (gbarak@nvidia.com)
Hongqiang Liu (hongqiang.liu@alibaba-inc.com)
Rui Miao (miao.rui@alibaba-inc.com)
Mickey Spiegel (mickey.spiegel@intel.com)

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