Variable Length Node Data Field Option for In-situ Operations, Administration, and Maintenance (IOAM)
draft-parikh-ioam-variable-length-field-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jainam Parikh , Carlos Pignataro , Alexander Clemm | ||
| Last updated | 2026-05-16 (Latest revision 2025-11-12) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
|
||
| 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
The purpose of this memo is to describe a new IOAM Node Data Field type, called Flex Field, for In-Situ Operations, Administration, and Maintenance (IOAM). This option type, under IOAM Trace Option-Types will allow one to append variable length node data in an IOAM packet, along a network path.
Authors
Jainam Parikh
Carlos Pignataro
Alexander Clemm
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)