Re: [core] Review of draft-fz-core-coap-pm-03

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 13 March 2023 18:15 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501D8C15256E for <core@ietfa.amsl.com>; Mon, 13 Mar 2023 11:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 8L9AjFhWx5kE for <core@ietfa.amsl.com>; Mon, 13 Mar 2023 11:15:35 -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 0F71DC1522AD for <core@ietf.org>; Mon, 13 Mar 2023 11:15:35 -0700 (PDT)
Received: from frapeml500005.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Pb4ZZ5ttNz6J68l; Tue, 14 Mar 2023 02:15:18 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml500005.china.huawei.com (7.182.85.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Mon, 13 Mar 2023 19:15:33 +0100
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.021; Mon, 13 Mar 2023 19:15:33 +0100
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org>, Christian Amsüss <christian@amsuess.com>, Marco Tiloca <marco.tiloca=40ri.se@dmarc.ietf.org>
CC: "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Review of draft-fz-core-coap-pm-03
Thread-Index: AQHZShjihhHGiO56RUOpRMd7g0VBf670IksAgAATWqCABOUZ8A==
Date: Mon, 13 Mar 2023 18:15:33 +0000
Message-ID: <0df95873ddc34ed89ab0c5cc0acb4283@huawei.com>
References: <80824788-14ed-2947-824f-f96acd6307b5@ri.se> <ZAtKXsMuVAKlvr3m@hephaistos.amsuess.com> <2cab5d3cb2b541b48b4b3893e1ffa1e2@huawei.com>
In-Reply-To: <2cab5d3cb2b541b48b4b3893e1ffa1e2@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.157.165]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hnDuYMZt4zc3E3nxqaqnVy4BTmw>
Subject: Re: [core] Review of draft-fz-core-coap-pm-03
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2023 18:15:36 -0000

Dear All,
Please note that we just submitted the new version of draft-fz-core-coap-pm in order to address the comments received during the interim meeting and on the mailing list.

Feedback and suggestions are always welcome.

Regards,

Giuseppe
(on behalf of the coauthors)


-----Original Message-----
From: core <core-bounces@ietf.org> On Behalf Of Giuseppe Fioccola
Sent: Friday, March 10, 2023 4:34 PM
To: Christian Amsüss <christian@amsuess.com>; Marco Tiloca <marco.tiloca=40ri.se@dmarc.ietf.org>
Cc: core@ietf.org
Subject: Re: [core] Review of draft-fz-core-coap-pm-03

Hi Christian,
Please see inline [GF]

Regards,

Giuseppe

-----Original Message-----
From: core <core-bounces@ietf.org> On Behalf Of Christian Amsüss
Sent: Friday, March 10, 2023 4:19 PM
To: Marco Tiloca <marco.tiloca=40ri.se@dmarc.ietf.org>
Cc: core@ietf.org
Subject: Re: [core] Review of draft-fz-core-coap-pm-03

Hi,

just one remark on what I noticed skimming:

On Sun, Feb 26, 2023 at 08:30:11PM +0100, Marco Tiloca wrote:
> * When using OSCORE, having the PM option as inner or outer does not 
> have to be mutually exclusive. That is, measurements can be performed 
> both at the ends, and in the individual hops, by having the option both outer and inner.
> 
>    However, if the PM option is used (also) as an outer option, 
> shouldn't the outer option also be (at least) integrity-protected, to 
> be reliably processed by the intended consumer? This would require 
> using also DTLS hop-by-hop, or an (additional) OSCORE association with 
> an intermediary (see draft-tiloca-core-oscore-capable-proxies).

I don't think that option should be Class-I. The option is hop-by-hop now, and may be legitimately terminated at proxies. If it were Class-I, a proxy's operation would make the requests fail.

[GF]: Yes, in case of collaborating proxies, the option is terminated at proxies and Class E is ok. But, in case of non-collaborating and non-caching proxies an implementation may consider the option as Safe-to-Forward in order to implement measurements. In this corner case, Class-I can be considered to enable hop-by-hop.

If an OSCORE endpoint sends both outer and inner, the inner is for measuring the connection to the E2E peer, and the outer is for measuring the connection to next hop proxy.

[GF]: Yes

BR
c

--
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

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