Geneve encapsulation for In-situ OAM Data
draft-brockners-nvo3-ioam-geneve-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-05-03 (latest revision 2017-10-30) | ||
| 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-brockners-nvo3-ioam-geneve-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 Geneve.
Authors
Frank Brockners
(fbrockne@cisco.com)
Shwetha Bhandari
(shwethab@cisco.com)
Vengada Govindan
(venggovi@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)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)