Re: [ippm] Fwd: RFC 9359 on Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
xiao.min2@zte.com.cn Mon, 10 April 2023 02:49 UTC
Return-Path: <xiao.min2@zte.com.cn>
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 E2A60C151B01 for <ippm@ietfa.amsl.com>; Sun, 9 Apr 2023 19:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 H1O4crAhl-LG for <ippm@ietfa.amsl.com>; Sun, 9 Apr 2023 19:49:46 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9F60C15155F for <ippm@ietf.org>; Sun, 9 Apr 2023 19:49:45 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4Pvtjg62pSz8R04D for <ippm@ietf.org>; Mon, 10 Apr 2023 10:49:43 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4Pvtj55QTdz501RP; Mon, 10 Apr 2023 10:49:13 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl1.zte.com.cn with SMTP id 33A2n6OR020559; Mon, 10 Apr 2023 10:49:06 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njy2app01[null]) by mapi (Zmail) with MAPI id mid201; Mon, 10 Apr 2023 10:49:07 +0800 (CST)
Date: Mon, 10 Apr 2023 10:49:07 +0800
X-Zmail-TransId: 2af964337923ffffffffeec-85e76
X-Mailer: Zmail v1.0
Message-ID: <202304101049077139651@zte.com.cn>
In-Reply-To: <CA+RyBmXa6XFzFOv4xgCSBm9egso6P+vU+tH2_WgG-WjBka1Hrg@mail.gmail.com>
References: 20230407225453.C89177FDC0@rfcpa.amsl.com, CA+RyBmXa6XFzFOv4xgCSBm9egso6P+vU+tH2_WgG-WjBka1Hrg@mail.gmail.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: gregimirsky@gmail.com
Cc: ippm@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 33A2n6OR020559
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 64337947.001/4Pvtjg62pSz8R04D
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Q1kjnpiB2GPSBjQjTHJTSkvGKBY>
Subject: Re: [ippm] Fwd: 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: Mon, 10 Apr 2023 02:49:51 -0000
Same here, a pleasant journey. :-)
Looking forward to more collaborations with you Greg.
Best Regards,
Xiao Min
Original
From: GregMirsky <gregimirsky@gmail.com>
To: 肖敏10093570;IETF IPPM WG <ippm@ietf.org>;
Date: 2023年04月08日 07:52
Subject: Fwd: [ippm] RFC 9359 on Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
Congratulations, Xiao Min! It's been a pleasure working with you.
Regards,
Greg
---------- Forwarded message ---------
From: <rfc-editor@rfc-editor.org>
Date: Fri, Apr 7, 2023 at 3:57 PM
Subject: [ippm] RFC 9359 on Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
To: <ietf-announce@ietf.org>, <rfc-dist@rfc-editor.org>
Cc: <rfc-editor@rfc-editor.org>, <drafts-update-ref@iana.org>, <ippm@ietf.org>
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
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm