Re: New Version Notification for draft-obispo-epp-idn-00.txt
Keith Gaughan <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Organization | Blacknight Internet Solutions |
| Message-ID | <[email protected]> |
On 22/12/11 16:41, Francisco Obispo wrote:
> On Dec 22, 2011, at 8:09 AM, Keith Gaughan wrote:
>
>> Essentially, what Patrik (and I) are asking is, if an IDN fits into a common
>> subset of the character tables of multiple languages, should it not be
>> possible to allow all those languages to be specified when registering the
>> IDN?
>
> Does it make a difference from the registration point of view?
Maybe not, but then why ask for the language at all? One could do what EURid
does and have a set of character tables per supported script (Latin, Greek and
Cyrillic), and so long as all the characters in an IDN are within the same
script, the registration is accepted.
It seems to me that given significant edge cases like the Danish/Norwegian
one I raised, if a language must be specified, one ought to be able to specify
multiple ones.
> The main purpose of this field, is so that the registry can apply a specific
> registration policy, in this case, the validation of unicode codepoints from
> a *published* language table towards the label (not a script).
Though more specifically, the point of even asking for the language in the
first place is to prevent homograph attacks. The use of languages rather than
scripts leads to slightly odd situations where a person wouldn't be able to
register a domain like æçöÿ.info (a silly example, I know, but valid), as
though there's no language that uses all those characters in their alphabet,
it's in no way a vector for homograph attacks.
> I guess we could make the extension flexible enough to allow for multiple
> "languages", but then make that an *optional* feature for the registry to
> allow it.
That I'll have to think about. I'm not sure it's exactly a massive
encumbrance upon an implementing registry to store all the associated
language codes, but then again, it may be acceptable for a registrar to
allow one and only one to be specified per IDN[1].
K.
[1] I raised the idea a while back about having a way for registries to
be able to publish their policies in a machine-readable form a while
back. This sort of thing would fit quite comfortably into it.
--
Keith Gaughan, Senior Developer
PGP/GPG key ID: 3E896381
Blacknight Internet Solutions Ltd. <http://blacknight.com/>
12A Barrowside Business Park, Carlow, Ireland
Registered in Ireland, Company No.: 370845
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg