Re: [ippm] IPPM adoption call for draft-mirsky-ippm-asymmetrical-pkts

xiao.min2@zte.com.cn Fri, 12 April 2024 03:45 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 23398C14F618 for <ippm@ietfa.amsl.com>; Thu, 11 Apr 2024 20:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.192
X-Spam-Level:
X-Spam-Status: No, score=-4.192 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 l4oDCPJzInrd for <ippm@ietfa.amsl.com>; Thu, 11 Apr 2024 20:45:52 -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 F30E9C14F600 for <ippm@ietf.org>; Thu, 11 Apr 2024 20:45:50 -0700 (PDT)
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 4VG2XX5wS2z8XrRF for <ippm@ietf.org>; Fri, 12 Apr 2024 11:45:48 +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 4VG2Ww4Kn4z50FXX; Fri, 12 Apr 2024 11:45:16 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl1.zte.com.cn with SMTP id 43C3jBFV098375; Fri, 12 Apr 2024 11:45:12 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid201; Fri, 12 Apr 2024 11:45:13 +0800 (CST)
Date: Fri, 12 Apr 2024 11:45:13 +0800
X-Zmail-TransId: 2aff6618ae49108-8f2ef
X-Mailer: Zmail v1.0
Message-ID: <20240412114513590Axr46uLydmHPd9DC-Nikq@zte.com.cn>
In-Reply-To: <EB9C8A72-2118-4D5F-8A49-BB6CC327297F@apple.com>
References: EB9C8A72-2118-4D5F-8A49-BB6CC327297F@apple.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: tpauly=40apple.com@dmarc.ietf.org
Cc: ippm@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 43C3jBFV098375
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6618AE6C.000/4VG2XX5wS2z8XrRF
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/JTVoDZdpfrB9KOYcyksGtiYIlLg>
Subject: Re: [ippm] IPPM adoption call for draft-mirsky-ippm-asymmetrical-pkts
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, 12 Apr 2024 03:45:56 -0000

I support wg adoption of this draft. I think it's a useful extension to STAMP.

Best Regards,
Xiao Min

Original


From: TommyPauly <tpauly=40apple.com@dmarc.ietf.org>
To: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>;
Date: 2024年04月10日 00:37
Subject: [ippm] IPPM adoption call for draft-mirsky-ippm-asymmetrical-pkts

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

Hello IPPM,
This email starts an adoption call for draft-mirsky-ippm-asymmetrical-pkts. This is a document we’ve discussed several times, and is a normative dependency for another document we discussed adopting at IETF 119, draft-gandhi-ippm-stamp-ext-hdr.

You can find the draft here:
https://datatracker.ietf.org/doc/draft-mirsky-ippm-asymmetrical-pkts/
https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-04.html#name-reflected-test-packet-control

Please review the draft and respond to this email to indicate if you think IPPM should adopt this document as a working group item.

This call will last for 3 weeks. Please reply by Tuesday, April 30.

Best,
Tommy & Marcus