In-situ OAM IPv4 Options
draft-gafni-ippm-ioam-ipv4-options-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Barak Gafni , Aviv Kfir , Shwetha Bhandari , Frank Brockners , Ramesh Sivakolundu , Tal Mizrahi | ||
| Last updated | 2019-09-10 (Latest revision 2019-03-09) | ||
| 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 outlines how IOAM data fields are encapsulated in IPv4.
Authors
Barak Gafni
Aviv Kfir
Shwetha Bhandari
Frank Brockners
Ramesh Sivakolundu
Tal Mizrahi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)