Re: [Uri-review] Internet-Draft: Using URIs With Multiple Transport Stacks

Graham Klyne <GK-lists@ninebynine.org> Sun, 09 July 2017 07:09 UTC

Return-Path: <GK-lists@ninebynine.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE8B129AC6; Sun, 9 Jul 2017 00:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 f_rQ1_mAr_A9; Sun, 9 Jul 2017 00:09:18 -0700 (PDT)
Received: from relay16.mail.ox.ac.uk (relay16.mail.ox.ac.uk [163.1.2.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA5E3129AC1; Sun, 9 Jul 2017 00:09:17 -0700 (PDT)
Received: from smtp6.mail.ox.ac.uk ([163.1.2.206]) by relay16.mail.ox.ac.uk with esmtp (Exim 4.89) (envelope-from <GK-lists@ninebynine.org>) id 1dU6LE-0001Ai-pd; Sun, 09 Jul 2017 08:09:16 +0100
Received: from gklyne38.plus.com ([81.174.129.24] helo=sasharissa.local) by smtp6.mail.ox.ac.uk with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <GK-lists@ninebynine.org>) id 1dU6LD-0008t3-LJ; Sun, 09 Jul 2017 08:09:15 +0100
Message-ID: <5961D699.50909@ninebynine.org>
Date: Sun, 09 Jul 2017 08:09:13 +0100
From: Graham Klyne <GK-lists@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>, Dave Thaler <dthaler@microsoft.com>
CC: "art@ietf.org" <art@ietf.org>, "uri-review@ietf.org" <uri-review@ietf.org>, "dispatch@ietf.org" <dispatch@ietf.org>
References: <MWHPR21MB0125E2464E9B3A25E0FB8967A3D50@MWHPR21MB0125.namprd21.prod.outlook.com> <f5b1spsl1mr.fsf@troutbeck.inf.ed.ac.uk>
In-Reply-To: <f5b1spsl1mr.fsf@troutbeck.inf.ed.ac.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Oxmail-Spam-Status: score=0.0 tests=none
X-Oxmail-Spam-Level: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/oVN6vmHWo_DQVoyaCizAd0o_HbY>
Subject: Re: [Uri-review] Internet-Draft: Using URIs With Multiple Transport Stacks
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2017 07:09:19 -0000

Henry, thanks for this reminder.

FWIW, looking at section 4 
(http://www.w3.org/2001/tag/doc/SchemeProtocols.html#findings), I think R1, R3, 
G5, G6, R7, G8, G9 (i.e., most of the findings!) all have some bearing on the 
issues being discussed, insofar as they affect the World Wide Web.  On a brief 
scan, I think the discussion here is as relevant today as it was in 2005 - some 
maybe more so with the move to HTTPS-everywhere.

#g
--


On 07/07/2017 16:15, Henry S. Thompson wrote:
> Dave Thaler writes:
>
>> Recently we've seen multiple requests (including from three different
>> SDOs) and discussions on different lists regarding using URI schemes
>> for application-layer protocols that can operate over multiple
>> transport stacks (e.g., UDP, TCP, websockets, HTTP, etc.). This draft
>> summarizes the various technical discussions and issues raised.
>>
>> Not sure if there is any regular meeting time available at IETF, but I
>> at least wanted to share this more broadly for visibility, and to
>> solicit additional feedback.
>
> The W3C TAG devoted a fair amount of effort to this issue about 12 years
> ago, and our thinking at the time (2005) is recorded here:
>
>    https://www.w3.org/2001/tag/doc/SchemeProtocols.html
>
> which may provide a useful independent perspective, albeit somewhat
> dated in some respects.
>
> ht
>