Re: [ippm] 回复:Re: 回复:Re: update "draft-he-ippm-integrating-am-into-ioam"

xiao.min2@zte.com.cn Thu, 11 January 2024 02:18 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 B34A9C14CE42 for <ippm@ietfa.amsl.com>; Wed, 10 Jan 2024 18:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 2BnecKThPCcd for <ippm@ietfa.amsl.com>; Wed, 10 Jan 2024 18:18:31 -0800 (PST)
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 4F472C14CE30 for <ippm@ietf.org>; Wed, 10 Jan 2024 18:18:26 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4T9Sy65ltfz8XrRD for <ippm@ietf.org>; Thu, 11 Jan 2024 10:18:22 +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 4T9SxX56Q4z4xVbq; Thu, 11 Jan 2024 10:17:52 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl1.zte.com.cn with SMTP id 40B2Hj12048361; Thu, 11 Jan 2024 10:17:45 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Thu, 11 Jan 2024 10:17:46 +0800 (CST)
Date: Thu, 11 Jan 2024 10:17:46 +0800
X-Zmail-TransId: 2afe659f4fcaffffffffb2f-1f88b
X-Mailer: Zmail v1.0
Message-ID: <202401111017464367758@zte.com.cn>
In-Reply-To: <tencent_8EEDAC54F31E0334F6551B6AB388215F1808@qq.com>
References: tencent_8EEDAC54F31E0334F6551B6AB388215F1808@qq.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: xiaoming-he@foxmail.com
Cc: ippm@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 40B2Hj12048361
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 659F4FEE.000/4T9Sy65ltfz8XrRD
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/04ITgz7ssN7CVQqUhn7pDMef5rc>
Subject: Re: [ippm] 回复:Re: 回复:Re: update "draft-he-ippm-integrating-am-into-ioam"
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: Thu, 11 Jan 2024 02:18:33 -0000

Hi Xiaoming He,

Thanks for taking my suggestion into account.
Cheers,
Xiao Min


Original


From: XiaomingHe <xiaoming-he@foxmail.com>
To: 肖敏10093570;
Cc: ippm <ippm@ietf.org>;
Date: 2024年01月10日 23:00
Subject: 回复:Re: 回复:Re: [ippm] update "draft-he-ippm-integrating-am-into-ioam"




Hi, Xiao Min,Thank you very much for reminding me to think over this question.

As you said, it is possile to extend the IOAM Trace Option for  incorporating the Alternate-Marking method. The benefits obtained from this are that, while conducting performance measurements, we can still collect telemetry data of user traffic along the path nodes.

We will consider to add the extended IOAM Trace Option in this updated draft.

Best Regards,
Xiaoming He
China telecom










原始邮件



发件人:"xiao.min2"< xiao.min2@zte.com.cn >;
发件时间:2024/1/10 15:31
收件人:"xiaoming-he"< xiaoming-he@foxmail.com >;
抄送人:"ippm"< ippm@ietf.org >;
主题:Re: 回复:Re: [ippm] update "draft-he-ippm-integrating-am-into-ioam"





Hi Xiaoming,

Thank you for the detailed explanation.
I understand the logic you choose to extend IOAM DEX Option, nevertheless what's not clear to me is that how difficult while extending IOAM Trace Option.
As said before, I see the application scenario to combine IOAM Tracing with Alternate Marking, in which the IOAM transit node might need to do both packet stamping (so-called passport mode) and direct export (so-called postcard mode). At present I don't see a reason why the IOAM transit node can't do that, so I raise this option for you to consider.

Cheers,
Xiao Min








From: XiaomingHe <xiaoming-he@foxmail.com>
To: 肖敏10093570;
Cc: ippm <ippm@ietf.org>;
Date: 2024年01月09日 22:13
Subject: 回复:Re: [ippm] update "draft-he-ippm-integrating-am-into-ioam"



Hi, Xiao Min,
Thank you for the question and concern.

Regarding the IOAM Trace Option, a passport-based IOAM, I think it is difficult for its extension supporting Alternate Marking method.

Because in IOAM Trace Option mode, the IOAM data is pushed into data packets by every transit node until the IOAM decapsulating node  (destination node) removes IOAM-Option-Type from packets and send the IOAM data to a receiving entity for analysis.

The Alternate Marking method demands that the network support Hop-by-Hop option or End-to-End option. In  Hop-by-Hop mode,  packet drop and packet drop location can be monitored accurately (which hop the loss occurs) , and End-to-End mode can only monitor packet loss (from source to destination).

So, the IOAM DEX Option, also called the postcard mode, is quite suitable for incorporating the Alternate Marking method.



Best Regards,
Xiaoming





原始邮件



发件人:"xiao.min2"< xiao.min2@zte.com.cn >;
发件时间:2024/1/9 16:49
收件人:"xiaoming-he"< xiaoming-he@foxmail.com >;
抄送人:"ippm"< ippm@ietf.org >;
主题:Re: [ippm] update "draft-he-ippm-integrating-am-into-ioam"





Hi Xiaoming He, authors,

Thank you for the interesting draft.
While reading this draft, a question raised in my mind, is it possible to extend IOAM Trace Option except for IOAM DEX Option?
AFAIK, IOAM Trace Option and IOAM DEX Option have different application scenarios, so it seems to me it's helpful to combine IOAM Tracing with Alternate Marking when IOAM Trace Option is preferred.
Best Regards,
Xiao Min








From: XiaomingHe <xiaoming-he@foxmail.com>
To: IPPM WG <ippm@ietf.org>;
Date: 2024年01月08日 17:41
Subject: [ippm] update "draft-he-ippm-integrating-am-into-ioam"

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm



Hi, IPPM,



A new version of Internet-Draft draft-he-ippm-integrating-am-into-ioam-01.txt
has been successfully submitted by Xiaoming He and posted to the
IETF repository.

Name:     draft-he-ippm-integrating-am-into-ioam
Revision: 01
Title:    Integrating the Alternate-Marking Method into In Situ Operations, Administration, and Maintenance (IOAM)
Date:     2024-01-08
Group:    Individual Submission
Pages:    13
URL: https://www.ietf.org/archive/id/draft-he-ippm-integrating-am-into-ioam-01.txt
Status: https://datatracker.ietf.org/doc/draft-he-ippm-integrating-am-into-ioam/
HTMLized: https://datatracker.ietf.org/doc/html/draft-he-ippm-integrating-am-into-ioam
Diff: https://author-tools.ietf.org/iddiff?url2=draft-he-ippm-integrating-am-into-ioam-01

Abstract:

   In situ Operations, Administration, and Maintenance (IOAM) is used
   for recording and collecting operational and telemetry information.
   Specifically, passport-based IOAM allows telemetry data generated by
   each node along the path to be pushed into data packets when they
   traverse the network, while postcard-based IOAM allows IOAM data
   generated by each node to be directly exported without being pushed
   into in-flight data packets.  This document extends IOAM Direct
   Export (DEX) Option-Type to integrate the Alternate-Marking Method
   into IOAM.


Any comments and questions are welcomed.


Best and Regards,
Xiaoming He
China telecom