Requirements for In-situ OAM
draft-brockners-inband-oam-requirements-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Frank Brockners , Shwetha Bhandari , Sashank Dara , Carlos Pignataro , Hannes Gredler , John Leddy , Stephen Youell , David Mozes , Tal Mizrahi , Petr Lapukhov <>, remy@barefootnetworks.com | ||
Last updated | 2017-09-14 (Latest revision 2017-03-13) | ||
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
This document discusses the motivation and requirements for including specific operational and telemetry information into data packets while the data packet traverses a path between two points in the network. This method is referred to as "in-situ" Operations, Administration, and Maintenance (OAM), given that the OAM information is carried with the data packets as opposed to in "out-of-band" packets dedicated to OAM. In situ OAM complements other OAM mechanisms which use dedicated probe packets to convey OAM information.
Authors
Frank Brockners
Shwetha Bhandari
Sashank Dara
Carlos Pignataro
Hannes Gredler
John Leddy
Stephen Youell
David Mozes
Tal Mizrahi
Petr Lapukhov <>
remy@barefootnetworks.com
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)