In-situ OAM raw data export with IPFIX
draft-spiegel-ippm-ioam-rawexport-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mickey Spiegel , Frank Brockners , Shwetha Bhandari , Ramesh Sivakolundu | ||
| Last updated | 2020-09-10 (Latest revision 2020-03-09) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 discusses how In-situ Operations, Administration, and Maintenance (IOAM) information can be exported in raw, i.e. uninterpreted, format from network devices to systems, such as monitoring or analytics systems using IPFIX.
Authors
Mickey Spiegel
Frank Brockners
Shwetha Bhandari
Ramesh Sivakolundu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)