[ippm] RFC 9326 on In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
rfc-editor@rfc-editor.org Wed, 16 November 2022 00:18 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2969EC14F74E; Tue, 15 Nov 2022 16:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9UaU534u3Rt; Tue, 15 Nov 2022 16:17:55 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBFACC14CF0C; Tue, 15 Nov 2022 16:17:55 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id AF76E5DDD5F; Tue, 15 Nov 2022 16:17:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ippm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221116001755.AF76E5DDD5F@rfcpa.amsl.com>
Date: Tue, 15 Nov 2022 16:17:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/knhP1cPBGgsTgBZ7CJqWw0IuVOY>
Subject: [ippm] RFC 9326 on In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2022 00:18:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9326
Title: In Situ Operations, Administration, and
Maintenance (IOAM) Direct Exporting
Author: H. Song,
B. Gafni,
F. Brockners,
S. Bhandari,
T. Mizrahi
Status: Standards Track
Stream: IETF
Date: November 2022
Mailbox: haoyu.song@futurewei.com,
gbarak@nvidia.com,
fbrockne@cisco.com,
shwetha.bhandari@thoughtspot.com,
tal.mizrahi.phd@gmail.com
Pages: 13
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ippm-ioam-direct-export-11.txt
URL: https://www.rfc-editor.org/info/rfc9326
DOI: 10.17487/RFC9326
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 (denoted IOAM-Option-Type) called the "IOAM
Direct Export (DEX) Option-Type". This Option-Type 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.
This document is a product of the IP Performance Measurement Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC