To:
Andrew Sullivan <andrew@ca.afilias.info>, ietf-provreg@cafax.se
From:
Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date:
Tue, 10 Apr 2007 10:49:28 +0200
Content-Disposition:
inline
In-Reply-To:
<20070409130632.GD12177@afilias.info>
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.5.13 (2006-08-11)
Subject:
[ietf-provreg] Re: EPP Extensions for IDN
On Mon, Apr 09, 2007 at 09:06:32AM -0400, Andrew Sullivan <andrew@ca.afilias.info> wrote a message of 62 lines which said: > > IDN deals with scripts, not with languages. > > My reading of the RFCs is that IDNA specifically deals with neither. > It rather deals with Unicode code points, You're right. > I can imagine that "??thenstravel" (in case that doesn't come > through, that's "[GREEK SMALL LETTER ALPHA]thens") could be a cool > name for a travel agency, for instance. So, which script is > "??thenstravel.example" in? Right and another example (may be more realistic) is company names in Russia where high-tech organisations sometimes have a name where a Latin-script acronym ("xml" for instance) is mixed with a Cyrillic-script name. > So at the very least, any extension is going to need support for > both "languages" and "scripts". May be using RFC 4646 for the tag would be the easier way to support both?