IETF Logo Mail Archive

Re: [Ltru] rechartering to handle 639-6

Mark Davis ⌛ <mark@macchiato.com> Mon, 13 July 2009 19:47 UTC

Return-Path: <mark.edward.davis@gmail.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F4A528C558 for <ltru@core3.amsl.com>; Mon, 13 Jul 2009 12:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.78
X-Spam-Level:
X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uieoX1yNTl2C for <ltru@core3.amsl.com>; Mon, 13 Jul 2009 12:47:26 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by core3.amsl.com (Postfix) with ESMTP id 5801228C41C for <ltru@ietf.org>; Mon, 13 Jul 2009 12:47:26 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c37so1178346anc.4 for <ltru@ietf.org>; Mon, 13 Jul 2009 12:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=62RYrA/D9pJHGeJD32IXowc3VydmNDqQYEWhDjVqm4U=; b=lbNkEOod/vzyN3hAClWdOT/uAtZMYME+JI38rolO8fWFTLEzuJtGja2OYiaXsucVPm qxraQbYkC3+zrvP8jf0pgoSQXwOUpTVQ6+Auo2T8HAmCNF8CkfGSomhMeV6Erkh5yeTv bNt7KtMROgS0Ph38akcf9DLNju9L9huIK37Cs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=U3udCC1h1iPE9POq+wtx6feX2VxdeKS4RSqpuHg+TZ23Fiv8StYvyLkYF1ZWYqBvm7 rtbkvMXpWdqmfzrc4d/pMtyCqjY4UkjL9GPnPAP96s3UXlYUSuy1gRkvPfQ8fW4dZ05y 7ecRqnwmDbMHShDOLbtLJv56D0sXapyZXSeSY=
MIME-Version: 1.0
Sender: mark.edward.davis@gmail.com
Received: by 10.100.231.8 with SMTP id d8mr7531095anh.196.1247514477330; Mon, 13 Jul 2009 12:47:57 -0700 (PDT)
In-Reply-To: <30b660a20907131247l6113dc52i8ec9656ba9805176@mail.gmail.com>
References: <4D25F22093241741BC1D0EEBC2DBB1DA01AB579874@EX-SEA5-D.ant.amazon.com> <000801ca03e0$6a22bea0$6801a8c0@oemcomputer> <30b660a20907131247l6113dc52i8ec9656ba9805176@mail.gmail.com>
Date: Mon, 13 Jul 2009 12:47:57 -0700
X-Google-Sender-Auth: 36fcc972e63d05e4
Message-ID: <30b660a20907131247n7b905b13ga404aa4f84610ab2@mail.gmail.com>
From: Mark Davis ⌛ <mark@macchiato.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary="0016368e207d460128046e9b99cb"
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] rechartering to handle 639-6
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 19:47:27 -0000

Actually, I agree on not rechartering for ISO 639-6. As to other matters, I
think we need to let the dust settle a bit.

Mark


On Mon, Jul 13, 2009 at 12:47, Mark Davis ⌛ <mark@macchiato.com> wrote:

> I agree.
>
> Mark
>
>
>
> On Mon, Jul 13, 2009 at 10:36, Randy Presuhn <randy_presuhn@mindspring.com
> > wrote:
>
>> Hi -
>>
>> As a technical contributor...
>>
>> I, too, oppose re-chartering ltru at this time.
>> The additions made by the documents recently approved
>> take us well past the point of diminishing returns
>> in terms of language coverage.
>>
>> What that might convince me that re-chartering was needed
>> would be the appearance large quantities of data in large
>> numbers of languages in use by substantial speech communities
>> not covered by the recent updates, and not adequately handled
>> by the registration procedures.  I don't think that's going to
>> happen anytime in the foreseeable future.
>>
>> Randy
>>
>> _______________________________________________
>> Ltru mailing list
>> Ltru@ietf.org
>> https://www.ietf.org/mailman/listinfo/ltru
>>
>
>

v2.23.0 | Report a Bug | By Email