Re: [core] Tossing around URIs to use outside an application

Christian Amsüss <christian@amsuess.com> Tue, 18 May 2021 10:17 UTC

Return-Path: <christian@amsuess.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 225933A1528 for <core@ietfa.amsl.com>; Tue, 18 May 2021 03:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 8_fYZ2fQ1h14 for <core@ietfa.amsl.com>; Tue, 18 May 2021 03:17:38 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A6F3A1505 for <core@ietf.org>; Tue, 18 May 2021 03:17:37 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 888AC407F3; Tue, 18 May 2021 12:17:35 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id A515CD3; Tue, 18 May 2021 12:17:34 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a014:89c6:8ba:ba93]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 5A06810A; Tue, 18 May 2021 12:17:34 +0200 (CEST)
Received: (nullmailer pid 940151 invoked by uid 1000); Tue, 18 May 2021 10:17:33 -0000
Date: Tue, 18 May 2021 12:17:33 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Thomas Fossati <thomas.fossati@arm.com>, "core@ietf.org" <core@ietf.org>
Message-ID: <YKOUPd9DTCWv+nmQ@hephaistos.amsuess.com>
References: <YKJltpQ9l6k4tseH@hephaistos.amsuess.com> <FFC288E5-88B3-4AEE-A28E-BB6811EC678C@arm.com> <19288F96-6650-4D81-BBFF-19153DB5CE3A@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LnqUfaFcvBibUub/"
Content-Disposition: inline
In-Reply-To: <19288F96-6650-4D81-BBFF-19153DB5CE3A@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/R2B7yaRW3Lzg3K03yb_0NCoVnYk>
Subject: Re: [core] Tossing around URIs to use outside an application
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 May 2021 10:17:40 -0000

> … and we should define an information model for this so we aren’t
> stuck with DNS for providing that information.

Whatever comes out of the EDHOC discussion about transferring public
keys by value could also serve this purpose. In [82] and [88],
contenders for that seem to be stripped-down `COSE_Key`s, C509
"certificates" (AIU they're not necessarily certificates but can be RPKs
just as well) and CWTs.

This has some overlap with what can currently be expressed in DNS
(public-by-value would relate to SubjectPublicKeyInfo).

BR
c

[82]: https://github.com/lake-wg/edhoc/issues/82
[82]: https://github.com/lake-wg/edhoc/issues/88

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