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

Julian Reschke <julian.reschke@gmx.de> Fri, 02 January 2015 16:54 UTC

Return-Path: <julian.reschke@gmx.de>
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 32A811A1B87 for <apps-discuss@ietfa.amsl.com>; Fri, 2 Jan 2015 08:54:33 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 kisTdSdRa6fh for <apps-discuss@ietfa.amsl.com>; Fri, 2 Jan 2015 08:54:31 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 499691A1B80 for <apps-discuss@ietf.org>; Fri, 2 Jan 2015 08:54:31 -0800 (PST)
Received: from [192.168.1.194] ([217.91.35.233]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LqiJO-1XbccL0Yni-00eOPa; Fri, 02 Jan 2015 17:54:19 +0100
Message-ID: <54A6CD33.3080101@gmx.de>
Date: Fri, 02 Jan 2015 17:54:11 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; 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> <54A6BB22.2060203@gmx.de> <54A6C01A.6020000@intertwingly.net>
In-Reply-To: <54A6C01A.6020000@intertwingly.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:9xKHGqqqCx44N4vTVkxmjcpsjLe7TmFza4vAE3O9TZf6O6ynXJw h9zc7WDWlVouy21R9GK2h0dQfWWl+XCCQzjMYb04h4l4lPn7b1Sr2iRpzu827GfnoyhE02j ZEl2aQSvLB6gKj5m12/p6b7QBlNtX5QvebbxHwreFSOVPp5KWH62stcNybgFT7rAor6xOpQ YTqk9jRQr2YqHB1Jys1xg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/nT6dRTJSqUHo9UjF9R6CCxGHGT0
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 16:54:33 -0000

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.

Best regards, Julian