Message-Id: <6.1.2.0.2.20050104190432.0d9eb010@mail.jefsey.com>
Date: Tue, 04 Jan 2005 19:14:09 +0100
To: John C Klensin <john-ietf@jck.com>, ietf-languages@alvestrand.no,
	ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <DD345C015189663441CBB81D@scan.jck.com>
References: <20050102035503.67030621E0@eikenes.alvestrand.no>
	<200501040938.55067.blilly@erols.com>
	<DD345C015189663441CBB81D@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed;
	x-avg-checked=avg-ok-7F11382D
Cc: iesg@ietf.org
Subject: Re: IDN and language
Precedence: list
Sender: ietf-languages-bounces@alvestrand.no
Errors-To: ietf-languages-bounces@alvestrand.no

At 18:06 04/01/2005, John C Klensin wrote:
>Returning to the DNS/IDN situation, ICANN has created a
>recommendation for all TLDs, and a requirement on at least some
>gTLDs, that languages not be mixed within a label and for
>registration and use of tables similar to those recommended by
>RFC 3743.  Those tables are identified by a combination of the
>Domain name associated with the registering TLD registry and a
>3066 code.  That system is not, IMO, working especially well and
>the 3066 code model will, I think, have to be extended to deal
>with some unusual situations.   But, interestingly,
>draft-phillips... doesn't appear to solve that particular
>problem: what is needed is a way to specify odd mixtures of
>languages and/or scripts that may be appropriate to a particular
>zone, and that means less specificity and more
>linguistically-strange constructions, not more specificity and
>structure.

The real problem is the confusion all this introduce because it is not a 
consensual draft by an IETF WG working along an IAB approved Charter, what 
is odd when the discussed RFC was authored by the IESG Chair and the 
private mailing list hosted under his name with the name "ietf-language" 
what is confusing to many.

At this stage, we can only say that there is no consensus on what is 
discussed, on the problems to solve and the proposed solutions. But that 
there is no reason why there would not be such a consensus when the charter 
I outlined yesterday would have been carried.
jfc 

_______________________________________________
Ietf-languages mailing list
Ietf-languages@alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages