In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active Flags
draft-ietf-ippm-ioam-flags-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ippm-ioam-flags@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, martin.h.duke@gmail.com, rfc-editor@rfc-editor.org, tpauly@apple.com
Subject: Protocol Action: 'In-situ OAM Loopback and Active Flags' to Proposed Standard (draft-ietf-ippm-ioam-flags-10.txt)

The IESG has approved the following document:
- 'In-situ OAM Loopback and Active Flags'
  (draft-ietf-ippm-ioam-flags-10.txt) as Proposed Standard

This document is the product of the IP Performance Measurement Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-flags/

Ballot Text

Technical Summary

   In-situ Operations, Administration, and Maintenance (IOAM) collects
   operational and telemetry information in packets while they traverse
   a path between two points in the network.  This document defines two
   new flags in the IOAM Trace Option headers, specifically the Loopback
   and Active flags.


Working Group Summary

This document has been in progress for several years. There was significant
discussion about amplification attacks, and during development the "direct
export" mode was peeled off into a separate document. The main work of the WG
on this document over the past year has been to work on the security
considerations to put bounds on the use of the flags. The WG did come to
consensus.

Document Quality

The document does have input and implementation support from many vendors.
We received SECDIR and TSVART reviews, which were valuable.

Personnel

The Document Shepherd is Tommy Pauly. The Responsible AD is Martin Duke.

RFC Editor Note