In-situ OAM IPv4 Options
draft-gafni-ippm-ioam-ipv4-options-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-09-10 (latest revision 2019-03-09) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
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) | ||
https://www.ietf.org/archive/id/draft-gafni-ippm-ioam-ipv4-options-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 outlines how IOAM data fields are encapsulated in IPv4.
Authors
Barak Gafni
(gbarak@mellanox.com)
Aviv Kfir
(avivk@mellanox.com)
Shwetha Bhandari
(shwethab@cisco.com)
Frank Brockners
(fbrockne@cisco.com)
Ramesh Sivakolundu
(sramesh@cisco.com)
Tal Mizrahi
(tal.mizrahi.phd@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)