Re: [apps-discuss] presumption that RFC3986 is correct

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 03 January 2015 18:56 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFEEF1A00F5 for <apps-discuss@ietfa.amsl.com>; Sat, 3 Jan 2015 10:56:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vzwECofDr7_Z for <apps-discuss@ietfa.amsl.com>; Sat, 3 Jan 2015 10:56:54 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8C11A007B for <apps-discuss@ietf.org>; Sat, 3 Jan 2015 10:56:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 85746BF02; Sat, 3 Jan 2015 18:56:52 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id moLm5IWfjF59; Sat, 3 Jan 2015 18:56:51 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.46.26.8]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 09463BEF4; Sat, 3 Jan 2015 18:56:51 +0000 (GMT)
Message-ID: <54A83B72.4010106@cs.tcd.ie>
Date: Sat, 03 Jan 2015 18:56:50 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Sam Ruby <rubys@intertwingly.net>, Graham Klyne <gk@ninebynine.org>
References: <20140926010029.26660.82167.idtracker@ietfa.amsl.com> <EAACE200D9B0224D94BF52CF2DD166A425A68A90@ex10mb6.qut.edu.au> <CACweHNBEYRFAuw9-vfeyd_wf703cvM3ykZoRMqAokRFYG_O7hQ@mail.gmail.com> <DM2PR0201MB09602B351692D424A49C6B0DC3650@DM2PR0201MB0960.namprd02.prod.outlook.com> <CACweHNBN_Bv=jeXQ_VwXi2HzHKNEwZJ1NiF-BJJo_9-mhO60gQ@mail.gmail.com> <54A5730C.8040501@ninebynine.org> <54A583DD.9010602@intertwingly.net> <54A59651.4060306@ninebynine.org> <54A59B26.5000408@intertwingly.net> <54A6AABF.4060406@ninebynine.org> <54A6B6DF.1010206@intertwingly.net> <54A7DC46.2020708@ninebynine.org> <54A7E9F4.80406@intertwingly.net> <54A820EA.20200@ninebynine.org> <54A82CC4.9080606@intertwingly.net>
In-Reply-To: <54A82CC4.9080606@intertwingly.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/Pzatcrf6ydVR6KYmHtJJ9DcQPAc
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] presumption that RFC3986 is correct
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jan 2015 18:56:57 -0000

Hi Sam,

On 03/01/15 17:54, Sam Ruby wrote:
> 
> I intend to work with implementors, providing patches and/or new
> implementations along the way.  And I'll continue to document and
> publish findings.  One such place I have published such work is at the 
> W3C:
> 
>   http://www.w3.org/TR/url/

I have at least one question about how you (or W3C, or any of us)
plan to head towards some reasonable level of completeness with
that work. (This may be a bit of an aside in the current discussion,
or maybe not, I'm not sure.)

The draft at the URL above includes [1], which is a risibly small
and fixed (?) subset of an IANA registry. [2] What's the plan for
making that sensible? I would assume pointing at the IANA registry
is the simple and obvious fix there, but am puzzled as to why that
hasn't been done in the few years this text has been around.

Is that just an oversight? Or is your work really only covering
exactly that particular subset of schemes? Or something else?

Thanks,
S.

[1] http://www.w3.org/TR/url/#relative-scheme
[2] https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml