Re: [Ltru] RFC 3282: should we revise it?

"Phillips, Addison" <addison@amazon.com> Wed, 05 August 2009 05:32 UTC

Return-Path: <addison@amazon.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 CB5BC28C14C for <ltru@core3.amsl.com>; Tue, 4 Aug 2009 22:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.099
X-Spam-Level:
X-Spam-Status: No, score=-107.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 CcxQem8BZJ9e for <ltru@core3.amsl.com>; Tue, 4 Aug 2009 22:32:47 -0700 (PDT)
Received: from smtp-fw-9101.amazon.com (smtp-fw-9101.amazon.com [207.171.184.25]) by core3.amsl.com (Postfix) with ESMTP id E4CA53A7088 for <ltru@ietf.org>; Tue, 4 Aug 2009 22:32:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,326,1246838400"; d="scan'208";a="251770216"
Received: from smtp-in-0201.sea3.amazon.com ([172.20.19.24]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Aug 2009 05:32:43 +0000
Received: from ex-hub-4102.ant.amazon.com (ex-hub-4102.ant.amazon.com [10.248.163.23]) by smtp-in-0201.sea3.amazon.com (8.12.11/8.12.11) with ESMTP id n755Weqj008724 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Wed, 5 Aug 2009 05:32:40 GMT
Received: from EX-SEA5-D.ant.amazon.com ([10.248.163.30]) by ex-hub-4102.ant.amazon.com ([10.248.163.23]) with mapi; Tue, 4 Aug 2009 22:32:40 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, LTRU Working Group <ltru@ietf.org>
Date: Tue, 04 Aug 2009 22:32:39 -0700
Thread-Topic: [Ltru] RFC 3282: should we revise it?
Thread-Index: AcoVjOrtBAJSbTvTSrqRnJoolCrYrwAACu2w
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA01AC38CFBF@EX-SEA5-D.ant.amazon.com>
References: <4D25F22093241741BC1D0EEBC2DBB1DA01ABC815C8@EX-SEA5-D.ant.amazon.com> <032801ca158c$d088a020$6801a8c0@oemcomputer>
In-Reply-To: <032801ca158c$d088a020$6801a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Ltru] RFC 3282: should we revise it?
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: Wed, 05 Aug 2009 05:32:47 -0000

> 
> Hi -
> 
> As a technical contributor (returning from two blissful weeks
> without email) ...

Welcome back!

> >
> > The one bit of language tagging infrastructure that we have not
> revised
> > since this whole body of work has started is RFC 3282, which
> defines
> > Content-Language and Accept-Language.
> 
> That was outside the scope for which ltru was originally chartered.

I agree, hence:

> 
> > This morning I had cause to want to reference it, but a desire
> not to
> > (since it depends on 3066 rather than the current-and-future BCP
> 47).
> > I'm pretty sure that the whole machinery of a WG is not needed to
> > revise this document--I'm thinking it would make a suitable
> > individual submission.
> 
> I agree.
> 
> > But I thought I'd mention it here to see if anyone had thoughts
> about
> > whether it were necessary, whether this list would make a
> suitable
> > place to solicit comments,
> 
> (As co-chair) This seems reasonable for now.  If it turns out to
> require
> significant discussion, or if a better WG "home" appears, we
> can redirect the discussion at that time.

Sounds reasonable. I doubt another WG would appear to make a home for this. Ever the optimist, I would hope that such a revision wouldn't require the level of effort needed for the BCP 47 work.

> 
> > and whether anyone thought a WG charter were necessary for
> > same (this last I studiously hope is not the case).
> 
> (As technical contributor) I would not support adding this work
> to the ltru charter.
> 

Absolutely not (shudders). Thanks for the note.

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.