In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
draft-ietf-ippm-ioam-direct-export-11

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-direct-export@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 Direct Exporting' to Proposed Standard (draft-ietf-ippm-ioam-direct-export-11.txt)

The IESG has approved the following document:
- 'In-situ OAM Direct Exporting'
  (draft-ietf-ippm-ioam-direct-export-11.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-direct-export/

Ballot Text

Technical Summary

   In-situ Operations, Administration, and Maintenance (IOAM) is used
   for recording and collecting operational and telemetry information.
   Specifically, IOAM allows telemetry data to be pushed into data
   packets while they traverse the network.  This document introduces a
   new IOAM option type called the Direct Export (DEX) option, which is
   used as a trigger for IOAM data to be directly exported or locally
   aggregated without being pushed into in-flight data packets.  The
   exporting method and format are outside the scope of this document.

Working Group Summary

This document was peeled out of the IOAM flags extension document, after
discussion revealed that it needed more careful analysis to avoid various
amplification attacks (or accidental amplification). 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 direct export. The WG did come to
consensus after this review.

Document Quality

The document does have input and implementation support from many vendors.

Personnel

Tommy Pauly is the document shepherd.
Martin Duke is the Responsible Area Director.

RFC Editor Note