[core] CRI Extension for multiple schemes

Jim Schaad <ietf@augustcellars.com> Sat, 13 June 2020 17:22 UTC

Return-Path: <ietf@augustcellars.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 42EF33A0A35 for <core@ietfa.amsl.com>; Sat, 13 Jun 2020 10:22:11 -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 QKhjafHzUwCE for <core@ietfa.amsl.com>; Sat, 13 Jun 2020 10:22:09 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EFD73A0A2C for <core@ietf.org>; Sat, 13 Jun 2020 10:22:09 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 13 Jun 2020 10:22:02 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: core@ietf.org
Date: Sat, 13 Jun 2020 10:21:59 -0700
Message-ID: <002f01d641a7$26c44870$744cd950$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdZBoorzzH3ZFQl9QdWRMWbdLYcGCw==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-TrFW7NkLQrb2ptX9E03r_DjMj4>
Subject: [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: Sat, 13 Jun 2020 17:22:11 -0000

I had a strange idea which both violates the entire concept of what CRI was
designed to do, but has the potential to solve some problems that have been
pushed onto the back burner.  

Given that we have broken down a URI into an array of items, and there has
been some desire to allow for some type of multiple schemes to be specified
for a URI, what happens if we put an array of schemes into a CRI.  This
would allow for something like the following:

[ ["coap", "coap+tls"], "example.com", ".well-known", "core"]

While one could additionally allow for an array of host/port information I
think that this would be a step to far.  One would need to "resolve" the
array of schemes down to a single item before it could be used as if it were
a URI but the ability to carry this information might be something very
useful.

Jim