IETF Logo Mail Archive

RE: RFC 3066 bis Libraries list

"Peter Constable" <petercon@microsoft.com> Mon, 12 September 2005 04:38 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEg5q-0000Js-CN; Mon, 12 Sep 2005 00:38:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEg5o-0000J9-7E for ietf@megatron.ietf.org; Mon, 12 Sep 2005 00:38:56 -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 AAA10601 for <ietf@ietf.org>; Mon, 12 Sep 2005 00:38:44 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEg9n-0006qM-5x for ietf@ietf.org; Mon, 12 Sep 2005 00:43:04 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 11 Sep 2005 21:38:35 -0700
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 11 Sep 2005 21:38:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Sep 2005 21:38:33 -0700
Message-ID: <F8ACB1B494D9734783AAB114D0CE68FE0712E303@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: RFC 3066 bis Libraries list
thread-index: AcW265y0QVhpooVPS4+mFcwLy2hlzgAZimuA
From: Peter Constable <petercon@microsoft.com>
To: ietf@ietf.org
X-OriginalArrivalTime: 12 Sep 2005 04:38:34.0866 (UTC) FILETIME=[D5E52520:01C5B753]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
Subject: RE: RFC 3066 bis Libraries list
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>

> RFC 3066 Bis imposes new constraints on the existing language tags
> software libraries.

We need to be more careful in describing the proposed revision to RFC
3066 (aka RFC 3066 bis) wrt exiting libraries that conform to RFC 3066:
every tag valid under the terms of RFC 3066 bis will be recognized by an
existing library written to conform to RFC 3066. Not every tag that
*could* be recognized by such a library would be valid under RFC 3066
bis, but every tag actually valid today under RFC 3066 is also valid
under RFC 3066 bis.


The draft was written with careful attention to ensuring compatibility
with existing libraries written to support RFC 3066. The draft can be
said to impose new constraints that existing libraries would not impose;
I don't see how it could be said that the draft imposes new constraints
on those libraries.



Peter Constable

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

v2.23.0 | Report a Bug | By Email