Re: [core] CRI Extension for multiple schemes

Christian Amsüss <christian@amsuess.com> Wed, 17 June 2020 20:38 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 482EB3A0AE7 for <core@ietfa.amsl.com>; Wed, 17 Jun 2020 13:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 R9efSPYYYTt0 for <core@ietfa.amsl.com>; Wed, 17 Jun 2020 13:38:21 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16EF93A0ACB for <core@ietf.org>; Wed, 17 Jun 2020 13:38:20 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 1EA0740674; Wed, 17 Jun 2020 22:38:18 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 3AF7AD3; Wed, 17 Jun 2020 22:38:17 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a581:7ff4:c0a6:4df9]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id E96371A0; Wed, 17 Jun 2020 22:38:16 +0200 (CEST)
Received: (nullmailer pid 2644251 invoked by uid 1000); Wed, 17 Jun 2020 20:38:16 -0000
Date: Wed, 17 Jun 2020 22:38:16 +0200
From: Christian Amsüss <christian@amsuess.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: core@ietf.org
Message-ID: <20200617203816.GA2643779@hephaistos.amsuess.com>
References: <002f01d641a7$26c44870$744cd950$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q"
Content-Disposition: inline
In-Reply-To: <002f01d641a7$26c44870$744cd950$@augustcellars.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/0WxvQSvBXcEw7NfsN5RCGJC7fVw>
Subject: Re: [core] CRI Extension for multiple schemes
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: Wed, 17 Jun 2020 20:38:23 -0000

Hi Jim,

On Sat, Jun 13, 2020 at 10:21:59AM -0700, Jim Schaad wrote:
> [ ["coap", "coap+tls"], "example.com", ".well-known", "core"]

The protocol negotiation work has seen less activity than I'd like to
have put into it, but the latest proposals go in the direction of
avoiding URI aliasing altogether:

Even though a TLS transport is offered, the server would be addressed as
'coap://server/path' by virtue of an (explicit or, later, implied /
compressed) Proxy-Scheme option; links there would use the canonical
form and may contain hints in attributes expressing that "the target's
server is also accepting connections using this or that protocol".

Having a shortcut in CRIs sounds tempting, but I dread the
translatability to the rest of the web ecosystem where those are
unavailable, and the need to deal with aliased URIs in general.

KR
c

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