[Ltru] Re: draft-ietf-ltru-4646bis-09.txt
"Frank Ellermann" <nobody@xyzzy.claranet.de> Sat, 01 December 2007 14:24 UTC
Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyTGd-0001uB-Q1; Sat, 01 Dec 2007 09:24:27 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IyTGc-0001u4-Fr for ltru-confirm+ok@megatron.ietf.org; Sat, 01 Dec 2007 09:24:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyTGc-0001tv-6G for ltru@lists.ietf.org; Sat, 01 Dec 2007 09:24:26 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IyTGb-0001GV-3z for ltru@lists.ietf.org; Sat, 01 Dec 2007 09:24:26 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IyTGO-0006Ir-N3 for ltru@lists.ietf.org; Sat, 01 Dec 2007 14:24:12 +0000
Received: from c-180-160-112.hh.dial.de.ignite.net ([62.180.160.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 01 Dec 2007 14:24:12 +0000
Received: from nobody by c-180-160-112.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Sat, 01 Dec 2007 14:24:12 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 01 Dec 2007 15:26:04 +0100
Organization: <http://purl.net/xyzzy>
Lines: 48
Message-ID: <firqpr$jjl$1@ger.gmane.org>
References: <200711291723.SAA00561@balsa.cetp.ipsl.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: c-180-160-112.hh.dial.de.ignite.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc:
Subject: [Ltru] Re: draft-ietf-ltru-4646bis-09.txt
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org
Elisabeth Porteneuve wrote: [2. about the 2006 ed. of ISO 3166 and 50 years] > Yes. Thanks for info, maybe the Netnews RFC can be updated in AUTH48 (it's actually almost irrelevant for Netnews, not the same situation as for 4646bis). > All change of the world in Europe in 1990's until the most recent > split into Serbia and Montenegro are related to the second world > war. To some extent the second war is being finished now. Kosovo will be the next. > I am optimistic, at least as far as Europe is concerned, to not > see much changes in country codes. I'm optimistic to see changes for regions where the population apparently wishes to gain independence of their "encompassing" country. For regions like Iraq or Somalia registering existing entities like Somaliland might be the best possible solution. > Concerning languages, I noted the inflation related to the > former Yugoslavia split - the Serbo-Croatian, or Yugoslavian, > was replicated with N different names. That is of course > politically sad, as all people from the former Yugoslavia > speaks Yugoslavian, Southern Slavic language (yug=south). Right, but ISO 639 has alpha3 code elements, they're likely never forced to "recycle" code elements. For country codes there's apparently also a tradition of creating "meaningful" code elements, so far that worked. YT is a counter-example, but still somehow related to maYoTte. > Eventually, I would be happy to answer any questions related > to ISO 3166/MA or ISO 3166-1 tables, or to provide in advance > information when changes may arise. Please feel free to ask > me directly (I will unsubscribe from ltru list shortly, going > back to browsing archives from time to time). Thanks, with Debbie's help we managed to avoid the ugliest traps and pitfalls for RFC 4646. For the DG+EA+IC+... zoo I hope that it won't pass an IAB review. The IETF isn't supposed to overrule RFC 1591 without first publishing a 1591bis (IMO, of couse, and obviously IANA already managed this stunt with its odd ccTLD EU). Frank _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Re: draft-ietf-ltru-4646bis-09.txt Elisabeth Porteneuve
- Re: [Ltru] Re: draft-ietf-ltru-4646bis-09.txt John Cowan
- Re: [Ltru] Re: draft-ietf-ltru-4646bis-09.txt Elisabeth Porteneuve
- [Ltru] Re: draft-ietf-ltru-4646bis-09.txt Frank Ellermann