Re: [apps-discuss] Potential issues in RFC 3986

Sam Ruby <rubys@intertwingly.net> Fri, 02 January 2015 18:39 UTC

Return-Path: <rubys@intertwingly.net>
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 068D51A01A5 for <apps-discuss@ietfa.amsl.com>; Fri, 2 Jan 2015 10:39:48 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 HjK495echPxQ for <apps-discuss@ietfa.amsl.com>; Fri, 2 Jan 2015 10:39:46 -0800 (PST)
Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) by ietfa.amsl.com (Postfix) with ESMTP id 77B261A007F for <apps-discuss@ietf.org>; Fri, 2 Jan 2015 10:39:46 -0800 (PST)
Received: from [98.27.51.253] ([98.27.51.253:45694] helo=rubix) by cdptpa-oedge03 (envelope-from <rubys@intertwingly.net>) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 02/94-20729-1F5E6A45; Fri, 02 Jan 2015 18:39:45 +0000
Received: from [192.168.1.115] (unknown [192.168.1.115]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: rubys) by rubix (Postfix) with ESMTPSA id 652BA140C4E; Fri, 2 Jan 2015 13:39:45 -0500 (EST)
Message-ID: <54A6E5F1.3070006@intertwingly.net>
Date: Fri, 02 Jan 2015 13:39:45 -0500
From: Sam Ruby <rubys@intertwingly.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
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> <54A6BB22.2060203@gmx.de> <54A6C01A.6020000@intertwingly.net> <54A6CD33.3080101@gmx.de>
In-Reply-To: <54A6CD33.3080101@gmx.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RR-Connecting-IP: 107.14.168.142:25
X-Cloudmark-Score: 0
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/P3PpwmirNTGdho9SDtx93BZVi7A
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Potential issues in RFC 3986
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: Fri, 02 Jan 2015 18:39:48 -0000

On 01/02/2015 11:54 AM, Julian Reschke wrote:
> On 2015-01-02 16:58, Sam Ruby wrote:
>> ...
>>>> ...
>>>>> In a brief sampling, I couldn't see any divergence which is likely
>>>>> to be
>>>>> resolvable by changing the URI spec.
>>>>
>>>> I encourage you to spend more time with that data.  An example of a
>>>> concrete problem is handing of hosts in a UTS-46 compliant manner.
>>>> ...
>>>
>>> Which test, specifically?
>>
>> Most of the tests in the range of 242..263 deal with IDNA issues in some
>> manner or another.  A particularly fun one is test 261:
>>
>> https://url.spec.whatwg.org/interop/test-results/e99bce2c50
>>
>> <aside>ordinal test numbers may change over time.  The hash, however,
>> will not</aside>.
>>
>> I encourage you to scan the text of RFC 3986 for the term "IDNA".  In
>> the decade between when RFC 3986 was published and today, things have
>> progressed a bit here.
>> ...
>
> I'm fully aware that RFC 3986 is likely incorrect wrt IDNA advice.
>
> However, the test that you cite does not use a valid URI, so I don't
> think it can be used as example that something in RFC 3986 is incorrect.

Since you agree that RFC 3986 is likely incorrect wrt IDNA advice, can I 
get you to suggest a test case that demonstrates this?

The master source for these tests is here:

https://github.com/w3c/web-platform-tests/blob/master/url/urltestdata.txt

A pull request would be appreciated.  A detailed suggestion with the 
same information (a source string, a base URI, and what the expected 
values for each of the components) also works.

  - - -

Railing this up a level, Roy Fielding believes that a WG would need to 
be chartered in order to update RFC 3986.  See the bottom of the 
following email:

http://lists.w3.org/Archives/Public/public-ietf-w3c/2014Dec/0088.html

Per that email, I tend to agree.

On any specific issue, I don't know what the outcome should be -- 
whether RFC 3986 should be updated, or whether implementations should 
change.  What I am looking for is to get together the set of people who 
are interested in that discussion and for us to come to a consensus 
together.

I'm willing to do the leg-work, whether that be running tests or 
updating specs, or filing bugs against implementations.

> Best regards, Julian

- Sam Ruby