[rfc-dist] RFC 9486 on IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)
rfc-editor@rfc-editor.org Fri, 29 September 2023 19:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E1FC151717; Fri, 29 Sep 2023 12:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, 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 T3ypbjXVLLa8; Fri, 29 Sep 2023 12:38:02 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 DA61CC1519A6; Fri, 29 Sep 2023 12:38:02 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D03CC76354; Fri, 29 Sep 2023 12:38:02 -0700 (PDT)
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: <20230929193802.D03CC76354@rfcpa.amsl.com>
Date: Fri, 29 Sep 2023 12:38:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/8t_DXWVxI5eTiGbt-_MuNwExAsk>
Subject: [rfc-dist] RFC 9486 on IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2023 19:38:03 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9486 Title: IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) Author: S. Bhandari, Ed., F. Brockners, Ed. Status: Standards Track Stream: IETF Date: September 2023 Mailbox: shwetha.bhandari@thoughtspot.com, fbrockne@cisco.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ippm-ioam-ipv6-options-12.txt URL: https://www.rfc-editor.org/info/rfc9486 DOI: 10.17487/RFC9486 In situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document outlines how IOAM Data-Fields are encapsulated in IPv6. 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