W3C home > Mailing lists > Public > uri@w3.org > August 2013

Re: Standardizing on IDNA 2003 in the URL Standard

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 22 Aug 2013 13:36:56 +0100
Message-ID: <CADnb78hTR_t7VCpurLdUfvn4_iSa-1Sp6-ShsWQnYqPpZuR=aA@mail.gmail.com>
To: Gervase Markham <gerv@mozilla.org>
Cc: Mark Davis ☕ <mark@macchiato.com>, Shawn Steele <Shawn.Steele@microsoft.com>, IDNA update work <idna-update@alvestrand.no>, "PUBLIC-IRI@W3.ORG" <public-iri@w3.org>, "uri@w3.org" <uri@w3.org>, John C Klensin <klensin@jck.com>, Peter Saint-Andre <stpeter@stpeter.im>, Marcos Sanz <sanz@denic.de>, Vint Cerf <vint@google.com>, "www-tag.w3.org" <www-tag@w3.org>
On Thu, Aug 22, 2013 at 1:28 PM, Gervase Markham <gerv@mozilla.org> wrote:
> You mean with regard to UseSTD3ASCIIRules? Happy to change my proposal
> in that regard. See the bug.

With regards to all the things that would be different, including
treatment of e.g. ß. We should provide a consistent platform to the
world, not one that keeps changing under your feet. And the
compatibility that is important here is not compatibility with
IDNA2003 per se, but with DNS as deployed and support for it in

As far as UseSTD3ASCIIRules is concerned, I haven't checked if TR46 is
safe when it comes to
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23009 if you turn that
flag off. We want "_" in the output, but never "/" (should just fail).
(Currently we have "/" in the output, but that causes downstream
security bugs due to parsing the serialization yielding different

Received on Thursday, 22 August 2013 12:37:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:16 UTC