[mpls] Fwd: I-D Action: draft-ietf-mpls-mna-ioam-08.txt

Rakesh Gandhi <rgandhi.ietf@gmail.com> Wed, 29 July 2026 13:33 UTC

MIME-Version: 1.0
References: <178526380649.1237603.3360151558499706271@dt-datatracker-d4d6ff9d9-fsx7d>
In-Reply-To: <178526380649.1237603.3360151558499706271@dt-datatracker-d4d6ff9d9-fsx7d>
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Date: Wed, 29 Jul 2026 09:33:16 -0400
Message-ID: <CAMZsk6cpdLdtUF7Z+wRA=x1DrFr-ZKCaxYk+G+aHo3RQFUL+GA@mail.gmail.com>
To: draft-ietf-mpls-mna-ioam@ietf.org, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000020b2150657c00023"
Message-ID-Hash: MH7GR6JGDSRRFZDHFJ3PRWYKLLCWGJPJ
Precedence: list
Subject: [mpls] Fwd: I-D Action: draft-ietf-mpls-mna-ioam-08.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Q2rvsYU4Sqso3KU4hsmAY-GSbg8>

Hi MPLS WG,

This revision addresses the comments from Giuseppe for Perfmetrdir review.

In addition, the description is added for opcode TBA1 that it is added in
ISD to specify the processing order within the NAS with other network
actions (as shown in Example 9.1).

The data for opcode TBA1 in ISD does not carry PSD offset to avoid
confusion with the PSD offset opcode (TBA1) in *draft-ietf-mpls-mna-ps-hdr.*

Welcome your review comments and suggestions.

Thanks,
Rakesh (for authors)



---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Jul 28, 2026 at 2:37 PM
Subject: [mpls] I-D Action: draft-ietf-mpls-mna-ioam-08.txt
To: <i-d-announce@ietf.org>
Cc: <mpls@ietf.org>


Internet-Draft draft-ietf-mpls-mna-ioam-08.txt is now available. It is a
work
item of the Multiprotocol Label Switching (MPLS) WG of the IETF.

   Title:   Supporting In Situ Operations, Administration, and Maintenance
Using MPLS Network Actions
   Authors: Rakesh Gandhi
            Greg Mirsky
            Haoyu Song
            Bin Wen
            Voitek Kozak
   Name:    draft-ietf-mpls-mna-ioam-08.txt
   Pages:   21
   Dates:   2026-07-28

Abstract:

   In situ Operations, Administration, and Maintenance (IOAM), defined
   in RFC 9197, is an on-path telemetry method to collect and record the
   operational state and telemetry information using, for example, Pre-
   allocated Trace, Proof-of-Transit, Edge-to-Edge, or Incremental Trace
   Option-Types that can be used to calculate various performance
   metrics.  RFC 9326 defines the IOAM Direct Export (IOAM-DEX) Option-
   Type 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 on each node along the path.

   MPLS Network Actions (MNA) techniques are meant to indicate actions
   to be performed on any combination of Label Switched Paths, MPLS
   packets, and the node itself, and to transport data needed for these
   actions.  This document employs the MNA mechanisms to collect and
   transport the on-path operational state and telemetry information
   using IOAM data fields as well as direct export.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-ioam/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-mpls-mna-ioam-08.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-mpls-mna-ioam-08

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
mpls mailing list -- mpls@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org

[mpls] I-D Action: draft-ietf-mpls-mna-ioam-08.txt internet-drafts
[mpls] Fwd: I-D Action: draft-ietf-mpls-mna-ioam-… Rakesh Gandhi