Return-Path: Received: from eikenes.alvestrand.no ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Mon, 14 Mar 2005 03:33:41 +0100 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2876261B96 for ; Mon, 14 Mar 2005 03:33:41 +0100 (CET) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23953-03 for ; Mon, 14 Mar 2005 03:33:39 +0100 (CET) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id D6ABE61B89 for ; Mon, 14 Mar 2005 03:33:38 +0100 (CET) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DAfND-0000I0-FL; Sun, 13 Mar 2005 21:32:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DAfNB-0000Hk-Sl for ltru@megatron.ietf.org; Sun, 13 Mar 2005 21:32:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02934 for ; Sun, 13 Mar 2005 21:32:00 -0500 (EST) Received: from [63.247.76.195] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DAfQi-000180-9n for ltru@ietf.org; Sun, 13 Mar 2005 21:35:41 -0500 Received: from lns-p19-19-idf-82-65-139-89.adsl.proxad.net ([82.65.139.89] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DAfN5-0002Hm-K6; Sun, 13 Mar 2005 18:31:59 -0800 Message-Id: <6.1.2.0.2.20050314024326.03f4fd20@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 14 Mar 2005 02:57:06 +0100 To: "Doug Ewell" From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] "Obsolete" region subtags (was: Re: Update to proposed registry) In-Reply-To: <002701c52833$a99cdd00$030aa8c0@DEWELL> References: <20050314001938.PAYD5424.mta6.adelphia.net@megatron.ietf.org> <002701c52833$a99cdd00$030aa8c0@DEWELL> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: ltru@ietf.org X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no On 02:17 14/03/2005, Doug Ewell said: >Frank Ellermann wrote: > > Actually I'm more interested to have some format, whatever it > > is, then pretend that 3066bis existed 1990 or earlier, prove > > that some resulting regional tags would be plain nonsense > > today, and then really _think_ about this part in the draft. > >This was something Frank brought up a while back on ietf-languages. >He's concerned about the fact that the draft admits all ISO 3166 codes >ever approved since the inception of that standard (1974), even those >that have since been withdrawn. IMHO There is a problem here of who does what. The IANA most known table, to the point to be referred worldwide as "the IANA table" is the ccTLD table which documents the ICANN understanding of ISO 3166. Also, as I understand the MoU between IANA, IESG and ICANN this table is in the ICANN area of decision (and is quite influenced by GAC). Obviously ICANN is not going to wipe off or to create a country at whim. But there may be differences and delays. Let for example consider the EU case. Recently someone discussed the existence of European Greek vs. Greece and Cyprus Greeks. ICANN will give the possibility to document it: is that in line with your proposition. Pacific and Indian countries have asked similar extensions. What is the situation you want for PS? At the end of the day we will most probably get the same situation. But the WG-ltru is not the one in control or a second, linguistic, IANA version of ISO 3166 is to be created? Another point to consider. An IETF WG is charter oriented. When the Charter is completed, it is closed. My understanding is that the IESG has approved this WG for two tasks and a short duration. It can obviously be renewed. But I think we should not assumed it to be permanent - at least at this stage and without a proper guidance from the IESG. jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru