Data Fields for In-situ OAM
draft-brockners-inband-oam-data-07
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-07-03 | ||
| Replaced by | draft-ippm-ioam-data, draft-ietf-ippm-ioam-data | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ippm-ioam-data, draft-ietf-ippm-ioam-data | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-brockners-inband-oam-data-07.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 the data fields and associated data types for in-situ OAM. In-situ OAM data fields can be embedded into a variety of transports such as NSH, Segment Routing, Geneve, native IPv6 (via extension header), or IPv4. In-situ OAM can be used to complement OAM mechanisms based on e.g. ICMP or other types of probe packets.
Authors
Frank Brockners
(fbrockne@cisco.com)
Shwetha Bhandari
(shwethab@cisco.com)
Carlos Pignataro
(cpignata@cisco.com)
Hannes Gredler
(hannes@rtbrick.com)
John Leddy
(john_leddy@cable.comcast.com)
Stephen Youell
(stephen.youell@jpmorgan.com)
Tal Mizrahi
(talmi@marvell.com)
David Mozes
(davidm@mellanox.com)
Petr Lapukhov
(petr@fb.com)
Remy Chang
(unknown-email-Remy-Chang)
daniel.bernier@bell.ca
(daniel.bernier@bell.ca)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)