draft-ietf-ltru-4645bis-09.txt   draft-ietf-ltru-4645bis-10.txt 
Network Working Group D. Ewell, Ed. Network Working Group D. Ewell, Ed.
Internet-Draft Consultant Internet-Draft Consultant
Intended status: Informational February 1, 2009 Intended status: Informational February 24, 2009
Expires: August 5, 2009 Expires: August 28, 2009
Update to the Language Subtag Registry Update to the Language Subtag Registry
draft-ietf-ltru-4645bis-09 draft-ietf-ltru-4645bis-10
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 5, 2009. This Internet-Draft will expire on August 28, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This memo defines the procedure used to update the IANA Language This memo defines the procedure used to update the IANA Language
Subtag Registry in conjunction with the publication of RFC 4646bis Subtag Registry in conjunction with the publication of RFC 4646bis
[RFC EDITOR NOTE: replace with actual RFC number], for use in forming [RFC EDITOR NOTE: replace with actual RFC number], for use in forming
tags for identifying languages. As an Internet-Draft, it also tags for identifying languages. As an Internet-Draft, it also
contained a complete replacement of the contents of the Registry to contained a complete replacement of the contents of the Registry to
be used by IANA in updating it. To prevent confusion, this material be used by IANA in updating it. To prevent confusion, this material
was removed before publication. was removed before publication.
skipping to change at page 2, line 32 skipping to change at page 2, line 32
2.4. New Region Subtags . . . . . . . . . . . . . . . . . . . 7 2.4. New Region Subtags . . . . . . . . . . . . . . . . . . . 7
2.5. Grandfathered and Redundant Tags . . . . . . . . . . . . 8 2.5. Grandfathered and Redundant Tags . . . . . . . . . . . . 8
2.6. Preferred-Value Changes . . . . . . . . . . . . . . . . . 10 2.6. Preferred-Value Changes . . . . . . . . . . . . . . . . . 10
2.7. Additional Changes . . . . . . . . . . . . . . . . . . . 11 2.7. Additional Changes . . . . . . . . . . . . . . . . . . . 11
3. Updated Registry Contents . . . . . . . . . . . . . . . . . . 12 3. Updated Registry Contents . . . . . . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 941 4. Security Considerations . . . . . . . . . . . . . . . . . . . 941
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 942 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 942
6. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 943 6. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 947 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 947
7.1. Normative References . . . . . . . . . . . . . . . . . . 947 7.1. Normative References . . . . . . . . . . . . . . . . . . 947
7.2. Informative References . . . . . . . . . . . . . . . . . 947 7.2. Informative References . . . . . . . . . . . . . . . . . 948
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 949 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 949
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 950 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 950
1. Introduction 1. Introduction
[RFC4646] provided for a Language Subtag Registry and described its [RFC4646] provided for a Language Subtag Registry and described its
format. The initial contents of the Registry and rules for format. The initial contents of the Registry and rules for
determining them were specified in [RFC4645]. determining them were specified in [RFC4645].
[draft-ietf-ltru-4646bis-20] expands on [RFC4646] by adding support [draft-ietf-ltru-4646bis-21] expands on [RFC4646] by adding support
for approximately 7,500 new primary and extended language subtags for approximately 7,500 new primary and extended language subtags
based on [ISO639-3] and [ISO639-5] alpha-3 code elements, and seven based on [ISO639-3] and [ISO639-5] alpha-3 code elements, and seven
new region subtags based on [ISO3166-1] exceptionally reserved code new region subtags based on [ISO3166-1] exceptionally reserved code
elements. This memo describes the process of updating the Registry elements. This memo describes the process of updating the Registry
to include these additional subtags, and to make secondary changes to to include these additional subtags, and to make secondary changes to
the Registry that result from adding the new subtags and from other the Registry that result from adding the new subtags and from other
decisions made by the Language Tag Registry Update (LTRU) Working decisions made by the Language Tag Registry Update (LTRU) Working
Group. Group.
In its initial phase as an Internet-Draft, this memo also contained a In its initial phase as an Internet-Draft, this memo also contained a
complete replacement of the contents of the Language Subtag Registry complete replacement of the contents of the Language Subtag Registry
to be used by the Internet Assigned Numbers Authority (IANA) in to be used by the Internet Assigned Numbers Authority (IANA) in
updating it. This content was deleted from this memo prior to updating it. This content was deleted from this memo prior to
publication as an RFC. publication as an RFC.
The format of the Language Subtag Registry, and the definition and The format of the Language Subtag Registry, and the definition and
intended purpose of each of the fields, are described in intended purpose of each of the fields, are described in
[draft-ietf-ltru-4646bis-20]. [draft-ietf-ltru-4646bis-21].
The Registry is expected to change over time, as new subtags are The Registry is expected to change over time, as new subtags are
registered and existing subtags are modified or deprecated. The registered and existing subtags are modified or deprecated. The
process of updating the Registry is described in process of updating the Registry is described in
[draft-ietf-ltru-4646bis-20], Section 3. In its Internet-Draft [draft-ietf-ltru-4646bis-21], Section 3. In its Internet-Draft
phase, this memo did not define the permanent contents of the phase, this memo did not define the permanent contents of the
Registry and should not be represented as having done so. Registry and should not be represented as having done so.
Many of the subtags defined in the Language Subtag Registry are based Many of the subtags defined in the Language Subtag Registry are based
on code elements defined in [ISO639-1], [ISO639-2], [ISO639-3], on code elements defined in [ISO639-1], [ISO639-2], [ISO639-3],
[ISO639-5], [ISO3166-1], [ISO15924], and [UN_M.49]. The Registry is [ISO639-5], [ISO3166-1], [ISO15924], and [UN_M.49]. The Registry is
not a mirror of the code lists defined by these standards and should not a mirror of the code lists defined by these standards and should
not be used as one. not be used as one.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 20 skipping to change at page 4, line 20
2.1. Starting Point 2.1. Starting Point
The version of the Language Subtag Registry that was current at the The version of the Language Subtag Registry that was current at the
time of IESG approval of this memo served as the starting point for time of IESG approval of this memo served as the starting point for
this update. This version was created according to the process this update. This version was created according to the process
described in [RFC4645] and maintained according to the process described in [RFC4645] and maintained according to the process
described in [RFC4646]. described in [RFC4646].
The source data for [ISO639-3] used for this update consisted of The source data for [ISO639-3] used for this update consisted of
three files, available from the official site of the ISO 639-3 three files, available from the official site of the ISO 639-3
Registration Authority. [RFC EDITOR NOTE: these files may be updated Registration Authority. [RFC EDITOR NOTE: this file is updated from
before approval of this memo.] time to time. The version used in the preparation of this memo was
the one in place on February 24, 2009.]
o [iso-639-3_20090126] is a list of all language code elements in o [iso-639-3_20090210] is a list of all language code elements in
[ISO639-3], including the alpha-3 code element and reference name [ISO639-3], including the alpha-3 code element and reference name
for each code element. For example, the entry for the Dari for each code element. For example, the entry for the Dari
language contained the code element 'prs' and the name "Dari" language contained the code element 'prs' and the name "Dari"
(among other information). (among other information).
o [iso-639-3_Name_Index_20090126] is a list containing all names o [iso-639-3_Name_Index_20090210] is a list containing all names
associated with each language according to [ISO639-3], including associated with each language according to [ISO639-3], including
both inverted and non-inverted forms where appropriate. An both inverted and non-inverted forms where appropriate. An
"inverted" name is one which is altered from the usual English- "inverted" name is one which is altered from the usual English-
language order by moving adjectival qualifiers to the end, after language order by moving adjectival qualifiers to the end, after
the main language name, and separated by a comma. A code element the main language name, and separated by a comma. A code element
may have more than one entry in this file; the reference name and may have more than one entry in this file; the reference name and
its inverted form are usually, but not always, given in the first its inverted form are usually, but not always, given in the first
entry. For example, this file contained an entry for the code entry. For example, this file contained an entry for the code
element 'prs' with the name "Dari" (twice) and another entry with element 'prs' with the name "Dari" (twice) and another entry with
the names "Eastern Farsi" and "Farsi, Eastern". the names "Eastern Farsi" and "Farsi, Eastern".
skipping to change at page 4, line 51 skipping to change at page 4, line 52
o [iso-639-3-macrolanguages_20090120] is a list of all alpha-3 code o [iso-639-3-macrolanguages_20090120] is a list of all alpha-3 code
elements for languages that are encompassed by a macrolanguage in elements for languages that are encompassed by a macrolanguage in
[ISO639-3], together with the alpha-3 code element for the [ISO639-3], together with the alpha-3 code element for the
macrolanguage. For example, a line containing the code elements macrolanguage. For example, a line containing the code elements
'fas' and 'prs' indicated that the macrolanguage "Persian" 'fas' and 'prs' indicated that the macrolanguage "Persian"
encompasses the individual language "Dari". (Note that these encompasses the individual language "Dari". (Note that these
alpha-3 code elements may not have corresponded directly to alpha-3 code elements may not have corresponded directly to
subtags in the Registry, which uses 2-letter subtags derived from subtags in the Registry, which uses 2-letter subtags derived from
[ISO639-1] when possible.) [ISO639-1] when possible.)
The source data for [ISO639-5] used for this update was Table 3, The source data for [ISO639-5] used for this update consisted of one
"Language families and groups ordered by identifier", from the PDF file, available from the official site of the ISO 639-5 Registration
version of the standard. Authority. [RFC EDITOR NOTE: this file is updated from time to time.
The version used in the preparation of this memo was the one in place
on February 24, 2009.]
Language code elements that were already retired in [ISO639-3] prior o [iso639-5.tab.txt] is a list of all language code elements in
to IESG approval of this memo were not listed in these files, and [ISO639-5], including the alpha-3 code elements and English name
consequently were not considered in this update. for each code element. For example, this file includes an entry
containing the code element 'ira' and the name "Iranian languages"
(among other information).
Language code elements that were already retired in all of the source
standards prior to IESG approval of this memo were not listed in
these files, and consequently were not considered in this update.
The values of the File-Date field, the Added date for each new subtag The values of the File-Date field, the Added date for each new subtag
record, and the Deprecated date for each existing grandfathered or record, and the Deprecated date for each existing grandfathered or
redundant tag deprecated by this update were set to a date as near as redundant tag deprecated by this update were set to a date as near as
practical to the date of IESG approval of this memo. [RFC EDITOR practical to the date of IESG approval of this memo. [RFC EDITOR
NOTE: these dates are initially set to 2029-09-09 for easy NOTE: these dates are initially set to 2029-09-09 for easy
recognition, and MUST be updated during AUTH48.] recognition, and MUST be updated during AUTH48.]
2.2. New Language Subtags 2.2. New Language Subtags
skipping to change at page 6, line 7 skipping to change at page 6, line 16
to the corresponding primary language subtag. to the corresponding primary language subtag.
If the language was encompassed by a macrolanguage, as determined by If the language was encompassed by a macrolanguage, as determined by
[iso-639-3-macrolanguages_20090120], a Macrolanguage field was added [iso-639-3-macrolanguages_20090120], a Macrolanguage field was added
for the encompassed language, with a value equal to the subtag of the for the encompassed language, with a value equal to the subtag of the
macrolanguage. (Note that 'sgn' is defined as a "collection code" by macrolanguage. (Note that 'sgn' is defined as a "collection code" by
[ISO639-3] and hence is not included in that standard; therefore, no [ISO639-3] and hence is not included in that standard; therefore, no
Macrolanguage field was added for sign-language subtags.) Macrolanguage field was added for sign-language subtags.)
If the language was assigned a "Scope" value of 'M' (Macrolanguage) If the language was assigned a "Scope" value of 'M' (Macrolanguage)
in [iso-639-3_20090126], a Scope value of "macrolanguage" was added in [iso-639-3_20090210], a Scope value of "macrolanguage" was added
for the language. Otherwise, if the language was assigned a "Scope" for the language. Otherwise, if the language was assigned a "Scope"
value of 'S' (Special), a Scope value of "special" was added. Most value of 'S' (Special), a Scope value of "special" was added. Most
languages in [ISO639-3] have scope 'I' (Individual) and thus were not languages in [ISO639-3] have scope 'I' (Individual) and thus were not
assigned a Scope value in the Registry. assigned a Scope value in the Registry.
For each language in [ISO639-5] that was not already represented by a For each language in [iso639-5.tab.txt] that was not already
language subtag in the Language Subtag Registry, a new language represented by a language subtag in the Language Subtag Registry, a
subtag was added to the Registry, using the [ISO639-5] code element new language subtag was added to the Registry, using the [ISO639-5]
as the value for the Subtag field and the "English name" field as the code element as the value for the Subtag field and the "English name"
Description field. Each of these languages was assigned a Scope field as the Description field. Each of these languages was assigned
value of "collection" in the Registry. a Scope value of "collection" in the Registry.
All subtags were added to the Registry maintaining alphabetical order All subtags were added to the Registry maintaining alphabetical order
within each type of subtag: all 2-letter "language" subtags first, within each type of subtag: all 2-letter "language" subtags first,
then all 3-letter "language" subtags, and finally all "extlang" then all 3-letter "language" subtags, and finally all "extlang"
subtags. Some existing records were moved to ensure this order. subtags. Some existing records were moved to ensure this order.
2.3. Modified Language Subtags 2.3. Modified Language Subtags
For each language in [ISO639-3] that was already represented by a For each language in [ISO639-3] that was already represented by a
language subtag in the Language Subtag Registry, Description fields language subtag in the Language Subtag Registry, Description fields
were added as necessary to reflect all non-inverted names listed for were added as necessary to reflect all non-inverted names listed for
that language in [iso-639-3_Name_Index_20090126]. Any existing that language in [iso-639-3_Name_Index_20090210]. Any existing
Description fields which reflected inverted names, or which Description fields which reflected inverted names, or which
represented a strict subset of the information provided by the represented a strict subset of the information provided by the
[ISO639-3] name, were deleted. An example of the latter was the name [ISO639-3] name, were deleted. An example of the latter was the name
"Ainu" for the subtag 'ain', which provided less information than the "Ainu" for the subtag 'ain', which provided less information than the
[ISO639-3] name "Ainu (Japan)". [ISO639-3] name "Ainu (Japan)".
The order of Description fields was adjusted to ensure that the The order of Description fields was adjusted to ensure that the
reference name from [ISO639-3] was listed first, followed by other reference name from [ISO639-3] was listed first, followed by other
names from [ISO639-3] in the order presented by that standard, names from [ISO639-3] in the order presented by that standard,
followed by any other names already existing in the Registry. In followed by any other names already existing in the Registry. In
some cases this resulted in a reordering of Description fields for some cases this resulted in a reordering of Description fields for
existing entries, even when no new values were added. existing entries, even when no new values were added.
For each language that was encompassed by a macrolanguage in For each language that was encompassed by a macrolanguage in
[ISO639-3], a Macrolanguage field was added, with a value equal to [ISO639-3], a Macrolanguage field was added, with a value equal to
the subtag of the macrolanguage. the subtag of the macrolanguage.
For each language in [ISO639-5] that was already represented in the For each language in [iso639-5.tab.txt] that was already represented
Language Subtag Registry, the Description field was adjusted as in the Language Subtag Registry, the Description field was adjusted
necessary to match the "English name" field in [ISO639-5]. Names in as necessary to match the "English name" field in [iso639-5.tab.txt].
inverted form were rearranged to remove the inversion. Each of these Names in inverted form were rearranged to remove the inversion. Each
languages was assigned a Scope value of "collection". Existing of these languages was assigned a Scope value of "collection".
language subtags whose code elements were assigned prior to the Existing language subtags whose code elements were assigned prior to
publication of [ISO639-3] or [ISO639-5] and which were identified by the publication of [ISO639-3] or [ISO639-5] and which were identified
the [ISO639-3] Registration Authority as representing collections by the [ISO639-3] Registration Authority as representing collections
were also assigned a Scope value of "collection", even though they were also assigned a Scope value of "collection", even though they
are not listed as such in [ISO639-5]. are not listed as such in [iso639-5.tab.txt].
Note in particular that the change from [ISO639-2] names such as Note in particular that the change from [ISO639-2] names such as
"Afro-Asiatic (Other)" to [ISO639-5] names such as "Afro-Asiatic "Afro-Asiatic (Other)" to [ISO639-5] names such as "Afro-Asiatic
languages" implies a broadening of scope for some of these subtags, languages" implies a broadening of scope for some of these subtags,
designated "remainder groups" in [ISO639-5]. designated "remainder groups" in [ISO639-5]. While
[iso639-5.tab.txt] includes a field indicating which code elements
As a result of discussions with officials from the [ISO639-2] and are designated as "groups" or "remainder groups" in [ISO639-2],
[ISO639-3] registration agencies, it was determined that the existing [draft-ietf-ltru-4646bis-21] does not make this distinction, and
language subtag 'car' would retain its existing Description, "Galibi consequently this field was not used in updating the Language Subtag
Carib", and would continue to be identified as an individual language Registry.
(i.e. no Scope value), even though the code element was also present
in [ISO639-5] as a collection code with the name "Carib languages".
A Scope value of "private-use" was added for the unique record with A Scope value of "private-use" was added for the unique record with
Subtag value 'qaa..qtz'. This record has a Description of "Private Subtag value 'qaa..qtz'. This record has a Description of "Private
use" (changed from "PRIVATE USE") and corresponds to a range of code use" (changed from "PRIVATE USE") and corresponds to a range of code
elements that is reserved for private use in [ISO639-2]. The elements that is reserved for private use in [ISO639-2]. The
Description fields for script and region private-use subtags were Description fields for script and region private-use subtags were
also capitalized as "Private use". also capitalized as "Private use".
2.4. New Region Subtags 2.4. New Region Subtags
[draft-ietf-ltru-4646bis-20] expands the scope of region subtags by [draft-ietf-ltru-4646bis-21] expands the scope of region subtags by
adding subtags based on code elements defined as "exceptionally adding subtags based on code elements defined as "exceptionally
reserved" in [ISO3166-1]. These code elements are reserved by the reserved" in [ISO3166-1]. These code elements are reserved by the
ISO 3166 Maintenance Agency "at the request of national ISO member ISO 3166 Maintenance Agency "at the request of national ISO member
bodies, governments and international organizations". At the time of bodies, governments and international organizations". At the time of
IESG approval of this memo, ISO 3166/MA had defined nine IESG approval of this memo, ISO 3166/MA had defined nine
exceptionally reserved code elements, all of which were added to the exceptionally reserved code elements, all of which were added to the
Language Subtag Registry except for the following: Language Subtag Registry except for the following:
o 'FX' (Metropolitan France) was already present in the Language o 'FX' (Metropolitan France) was already present in the Language
Subtag Registry because it was an assigned [ISO3166-1] code Subtag Registry because it was an assigned [ISO3166-1] code
element from 1993 to 1997, but was deprecated with a Preferred- element from 1993 to 1997, but was deprecated with a Preferred-
Value of "FR". Value of "FR".
o 'UK' (United Kingdom) was not added because it is associated with o 'UK' (United Kingdom) was not added because it is associated with
the same UN M.49 code (826) as the existing region subtag 'GB'. the same UN M.49 code (826) as the existing region subtag 'GB'.
[draft-ietf-ltru-4646bis-20], Section 3.4, item 15 (D) states that [draft-ietf-ltru-4646bis-21], Section 3.4, item 15 (D) states that
a new region subtag is not added to the Language Subtag Registry a new region subtag is not added to the Language Subtag Registry
if it carries the same meaning as an existing region subtag. if it carries the same meaning as an existing region subtag.
2.5. Grandfathered and Redundant Tags 2.5. Grandfathered and Redundant Tags
As stated in [draft-ietf-ltru-4646bis-20], "grandfathered" and As stated in [draft-ietf-ltru-4646bis-21], "grandfathered" and
"redundant" tags are complete tags in the Language Subtag Registry "redundant" tags are complete tags in the Language Subtag Registry
that were registered under [RFC1766] or [RFC3066] and remain valid. that were registered under [RFC1766] or [RFC3066] and remain valid.
Grandfathered tags cannot be generated from a valid combination of Grandfathered tags cannot be generated from a valid combination of
subtags, while redundant tags can be. subtags, while redundant tags can be.
Under certain conditions, registration of a subtag under Under certain conditions, registration of a subtag under
[draft-ietf-ltru-4646bis-20] may cause a grandfathered tag to be [draft-ietf-ltru-4646bis-21] may cause a grandfathered tag to be
reclassified as redundant. It may also enable the creation of a reclassified as redundant. It may also enable the creation of a
generative tag with the same meaning as a grandfathered or redundant generative tag with the same meaning as a grandfathered or redundant
tag; in that case, the grandfathered or redundant tag is marked as tag; in that case, the grandfathered or redundant tag is marked as
Deprecated, and the generative tag (including the new subtag) becomes Deprecated, and the generative tag (including the new subtag) becomes
its Preferred-Value. its Preferred-Value.
As a result of adding the new subtags in this update, each of the As a result of adding the new subtags in this update, each of the
following grandfathered tags became composable and was reclassified following grandfathered tags became composable and was reclassified
as redundant, and was deprecated with the indicated generative tag as redundant, and was deprecated with the indicated generative tag
serving as the Preferred-Value: serving as the Preferred-Value:
skipping to change at page 10, line 39 skipping to change at page 10, line 45
In previous versions of the Registry, grandfathered tags that had In previous versions of the Registry, grandfathered tags that had
been deprecated as a result of adding an ISO 639-based language been deprecated as a result of adding an ISO 639-based language
subtag included a Comments field, with a value of the form "replaced subtag included a Comments field, with a value of the form "replaced
by ISO code xxx", where 'xxx' represented the new language subtag. by ISO code xxx", where 'xxx' represented the new language subtag.
These comments duplicated the information contained within the These comments duplicated the information contained within the
Preferred-Value field, and were deleted as part of this update. No Preferred-Value field, and were deleted as part of this update. No
changes were made to other Comments fields. changes were made to other Comments fields.
2.6. Preferred-Value Changes 2.6. Preferred-Value Changes
[draft-ietf-ltru-4646bis-20], Section 3.1.7 provides for the value of [draft-ietf-ltru-4646bis-21], Section 3.1.7 provides for the value of
Preferred-Value fields to be updated as necessary to reflect changes Preferred-Value fields to be updated as necessary to reflect changes
in one of the source standards. Accordingly, the Preferred-Value in one of the source standards. Accordingly, the Preferred-Value
fields for the following deprecated tags were changed: fields for the following deprecated tags were changed:
i-hak (changed from zh-hakka to hak) i-hak (changed from zh-hakka to hak)
zh-guoyu (changed from zh-cmn to cmn) zh-guoyu (changed from zh-cmn to cmn)
This makes it unnecessary for consumers of the Language Subtag This makes it unnecessary for consumers of the Language Subtag
Registry to follow a "chain" of Preferred-Values in order to arrive Registry to follow a "chain" of Preferred-Values in order to arrive
at a non-deprecated subtag. at a non-deprecated subtag.
2.7. Additional Changes 2.7. Additional Changes
For consistency with the handling of alternative names in language For consistency with the handling of alternative names in language
subtags, Description fields for script subtags taken from [ISO15924] subtags, Description fields for script subtags taken from [ISO15924]
skipping to change at page 11, line 29 skipping to change at page 11, line 34
Description fields in inverted form for script and region subtags Description fields in inverted form for script and region subtags
were rearranged to remove the inversion, for consistency with the were rearranged to remove the inversion, for consistency with the
handling of language subtags in Section 2.2 and Section 2.3. For handling of language subtags in Section 2.2 and Section 2.3. For
example, the Description field "Korea, Republic of" was changed to example, the Description field "Korea, Republic of" was changed to
"Republic of Korea". "Republic of Korea".
The capitalization of the Subtag fields for certain grandfathered and The capitalization of the Subtag fields for certain grandfathered and
redundant tags (sgn-BE-fr, sgn-BE-nl, sgn-CH-de, yi-latn) was redundant tags (sgn-BE-fr, sgn-BE-nl, sgn-CH-de, yi-latn) was
modified to conform with the capitalization conventions described in modified to conform with the capitalization conventions described in
[draft-ietf-ltru-4646bis-20], Section 2.1.1. This has no effect on [draft-ietf-ltru-4646bis-21], Section 2.1.1. This has no effect on
the validity or meaning of these tags. the validity or meaning of these tags.
The Description field for subtag 'sgn' was capitalized as "Sign The Description field for subtag 'sgn' was capitalized as "Sign
languages", to match the capitalization used for other languages in languages", to match the capitalization used for other languages in
[ISO639-5], even though this capitalization does not exactly match [ISO639-5], even though this capitalization does not exactly match
that used for code element 'sgn' in any of the ISO 639 parts. that used for code element 'sgn' in any of the ISO 639 parts.
The Deprecated field for the region subtag TP was modified from 2002- The Deprecated field for the region subtag TP was modified from 2002-
11-15 to 2002-05-20, to correct a clerical error. The corrected date 11-15 to 2002-05-20, to correct a clerical error. The corrected date
reflects the actual date the code element TP was withdrawn in reflects the actual date the code element TP was withdrawn in
[ISO3166-1]. [ISO3166-1].
The order of fields within records in the Registry was adjusted as The order of fields within records in the Registry was adjusted as
necessary to match the order in which these fields are described in necessary to match the order in which these fields are described in
[draft-ietf-ltru-4646bis-20], Section 3.1.2. This ordering is not [draft-ietf-ltru-4646bis-21], Section 3.1.2. This ordering is not
required by [draft-ietf-ltru-4646bis-20] and may not necessarily be required by [draft-ietf-ltru-4646bis-21] and may not necessarily be
reflected in future additions or modifications to the Registry. reflected in future additions or modifications to the Registry.
3. Updated Registry Contents 3. Updated Registry Contents
The remainder of this section specified the updated set of records The remainder of this section specified the updated set of records
for the Language Subtag Registry. This material was deleted before for the Language Subtag Registry. This material was deleted before
publication of this memo, to avoid any potential confusion with the publication of this memo, to avoid any potential confusion with the
Registry itself. The IANA Language Subtag Registry can be found at Registry itself. The IANA Language Subtag Registry can be found at
<http://www.iana.org/numbers.html> under "Language Tags". <http://www.iana.org/numbers.html> under "Language Tags".
skipping to change at page 417, line 51 skipping to change at page 417, line 51
Description: Langobardic Description: Langobardic
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: lnh Subtag: lnh
Description: Lanoh Description: Lanoh
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: lni Subtag: lni
Description: Lantanai Description: Daantanai'
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: lnj Subtag: lnj
Description: Leningitij Description: Leningitij
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: lnl Subtag: lnl
skipping to change at page 511, line 31 skipping to change at page 511, line 31
Description: Ngando (Central African Republic) Description: Ngando (Central African Republic)
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: nge Subtag: nge
Description: Ngemba Description: Ngemba
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: ngf Subtag: ngf
Description: Trans New Guinea Description: Trans-New Guinea languages
Added: 2029-09-09 Added: 2029-09-09
Scope: collection Scope: collection
%% %%
Type: language Type: language
Subtag: ngg Subtag: ngg
Description: Ngbaka Manza Description: Ngbaka Manza
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: ngh Subtag: ngh
skipping to change at page 563, line 20 skipping to change at page 563, line 20
Description: Tagargrent Description: Tagargrent
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: oub Subtag: oub
Description: Glio-Oubi Description: Glio-Oubi
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: oue Subtag: oue
Description: Oune Description: Ounge
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: oui Subtag: oui
Description: Old Uighur Description: Old Uighur
Added: 2029-09-09 Added: 2029-09-09
%% %%
Type: language Type: language
Subtag: oum Subtag: oum
Description: Ouma Description: Ouma
skipping to change at page 860, line 9 skipping to change at page 860, line 9
%% %%
Type: extlang Type: extlang
Subtag: icl Subtag: icl
Description: Icelandic Sign Language Description: Icelandic Sign Language
Added: 2029-09-09 Added: 2029-09-09
Preferred-Value: icl Preferred-Value: icl
Prefix: sgn Prefix: sgn
%% %%
Type: extlang Type: extlang
Subtag: ils
Description: International Sign
Added: 2029-09-09
Preferred-Value: ils
Prefix: sgn
%%
Type: extlang
Subtag: inl Subtag: inl
Description: Indonesian Sign Language Description: Indonesian Sign Language
Added: 2029-09-09 Added: 2029-09-09
Preferred-Value: inl Preferred-Value: inl
Prefix: sgn Prefix: sgn
%% %%
Type: extlang Type: extlang
Subtag: ins Subtag: ins
Description: Indian Sign Language Description: Indian Sign Language
Added: 2029-09-09 Added: 2029-09-09
skipping to change at page 941, line 8 skipping to change at page 941, line 8
Type: redundant Type: redundant
Tag: zh-yue Tag: zh-yue
Description: Cantonese Description: Cantonese
Added: 1999-12-18 Added: 1999-12-18
Deprecated: 2029-09-09 Deprecated: 2029-09-09
Preferred-Value: yue Preferred-Value: yue
4. Security Considerations 4. Security Considerations
For security considerations relevant to the Language Subtag Registry For security considerations relevant to the Language Subtag Registry
and the use of language tags, see [draft-ietf-ltru-4646bis-20]. and the use of language tags, see [draft-ietf-ltru-4646bis-21].
5. IANA Considerations 5. IANA Considerations
In its initial phase as an Internet-Draft, this memo contained a In its initial phase as an Internet-Draft, this memo contained a
complete replacement of the contents of the Language Subtag Registry complete replacement of the contents of the Language Subtag Registry
to be used by IANA in updating it. As an RFC, it contains a pointer to be used by IANA in updating it. As an RFC, it contains a pointer
to the Registry, which is maintained by IANA. The Language Subtag to the Registry, which is maintained by IANA. The Language Subtag
Registry can be found at <http://www.iana.org/numbers.html> under Registry can be found at <http://www.iana.org/numbers.html> under
"Language Tags". For details on the procedures for the format and "Language Tags". For details on the procedures for the format and
ongoing maintenance of this Registry, see ongoing maintenance of this Registry, see
[draft-ietf-ltru-4646bis-20]. [draft-ietf-ltru-4646bis-21].
6. Changes 6. Changes
[RFC EDITOR NOTE: This section is provided for the convenience of [RFC EDITOR NOTE: this section is provided for the convenience of
reviewers and will be removed from the final document.] reviewers and will be removed from the final document.]
This memo is a new work, not an incremental update of [RFC4645]. The This memo is a new work, not an incremental update of [RFC4645]. The
procedure for populating the original Language Subtag Registry, procedure for populating the original Language Subtag Registry,
specified by the earlier [RFC4646], is included by reference to specified by the earlier [RFC4646], is included by reference to
[RFC4645]. Therefore, no changes from [RFC4645] are listed in this [RFC4645]. Therefore, no changes from [RFC4645] are listed in this
section. section.
Changes between draft-ietf-ltru-4645bis-08 and this version are: Changes between draft-ietf-ltru-4645bis-09 and this version are:
o Updated references to draft-ietf-ltru-4646bis-21 and [ISO639-3]
data files.
o Updated Registry data to reflect new [ISO639-3] data.
o Added references to [ISO639-5] Web site and data file and removed
references to PDF file.
o Removed paragraph explaining conflict resolution for language
subtag 'car', since the conflict was resolved by the publication
of [ISO639-5] online data.
o Added extended language subtag "ils', omitted by mistake from
draft=ietf-ltru-4645bis-09.
Changes between draft-ietf-ltru-4645bis-08 and
draft-ietf-ltru-4645bis-09 were:
o Changed IPR boilerplate to conform to RFC 5378. o Changed IPR boilerplate to conform to RFC 5378.
o Updated references to draft-ietf-ltru-4646bis-20 and [ISO639-3] o Updated references to draft-ietf-ltru-4646bis-20 and [ISO639-3]
data files. data files.
o Updated Registry data to reflect new contents of Language Subtag o Updated Registry data to reflect new contents of Language Subtag
Registry and new [ISO639-3] data. Registry and new [ISO639-3] data.
o Changed rule slightly for assigning extlangs with "sgn" Prefix, as o Changed rule slightly for assigning extlangs with "sgn" Prefix, as
a result of ISO 639-3 adding a code for a sign language whose name a result of ISO 639-3 adding a code for a sign language whose name
does not include the words "Sign Language". does not include the words "Sign Language".
o Deleted Preferred-Value for language subtag 'YU' and added
comment.
Changes between draft-ietf-ltru-4645bis-07 and Changes between draft-ietf-ltru-4645bis-07 and
draft-ietf-ltru-4645bis-08 were: draft-ietf-ltru-4645bis-08 were:
o Minor editorial changes, including recasting all text in quotation o Minor editorial changes, including recasting all text in quotation
marks in British or so-called "logical" style. marks in British or so-called "logical" style.
o Updated reference to draft-ietf-ltru-4646bis-19. o Updated reference to draft-ietf-ltru-4646bis-19.
Changes between draft-ietf-ltru-4645bis-06 and Changes between draft-ietf-ltru-4645bis-06 and
draft-ietf-ltru-4645bis-07 were: draft-ietf-ltru-4645bis-07 were:
skipping to change at page 947, line 13 skipping to change at page 947, line 13
o Added Changes and Acknowledgements sections. o Added Changes and Acknowledgements sections.
7. References 7. References
7.1. Normative References 7.1. Normative References
[ISO639-3] [ISO639-3]
International Organization for Standardization, "ISO 639- International Organization for Standardization, "ISO 639-
3:2007. Codes for the representation of names of 3:2007. Codes for the representation of names of
languages - Part 3: Alpha-3 code for comprehensive languages - Part 3: Alpha-3 code for comprehensive
coverage of languages, first edition", February 2007. coverage of languages", February 2007.
[ISO639-5] [ISO639-5]
International Organization for Standardization, "ISO 639- International Organization for Standardization, "ISO 639-
5:2008. Codes for the representation of names of languages 5:2008. Codes for the representation of names of languages
-- Part 5: Alpha-3 code for language families and groups", -- Part 5: Alpha-3 code for language families and groups",
May 2008. May 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[draft-ietf-ltru-4646bis-20] [draft-ietf-ltru-4646bis-21]
Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", December 2008, <http://www.ietf.org/ Languages", February 2009, <http://www.ietf.org/
internet-drafts/draft-ietf-ltru-4646bis-20.txt>. internet-drafts/draft-ietf-ltru-4646bis-21.txt>.
[iso-639-3-macrolanguages_20090120] [iso-639-3-macrolanguages_20090120]
International Organization for Standardization, "ISO 639-3 International Organization for Standardization, "ISO 639-3
Macrolanguage Mappings", January 2009, <http:// Macrolanguage Mappings", January 2009, <http://
www.sil.org/iso639-3/ www.sil.org/iso639-3/
iso-639-3-macrolanguages_20090120.tab>. iso-639-3-macrolanguages_20090120.tab>.
[iso-639-3_20090126] [iso-639-3_20090210]
International Organization for Standardization, "ISO 639-3 International Organization for Standardization, "ISO 639-3
Code Set", January 2009, Code Set", February 2009,
<http://www.sil.org/iso639-3/iso-639-3_20090126.tab>. <http://www.sil.org/iso639-3/iso-639-3_20090210.tab>.
[iso-639-3_Name_Index_20090126] [iso-639-3_Name_Index_20090210]
International Organization for Standardization, "ISO 639-3 International Organization for Standardization, "ISO 639-3
Language Names Index", January 2009, <http://www.sil.org/ Language Names Index", February 2009, <http://www.sil.org/
iso639-3/iso-639-3_Name_Index_20090126.tab>. iso639-3/iso-639-3_Name_Index_20090210.tab>.
[iso639-5.tab.txt]
International Organization for Standardization, "ISO 639-5
code list, Tab-delimited text", February 2009,
<http://www.loc.gov/standards/iso639-5/iso639-5.tab.txt>.
7.2. Informative References 7.2. Informative References
[ISO15924] [ISO15924]
International Organization for Standardization, "ISO International Organization for Standardization, "ISO
15924:2004. Information and documentation -- Codes for 15924:2004. Information and documentation -- Codes for
the representation of names of scripts", January 2004. the representation of names of scripts", January 2004.
[ISO3166-1] [ISO3166-1]
International Organization for Standardization, "ISO 3166- International Organization for Standardization, "ISO 3166-
skipping to change at page 948, line 17 skipping to change at page 948, line 26
codes", November 2006. codes", November 2006.
[ISO639-1] [ISO639-1]
International Organization for Standardization, "ISO 639- International Organization for Standardization, "ISO 639-
1:2002. Codes for the representation of names of 1:2002. Codes for the representation of names of
languages -- Part 1: Alpha-2 code", July 2002. languages -- Part 1: Alpha-2 code", July 2002.
[ISO639-2] [ISO639-2]
International Organization for Standardization, "ISO 639- International Organization for Standardization, "ISO 639-
2:1998. Codes for the representation of names of 2:1998. Codes for the representation of names of
languages -- Part 2: Alpha-3 code, first edition", languages -- Part 2: Alpha-3 code", October 1998.
October 1998.
[RFC1766] Alvestrand, H., "Tags for the Identification of [RFC1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995. Languages", RFC 1766, March 1995.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999. June 1999.
[RFC3066] Alvestrand, H., "Tags for the Identification of [RFC3066] Alvestrand, H., "Tags for the Identification of
Languages", RFC 3066, January 2001. Languages", RFC 3066, January 2001.
 End of changes. 44 change blocks. 
76 lines changed or deleted 113 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/