Parsing the issues and finding a middle ground -- another attempt

Erik van der Poel erikv at
Wed Mar 4 16:20:28 CET 2009

My point of view is a little different.

One of the most important contexts for URLs/URIs/IRIs is HTML. In that
context, I'd prefer to do no mapping, or, if really necessary, only
/global/ mapping. We'd have interoperability problems if browsers
started performing language-specific (local) mappings to domain names
in URLs in HTML.

Local mapping might be useful in the URL bar, where browsers accept
bare host names (without the leading "http://").

Maybe this discussion is due to global vs local terminological confusion.


On Wed, Mar 4, 2009 at 7:12 AM, Andrew Sullivan <ajs at> wrote:
> On Tue, Mar 03, 2009 at 06:54:09PM -0500, John C Klensin wrote:
>> way through all of the cases and issues.  Just to mention
>> another alternative before we go down too far down one path or
>> the other...
> [&c.]
> I think this idea is promising, because if I understand it correctly
> it sounds like it permits isolating whatever problems local mappings
> are going to cause to the particular situations for which those local
> mappings are supposed to be helpful.  I'm still somewhat sceptical,
> but this sounds like the best suggestion for a way forward so far, so
> I'd like to understand it better.
> A
> --
> Andrew Sullivan
> ajs at
> Shinkuro, Inc.
> _______________________________________________
> Idna-update mailing list
> Idna-update at

More information about the Idna-update mailing list