Additional data fields for IOAM Trace Option Types
draft-gafni-ippm-ioam-additional-data-fields-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Barak Gafni , Hongqiang H. Liu , Rui Miao , Mickey Spiegel | ||
Last updated | 2021-05-06 (Latest revision 2020-11-02) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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 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
Hongqiang H. Liu
Rui Miao
Mickey Spiegel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)