BCP 166, RFC 6365 on Terminology Used in Internationalization in the IETF
rfc-editor@rfc-editor.org Wed, 07 September 2011 21:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2384F21F87FC; Wed, 7 Sep 2011 14:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Level:
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f1HIfd+asuHh; Wed, 7 Sep 2011 14:41:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8783021F8B84; Wed, 7 Sep 2011 14:41:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 19FE198C284; Wed, 7 Sep 2011 14:43:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 166, RFC 6365 on Terminology Used in Internationalization in the IETF
From: rfc-editor@rfc-editor.org
Message-Id: <20110907214310.19FE198C284@rfc-editor.org>
Date: Wed, 07 Sep 2011 14:43:10 -0700
Cc: apps-discuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2011 21:41:24 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 166
RFC 6365
Title: Terminology Used in Internationalization in
the IETF
Author: P. Hoffman, J. Klensin
Status: Best Current Practice
Stream: IETF
Date: September 2011
Mailbox: paul.hoffman@vpnc.org,
john+ietf@jck.com
Pages: 47
Characters: 103155
Obsoletes: RFC3536
See Also: BCP0166
I-D Tag: draft-ietf-appsawg-rfc3536bis-06.txt
URL: http://www.rfc-editor.org/rfc/rfc6365.txt
This document provides a list of terms used in the IETF when
discussing internationalization. The purpose is to help frame
discussions of internationalization in the various areas of the IETF
and to help introduce the main concepts to IETF participants.
This memo documents an Internet Best Current Practice.
This document is a product of the Applications Area Working Group Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC