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

Sean Leonard <dev+ietf@seantek.com> Sat, 03 January 2015 19:36 UTC

Return-Path: <dev+ietf@seantek.com>
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 458CB1A0055 for <apps-discuss@ietfa.amsl.com>; Sat, 3 Jan 2015 11:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 3ms088jPyrxa for <apps-discuss@ietfa.amsl.com>; Sat, 3 Jan 2015 11:36:13 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A73421A0058 for <apps-discuss@ietf.org>; Sat, 3 Jan 2015 11:36:13 -0800 (PST)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 942FD22E261 for <apps-discuss@ietf.org>; Sat, 3 Jan 2015 14:36:12 -0500 (EST)
Message-ID: <54A84470.1000909@seantek.com>
Date: Sat, 03 Jan 2015 11:35:12 -0800
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: apps-discuss@ietf.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> <54A83B72.4010106@cs.tcd.ie>
In-Reply-To: <54A83B72.4010106@cs.tcd.ie>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/AkHbg2ehQZjQNOeFXn1Im1ue1EI
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 19:36:15 -0000

On 1/3/2015 10:56 AM, Stephen Farrell wrote:
> 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.

+1
Yeah man, just use the IANA registry...

Sean