Skip to main content

In Situ OAM Profiles
draft-mizrahi-ippm-ioam-profile-06

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Tal Mizrahi , Frank Brockners , Shwetha Bhandari , Ramesh Sivakolundu , Carlos Pignataro , Aviv Kfir , Barak Gafni , Mickey Spiegel , Tianran Zhou
Last updated 2022-08-21 (Latest revision 2022-02-17)
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

In Situ Operations, Administration and Maintenance (IOAM) is used for monitoring network performance and for detecting traffic bottlenecks and anomalies. This is achieved by incorporating IOAM data into in- flight data packets. This document introduces the concept of use case-driven IOAM profiles. An IOAM profile defines a use case or a set of use cases for IOAM, and an associated set of rules that restrict the scope and features of the IOAM specification, thereby limiting it to a subset of the full functionality. The motivation for defining profiles is to limit the scope of IOAM features, allowing simpler implementation, verification, and interoperability testing in the context of specific use cases that do not require the full functionality of IOAM.

Authors

Tal Mizrahi
Frank Brockners
Shwetha Bhandari
Ramesh Sivakolundu
Carlos Pignataro
Aviv Kfir
Barak Gafni
Mickey Spiegel
Tianran Zhou

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)