headers
John C Klensin | 30 Apr 23:18

Two Internet Drafts of possible interest

Hi.

I've just posted new version of 
draft-klensin-reg-guidelines-03.txt and 
draft-klensin-idn-tld-02.txt.  The former is an attempt to 
discuss the issues involved in modifying the JET Guidelines (RFC 
3743) and applying them to non-CJK languages and scripts, 
replacing (with some encouragement from Paul) both 
draft-klensin-reg-guidelines-0(0 1 2) and 
draft-hoffman-idn-reg-02.txt.  The latter is a discussion of an 
alternate approach to the "multilingual TLD" issue.  The more 
common suggestions for dealing with that issue is to create 
additional root entries for the "translation" of the domain 
names into various languages.

Neither of these drafts are part of the agenda of the (former) 
IDN WG, since they move well into the area of thinking about 
policy and applications of IDNA that the WG excluded.  But, 
since I'm about to attempt a conversation with the IESG about 
what to do with them -- and to hand them off to the RFC Editor 
as individual submissions if the IESG doesn't see an appropriate 
way to process them as IETF documents -- it seems like the right 
time to call them to the attention of this mailing list in the 
event that anyone has comments.  Assume you have a week or less 
-- I'd like to get this in motion before I leave for INET.

best,
   john
(Continue reading)

Permalink | Reply | 2 comments |
headers
Adam M. Costello | 1 May 23:37

Re: Two Internet Drafts of possible interest

John C Klensin <klensin <at> jck.com> wrote:

> http://www.ietf.org/internet-drafts/draft-klensin-idn-tld-02.txt

Section 3.1:

> A user in Korea who can access the national ccTLD in the Korean
> language and character set has every reason to expect that both
> generic top level domains and domains associated with other countries
> would be similarly accessible, especially if the second-level domains
> bear Korean names.

If there are Korean labels registered under a France TLD, then users
would certainly benefit from being able to access those domains using a
Korean translation of ".fr".  I see no benefit in ensuring that French
or Chinese labels are accessible under the Korean translation of ".fr".
If a solution happens to make domains accessible under counter-intuitive
TLDs (via some sort of local or global aliasing), that's fine, but it
doesn't need to be a goal.

> That level of local optimization is not realistic -- some would
> argue not possible -- with the DNS since it would ultimately require
> that every top level domain be replicated for each of the world's
> languages.  That replication process would involve not just the top
> level domain itself: in principle, all of its subtrees would need to
> be completely replicated as well.

I don't see the benefit of replicating the subtrees.  If Korean and
Chinese translations of ".fr" exist, and if I have a server that I
want to be accessible via Korean and Chinese domain names, why would I
(Continue reading)

Permalink | Reply | 1 comment |

Gmane