[ippm] RFC 9359 on Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
rfc-editor@rfc-editor.org Fri, 07 April 2023 22:54 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 2BD5AC15C294; Fri, 7 Apr 2023 15:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.647
X-Spam-Level:
X-Spam-Status: No, score=-6.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 ogGcAvbxTFGJ; Fri, 7 Apr 2023 15:54:54 -0700 (PDT)
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 EFAFCC151532; Fri, 7 Apr 2023 15:54:53 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C89177FDC0; Fri, 7 Apr 2023 15:54:53 -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: <20230407225453.C89177FDC0@rfcpa.amsl.com>
Date: Fri, 07 Apr 2023 15:54:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/SgKjPq1WXi2xcxdgi9jky1TFAkE>
Subject: [ippm] RFC 9359 on Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
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: Fri, 07 Apr 2023 22:54:58 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9359 Title: Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities Author: X. Min, G. Mirsky, L. Bo Status: Standards Track Stream: IETF Date: April 2023 Mailbox: xiao.min2@zte.com.cn, gregimirsky@gmail.com, leibo@chinatelecom.cn Pages: 17 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ippm-ioam-conf-state-10.txt URL: https://www.rfc-editor.org/info/rfc9359 DOI: 10.17487/RFC9359 This document describes a generic format for use in echo request/reply mechanisms, which can be used within an IOAM-Domain, allowing the IOAM encapsulating node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node. The generic format is intended to be used with a variety of data planes such as IPv6, MPLS, Service Function Chain (SFC), and Bit Index Explicit Replication (BIER). 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