IETF Logo Mail Archive

Re: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Fri, 29 September 2023 09:27 UTC

Return-Path: <giuseppe.fioccola@huawei.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 DDB90C17EB7D for <ippm@ietfa.amsl.com>; Fri, 29 Sep 2023 02:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 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, 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 1cJ08RNkYPjD for <ippm@ietfa.amsl.com>; Fri, 29 Sep 2023 02:27:25 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3295FC17EB7A for <ippm@ietf.org>; Fri, 29 Sep 2023 02:27:25 -0700 (PDT)
Received: from frapeml100006.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RxlP31l9Sz6D92b; Fri, 29 Sep 2023 17:27:19 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml100006.china.huawei.com (7.182.85.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 29 Sep 2023 11:27:22 +0200
Received: from frapeml500006.china.huawei.com ([7.182.85.219]) by frapeml500006.china.huawei.com ([7.182.85.219]) with mapi id 15.01.2507.031; Fri, 29 Sep 2023 11:27:22 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step
Thread-Index: AQHZ5l6mdZot2OQkNUCYdyQ78RslIbAv/hIw
Date: Fri, 29 Sep 2023 09:27:22 +0000
Message-ID: <1f77c5d2a0014c1a97d66c4631f6b187@huawei.com>
References: <148C83FD-7102-405E-85AF-C29D0A265EB2@apple.com>
In-Reply-To: <148C83FD-7102-405E-85AF-C29D0A265EB2@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.150.123]
Content-Type: multipart/alternative; boundary="_000_1f77c5d2a0014c1a97d66c4631f6b187huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/wTu8tI0MVrYKohVSgrcxIP0aKaI>
Subject: Re: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step
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, 29 Sep 2023 09:27:29 -0000

Hi All,
I have read the document and I support its adoption.
Some comments:

  *   I think it would be useful to highlight better in the Introduction the motivations for this new mechanism.
  *   In the draft it is mentioned that in some cases a follow-up packet can be originated without using the trigger. I think it can be good to list all the potential cases.
  *   I would also suggest to make some examples of application (maybe in a new section) in order to show the reader some possible scenarios after describing the theory of operation.
  *   Usage examples can also be useful to make clear the mechanism of the trigger and follow-up packets with the related timers.

Regards,

Giuseppe


From: ippm <ippm-bounces@ietf.org> On Behalf Of Tommy Pauly
Sent: Wednesday, September 13, 2023 6:22 PM
To: IETF IPPM WG <ippm@ietf.org>
Subject: [ippm] Call for adoption for draft-mirsky-ippm-hybrid-two-step

Hello IPPM,

This email starts a call for adoption for draft-mirsky-ippm-hybrid-two-step. This draft has been around for a while and discussed several times on list and in WG meetings.

https://datatracker.ietf.org/doc/draft-mirsky-ippm-hybrid-two-step/
https://www.ietf.org/archive/id/draft-mirsky-ippm-hybrid-two-step-15.html

Please review the document and email the list with your comments, and if you think IPPM should adopt this work.

This call for adoption will last three weeks and end on October 4th.

Best,
Tommy

v2.23.0 | Report a Bug | By Email