Re: [ippm] Adoption call for Explicit Flow Measurements Techniques

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Thu, 14 October 2021 21:24 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 7564E3A0CA2 for <ippm@ietfa.amsl.com>; Thu, 14 Oct 2021 14:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.797
X-Spam-Level:
X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRyeq7Wjtopf for <ippm@ietfa.amsl.com>; Thu, 14 Oct 2021 14:24:07 -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 22B733A0D7B for <ippm@ietf.org>; Thu, 14 Oct 2021 14:24:07 -0700 (PDT)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HVj4f39VYz67NYL; Fri, 15 Oct 2021 05:21:06 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 14 Oct 2021 23:24:02 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2308.008; Thu, 14 Oct 2021 23:24:02 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Haoyu Song <haoyu.song@futurewei.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Thread-Topic: [ippm] Adoption call for Explicit Flow Measurements Techniques
Thread-Index: AQHXvF2JxQbTKMWCnUCA/EeIh/2STqvSns+AgABfn4A=
Date: Thu, 14 Oct 2021 21:24:02 +0000
Message-ID: <607b55b18a9f4c129691b24dd7aa67ec@huawei.com>
References: <A318EC97-859A-4723-9211-03B1CBF74374@apple.com> <BY3PR13MB47877DB1B8A17B6FA8A240019AB89@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB47877DB1B8A17B6FA8A240019AB89@BY3PR13MB4787.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.217.53]
Content-Type: multipart/alternative; boundary="_000_607b55b18a9f4c129691b24dd7aa67echuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/BpvcIiHtACu9U-pXA5zUWnEGWGU>
Subject: Re: [ippm] Adoption call for Explicit Flow Measurements Techniques
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Oct 2021 21:24:12 -0000

Hi Haoyu,
The methods described in this document, if applied to encrypted protocols, need to use unencrypted header fields in order to enable the on-path measurements. That is the case of the examples for QUIC and TCP. In this regard, note that the spin bit has already been defined in the QUIC short packet header (RFC9000).

We can further clarify this point in the next version.

Regards,

Giuseppe


From: ippm <ippm-bounces@ietf.org> On Behalf Of Haoyu Song
Sent: Thursday, October 14, 2021 6:57 PM
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>
Subject: Re: [ippm] Adoption call for Explicit Flow Measurements Techniques

IPPM WG and chairs,

The proposed method is interesting and useful. I support the WG adoption.
I have a question to the authors. The draft says that the method is valuable for encrypted transport headers but later it suggested to encapsulate the bits in QUIC and TCP header. How does that work if the transport header is encrypted?

Best regards,
Haoyu
From: ippm <ippm-bounces@ietf.org<mailto:ippm-bounces@ietf.org>> On Behalf Of Tommy Pauly
Sent: Friday, October 8, 2021 8:59 AM
To: IETF IPPM WG (ippm@ietf.org<mailto:ippm@ietf.org>) <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: [ippm] Adoption call for Explicit Flow Measurements Techniques

Hello IPPM,

This email starts an adoption call for draft-mdt-ippm-explicit-flow-measurements, "Explicit Flow Measurements Techniques". This document is proposed as an Informational document that describes techniques that go beyond single bit markings like the QUIC spin bit.

https://datatracker.ietf.org/doc/draft-mdt-ippm-explicit-flow-measurements/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-mdt-ippm-explicit-flow-measurements%2F&data=04%7C01%7Chaoyu.song%40futurewei.com%7C0bb1ccaae82a449e5c8308d98a749f47%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637693055772340329%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=o%2FcX355kvvyuGlhYGsYrsEPfQimXoPMFoxYFptqmxsE%3D&reserved=0>
https://datatracker.ietf.org/doc/html/draft-mdt-ippm-explicit-flow-measurements-02<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-mdt-ippm-explicit-flow-measurements-02&data=04%7C01%7Chaoyu.song%40futurewei.com%7C0bb1ccaae82a449e5c8308d98a749f47%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637693055772350280%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RcUvJsuRDvZ38Ec1Ss2X10CzTDHX5rCC748iZmcLJyU%3D&reserved=0>

This adoption call will last until Friday, October 22. Please review the document, and reply to this email thread to indicate if you think IPPM should adopt this document.

Best,
Tommy