BCP 47, RFC 3066 on Tags for Identification of Languages
RFC Editor <rfc-ed@ISI.EDU> Thu, 01 February 2001 19:11 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08278; Thu, 1 Feb 2001 14:11:35 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA29384 for ietf-123-outbound.10@ietf.org; Thu, 1 Feb 2001 13:55:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id NAA28929 for <all-ietf@loki.ietf.org>; Thu, 1 Feb 2001 13:19:34 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05434 for <all-ietf@ietf.org>; Thu, 1 Feb 2001 13:19:34 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA20074; Thu, 1 Feb 2001 10:19:34 -0800 (PST)
Message-Id: <200102011819.KAA20074@boreas.isi.edu>
To: IETF-Announce:;
Subject: BCP 47, RFC 3066 on Tags for Identification of Languages
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 Feb 2001 10:19:34 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
BCP 47
RFC 3066
Title: Tags for the Identification of Languages
Author(s): H. Alvestrand
Status: Best Current Practice
Date: January 2001
Mailbox: Harald@Alvestrand.no
Pages: 13
Characters: 26522
Obsoletes 1766
SeeAlso: BCP 47
I-D Tag: draft-alvestrand-lang-tag-v2-05.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3066.txt
This document describes a language tag for use in cases where it is
desired to indicate the language used in an information object, how to
register values for use in this language tag, and a construct for
matching such language tags.
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.