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; Wed, 29 Jun 2005 02:15:18 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 518D661B4C for ; Wed, 29 Jun 2005 02:15:18 +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 18668-08 for ; Wed, 29 Jun 2005 02:15:14 +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 5783161AF3 for ; Wed, 29 Jun 2005 02:15:10 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnQBz-0001t8-Nt; Tue, 28 Jun 2005 20:12:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnQBu-0001sy-No for ietf@megatron.ietf.org; Tue, 28 Jun 2005 20:12:35 -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 UAA12759 for ; Tue, 28 Jun 2005 20:12:33 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnQbM-0001EZ-Ob for ietf@ietf.org; Tue, 28 Jun 2005 20:38:53 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DnQBI-0005Tp-55; Tue, 28 Jun 2005 17:12:29 -0700 Message-Id: <6.2.1.2.2.20050629004548.04950a60@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 29 Jun 2005 02:11:43 +0200 To: "Randy Presuhn" , From: "JFC (Jefsey) Morfin" In-Reply-To: <011a01c57c1f$5224c8e0$7f1afea9@oemcomputer> References: <200506271728.j5RHSOK4010945@cichlid.raleigh.ibm.com> <22563.1119937030@munnari.OZ.AU> <5F1B6D95C0DBE599ACBA1A9F@scan.jck.com> <1452A05293A1AAB40A2E4A62@gloppen.hjemme.alvestrand.no> <6.2.1.2.2.20050628153555.03eb3eb0@mail.jefsey.com> <011a01c57c1f$5224c8e0$7f1afea9@oemcomputer> 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: 7aafa0432175920a4b3e118e16c5cb64 Cc: Subject: Re: RFC 2434 term "IESG approval" (Re: IANA Action: Assignment of an IPV6 Hop-by-hop Option) X-BeenThere: ietf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-bounces@ietf.org Errors-To: ietf-bounces@ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no This is a beautifull troll :-) However the good of the WG-ltru work calls for short comments where we will probably partly agree. At 22:23 28/06/2005, Randy Presuhn wrote: > > The review of the management of the IANA langtag registry is subject to > > the work of the WG-ltru. http://ietf.org/html.charters/ltru-charter.html > >Thank you for the advertisement. We are very close to WG last call, so >I urge those interested to join now. Yes! This is really an important issue. Not usual IEFT but important. >There are more than two WG participants whose first language is not English. True. I should have said as regular contributors. We need more. >Some members are linguists by training, and the WG includes experts in >internationalization. Yes. But we are missing experts in networking, Internet standard process, multilingualism, national cultures, LDAP, standard document witing. This is a actually complex issue (mix of lingual subjective and networking/standardisation precise issues). > > The consistency with ISO 11179 (Registries continuity) and the work IETF > > should carry in that area, is precisely what would prevent cases like the > > HBH case and determine how such parameters should be recorded and where. >... > >The ltru WG consensus was to not delay our work in order to align with ISO >11179. This is unfortunately a self-evaluation of the WG current consensus process ... I say this because the WG charter says "[the Dratf/WG] is also expected to provide mechanisms to support the evolution of the underlying ISO standards". The ISO 639-6 and ISO 639-4 persons (present on the list) explained these two standards will comply with ISO 11179. ISO 639-4 defines the guidelines for all the language standards used by the WG. This consensus therefore opposes the charter (but if the Draft does not want to be BCP 47, this is IMHO acceptable, but must be discussed). Anyway I understand the concern as ISO 11179 is a "big" thing. It is also key element of the future. And certainly the key of the evolution of RFC 2434 if to stay compatible with the global convergence. Interesting to share here. Beware: ISO 11179 is not finished and already an heavy document. IETF should work on its network/multilingual simplification. jfc _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf