Re: [core] Using SVCB with OSCORE/EDHOC
chrysn <chrysn@fsfe.org> Mon, 27 March 2023 03:00 UTC
Return-Path: <chrysn@fsfe.org>
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 92ED0C151B13 for <core@ietfa.amsl.com>; Sun, 26 Mar 2023 20:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level:
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 CF3ZFaomKjaB for <core@ietfa.amsl.com>; Sun, 26 Mar 2023 20:00:58 -0700 (PDT)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 510AFC151B18 for <core@ietf.org>; Sun, 26 Mar 2023 20:00:57 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by smtp.akis.at (8.17.1/8.17.1) with ESMTPS id 32R30tmn090120 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 27 Mar 2023 05:00:55 +0200 (CEST) (envelope-from chrysn@fsfe.org)
X-Authentication-Warning: smtp.akis.at: Host 095129206250.cust.akis.net [95.129.206.250] claimed to be poseidon-mailhub.amsuess.com
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 823D11DA04; Mon, 27 Mar 2023 05:00:55 +0200 (CEST)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::aa6]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 5456A200C9; Mon, 27 Mar 2023 05:00:55 +0200 (CEST)
Received: (nullmailer pid 25703 invoked by uid 1000); Mon, 27 Mar 2023 03:00:54 -0000
Date: Mon, 27 Mar 2023 05:00:54 +0200
From: chrysn <chrysn@fsfe.org>
To: Carsten Bormann <cabo@tzi.org>
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Message-ID: <ZCEG5hGanlF58G2w@hephaistos.amsuess.com>
References: <ZCAywSGXT9Yv16ZC@hephaistos.amsuess.com> <CA78D163-0DEE-4771-8367-A38F3CE5E7FD@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="wtj3ivNyd/J3AvLv"
Content-Disposition: inline
In-Reply-To: <CA78D163-0DEE-4771-8367-A38F3CE5E7FD@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/QnZdheePgNi3HspxDpmreu3pbxU>
Subject: Re: [core] Using SVCB with OSCORE/EDHOC
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, 27 Mar 2023 03:00:59 -0000
On Mon, Mar 27, 2023 at 12:41:12AM +0900, Carsten Bormann wrote: > I wonder if we can defuse the complexity of this by defining the actual data model. Well, currently we have ongoing work describing EDHOC availability though link-format ... which is not a great data model on its own. It also doesn't tackle matters of identity yet, but I think it could (and that might be a good hint for me to revive rdlink[2]). The metadata could then also contain information about how to verify the peer (eg. by giving its CCS or an id / id_cred pair contianing a CCS), which would allow links to be securely followable without prior relation to the RS ... leading us once more to unanswered questions about our web security model. BR c [1]: https://www.ietf.org/archive/id/draft-ietf-core-oscore-edhoc-07.html#name-web-linking [2]: https://datatracker.ietf.org/doc/draft-amsuess-t2trg-rdlink/
- [core] Using SVCB with OSCORE/EDHOC Christian Amsüss
- Re: [core] Using SVCB with OSCORE/EDHOC Carsten Bormann
- Re: [core] Using SVCB with OSCORE/EDHOC chrysn