MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Gyan Mishra via Datatracker <noreply@ietf.org>
To: <rtg-dir@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: 
 <178952091564.994052.7561692262583779771@dt-datatracker-597c8c8754-4t7c8>
Date: Tue, 15 Sep 2026 18:08:35 -0700
Message-ID-Hash: HQJBPEMCHVEI3QW5OX3AQBOOIWHYBYJK
CC: draft-ietf-mpls-on-path-telemetry-flag.all@ietf.org, mpls@ietf.org
Reply-To: Gyan Mishra <hayabusagsm@gmail.com>
Subject: [mpls] draft-ietf-mpls-on-path-telemetry-flag-03 early Rtgdir review
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/mpls/gK5Fl0q_-im-2aYfpQZQ3-o-AtE>

Document: draft-ietf-mpls-on-path-telemetry-flag
Title: MPLS On-Path Telemetry Network Action Flag for OAM
Reviewer: Gyan Mishra
Review result: Ready

Summary:

This document describes postcard-based on-path telemetry with packet marking
(PBT-M) using an MPLS Network Actions (MNA) flag to support Operations,
Administration, and Maintenance (OAM) in MPLS networks. The scheme uses a
single flag bit carried in a Flag-Based Network Action Indicator (Opcode 1) of
the MNA Sub-Stack as defined in RFC 9994. In addition to addressing the
protocol requirements for applying PBT-M, this document provides comprehensive
operational, manageability, and security considerations.

I have reviewed the last version 10 of the draft and I don’t see any issues and
believe the draft is ready for publication.

Minor issues:
None

Major issues:
None

Nits:
None