Last Call: <draft-ietf-ippm-ioam-data-integrity-16.txt> (Integrity Protection of In Situ Operations, Administration, and Maintenance (IOAM) Data Fields) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 24 February 2026 15:29 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.6.246] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 70394BD2E81D; Tue, 24 Feb 2026 07:29:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-ippm-ioam-data-integrity-16.txt> (Integrity Protection of In Situ Operations, Administration, and Maintenance (IOAM) Data Fields) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 12.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <177194698139.2203295.8594588337318387522@dt-datatracker-6ff7c68975-7k42g>
Date: Tue, 24 Feb 2026 07:29:41 -0800
Message-ID-Hash: DSTLQTHQ3BCF4QSTNCUCWS5SAODNAK25
X-Message-ID-Hash: DSTLQTHQ3BCF4QSTNCUCWS5SAODNAK25
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-ippm-ioam-data-integrity@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, mohamed.boucadair@orange.com
X-Mailman-Version: 3.3.9rc6
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/cHYepJLNmJHwmq9wRZhuvPK_1RY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

The IESG has received a request from the IP Performance Measurement WG (ippm)
to consider the following document: - 'Integrity Protection of In Situ
Operations, Administration, and
   Maintenance (IOAM) Data Fields'
  <draft-ietf-ippm-ioam-data-integrity-16.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2026-03-10. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   In Situ Operations, Administration, and Maintenance (IOAM) records
   operational (including telemetry) information in packets while they
   traverse a path in the network.  RFC 9197 specifies data fields for
   IOAM (a.k.a IOAM-Data-Fields) and associated data types.  This
   document specifies integrity protection of IOAM-Data-Fields for
   Intra-IOAM-Domain use cases.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-data-integrity/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/5815/