[Ltru] Re: [EAI] New draft for allowing UTF-8 in SMTP responses

"Doug Ewell" <dewell@adelphia.net> Sat, 19 August 2006 18:17 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEVNf-0007Pm-S3; Sat, 19 Aug 2006 14:17:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEVNe-0007PV-DX for ltru@ietf.org; Sat, 19 Aug 2006 14:17:10 -0400
Received: from mta9.adelphia.net ([68.168.78.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GEVNd-0001G0-4s for ltru@ietf.org; Sat, 19 Aug 2006 14:17:10 -0400
Received: from DGBP7M81 ([69.162.95.23]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20060819181704.EOZX14558.mta9.adelphia.net@DGBP7M81>; Sat, 19 Aug 2006 14:17:04 -0400
Message-ID: <004801c6c3bb$a92d3250$040aa8c0@DGBP7M81>
From: Doug Ewell <dewell@adelphia.net>
To: LTRU Working Group <ltru@ietf.org>
References: <E1GETFA-0006Rx-72@megatron.ietf.org>
Date: Sat, 19 Aug 2006 11:16:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: alexey.melnikov@isode.com
Subject: [Ltru] Re: [EAI] New draft for allowing UTF-8 in SMTP responses
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>
Errors-To: ltru-bounces@ietf.org

Martin Duerst <duerst at it dot aoyama dot ac dot jp> wrote:

> Section 3: "It also recommends that server recognizes languges that
>   have multiple different tags (for example "ru" and "rus")."
>
>   This is a bad idea. RFC 3066, and its successor RFC 3066bis
>   (draft-ietf-ltru-registry-14.txt, approved by the IESG and in
>    operation) both make it very clear that for languages that
>   have both two-letter and three-letter codes, only the two-letter
>   codes are used.
>
> Please update the reference to RFC 3066 to RFC3066bis.

In fact, if you update the reference to RFC 3066bis, your references to 
ISO 639-1 and ISO 639-2 (e.g. in Example 3 or Section 3) should be 
replaced by references to the IANA Language Subtag Registry:

http://www.iana.org/assignments/language-subtag-registry

This contains all valid subtags that can be used to generate a language 
tag according to the rules of RFC 3066bis.  Applications that implement 
your protocol may use a local copy of the Registry; they are not 
required to download the IANA-hosted copy on each use.

Using this model, the question about "rus" goes away, since that subtag 
does not exist in the Registry.

--
Doug Ewell
Fullerton, California, USA
http://users.adelphia.net/~dewell/
Editor, draft-ietf-ltru-initial



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