Return-Path: <ltru-bounces@ietf.org>
Received: from murder ([unix socket])
	 by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA;
	 Fri, 09 Sep 2005 18:33:06 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (eikenes.alvestrand.no [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 036E4320092
	for <harald@alvestrand.no>; Fri,  9 Sep 2005 18:33:06 +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 23784-08 for <harald@alvestrand.no>;
 Fri,  9 Sep 2005 18:33:01 +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 AA85E32008F
	for <harald@alvestrand.no>; Fri,  9 Sep 2005 18:33:00 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDlnM-0002u0-7h; Fri, 09 Sep 2005 12:32:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDlnL-0002ts-Dv; Fri, 09 Sep 2005 12:32:07 -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 MAA13015;
	Fri, 9 Sep 2005 12:32:04 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EDlqv-0006rw-O9; Fri, 09 Sep 2005 12:35:52 -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 1EDln3-0006ne-Ry; Fri, 09 Sep 2005 09:31:50 -0700
Message-Id: <6.2.3.4.2.20050909171544.03e925e0@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Fri, 09 Sep 2005 18:31:47 +0200
To: "Doug Ewell" <dewell@adelphia.net>,
	"John C Klensin" <john-ietf@jck.com>,
	"Sam Hartman" <hartmans-ietf@mit.edu>
From: r&d afrac <rd@afrac.org>
In-Reply-To: <013101c5b550$313fc0c0$030aa8c0@DEWELL>
References: <DE3D67514661E20ADB65F357@scan.jck.com>
	<tslu0gy101q.fsf@cz.mit.edu>
	<EFAFFC7D681AFA7F592E18AF@scan.jck.com>
	<tslll29c2nn.fsf@cz.mit.edu>
	<02BD58E66D8134A92F365882@scan.jck.com>
	<013101c5b550$313fc0c0$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 - afrac.org
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ltru@ietf.org, iesg@ietf.org
Subject: [Ltru] Re: Last call comments on LTRU registry and initialization
 documents
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org
X-Virus-Scanned: by amavisd-new at alvestrand.no

The problem with your Draft is that you do not include the 3 letters 
version of the 2 letter version as a correlative information between 
ISO 639-2 and ISO 639-3 tables. I do not think should be left to the 
Editor. Otherwise your Draft seems no problem. But I suppose that 
IESG would need a formal OK from Michael Everson since he is charge 
of ietf-languages@alvestrand.no.
jfc

At 17:07 09/09/2005, Doug Ewell wrote:
>John C Klensin <john dash ietf at jck dot com> wrote:
>
> > The success or failure of the "foo" registry is
> > not evaluated on how many foos we can put in to it, or its
> > comprehensiveness relative to some external foo-list, but on
> > whether it does the job that the foo-protocol (and maybe foo1,
> > foo2, etc.), requires.  Normally, we don't even write a "create
> > the baz registry" document.  Instead, we write a "baz protocol
> > specification" document and include a more or less long section
> > that instructs IANA to create the registry, what to put in it,
> > and how.
>
>So, do you propose that we withdraw the specification of the initial
>registry contents, all 963 tags and subtags, and replace it with a set
>of instructions to IAN on how they can duplicate our work?  And cross
>our fingers that they get it right, or prepare to go through
>item-languages for any correctible errors or omissions they may
>introduce, and live with the uncorrectable errors?  Just wondering.
>
>--
>Doug Ewell
>Fullerton, California
>http://users.adelphia.net/~dewell/
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru