Skip to main content

Supporting In-Situ Operations, Administration, and Maintenance Direct Export Using MPLS Network Actions
draft-mb-mpls-ioam-dex-09

Document Type Replaced Internet-Draft (mpls WG)
Expired & archived
Authors Greg Mirsky , Mohamed Boucadair , Tony Li
Last updated 2024-10-21
Replaced by draft-ietf-mpls-mna-ioam
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state Candidate for WG Adoption
Document shepherd Nicolai Leymann
IESG IESG state Replaced by draft-ietf-mpls-mna-ioam
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to n.leymann@telekom.de

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), defined in RFC 9197, is an on-path telemetry method to collect and transport the operational state and telemetry information that can be used to calculate various performance metrics. IOAM Direct Export (IOAM-DEX) is one of the IOAM Option types, in which the operational state and telemetry information are collected according to the specified profile and exported in a manner and format defined by a local policy. MPLS Network Actions (MNA) techniques are meant to indicate actions to be performed on any combination of Label Switched Paths (LSPs), MPLS packets, and the node itself, and also to transfer data needed for these actions. This document explores the on-path operational state, and telemetry information can be collected using IOAM-DEX Option in combination with MNA.

Authors

Greg Mirsky
Mohamed Boucadair
Tony Li

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