Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Fri, 29 Jul 2005 10:54:47 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (unknown [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 31D3A61AFD for ; Fri, 29 Jul 2005 10:54:47 +0200 (CEST) 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 29682-08 for ; Fri, 29 Jul 2005 10:54:44 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1F2E961AF5 for ; Fri, 29 Jul 2005 10:54:44 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyQc1-0000aY-VP; Fri, 29 Jul 2005 04:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyQbz-0000ZI-SQ for ltru@megatron.ietf.org; Fri, 29 Jul 2005 04:53:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21682 for ; Fri, 29 Jul 2005 04:52:57 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyR7c-0001Kf-DF for ltru@ietf.org; Fri, 29 Jul 2005 05:25:41 -0400 Received: from i03m-212-195-148-209.d4.club-internet.fr ([212.195.148.209] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DyQbl-0003Ud-H9; Fri, 29 Jul 2005 01:52:45 -0700 Message-Id: <6.2.1.2.2.20050729101334.03a9d350@mail.afrac.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 29 Jul 2005 10:28:04 +0200 To: "Debbie Garside" , "'Addison Phillips'" , "'Randy Presuhn'" , Martin Duerst From: r&d afrac Subject: RE: [Ltru] Re: ABNF beautification...Last Call question In-Reply-To: <200507282244.j6SMikln014092@smtp-los02.proxy.aol.com> References: <634978A7DF025A40BFEF33EB191E13BC0C3F986B@irvmbxw01.quest.com> <200507282244.j6SMikln014092@smtp-los02.proxy.aol.com> 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 - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - afrac.org X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a 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: amavisd-new at alvestrand.no At 00:45 29/07/2005, Debbie Garside wrote: >Hi All >Just to clarify, does the beautified ABNF mean that should 639-6 come to >pass it needs to wait for ter before it can be used or can it be used in >bis? If the latter then I am happy if not then I could be unhappy; given >the time it has taken to get bis to this stage! I am not good at ABNF. But I rose a Last Call point that language subtags are treated equal from 2 to 8 alphanums (what permits to ensure reasonable compatibility with every ISO and non ISO standard the IETF or the Internet Community ad-hoc entities would adopt). If this is not the case I rise another Last Call point, and if the Last Call is finished, this would be a new exclusion point to be addressed in their turn by IETF, IESG, IAB, IANA and GAC with appeal to WTO. But by that time everything will be ruled discussed on the UN Internet Governance Forum. So, I am not sure you can deduce anything from the current status of "numerobis" (cf. Asterix & Cleopatre). I suppose that ISO 639-6 will be for long in use in various network protocols before the current Draft is enforced by the IANA... This however depends on its authors. I know some would love to make ISO 639-6 depend on this Draft and on its "consensus" that Randy and Martin will probably announce anytime soon (under their co-Chair responsibility). This is a mistake. BTW I wait for the information I asked you. jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru