draft-ietf-ltru-4645bis-07.txt   draft-ietf-ltru-4645bis-08.txt 
Network Working Group D. Ewell, Ed. Network Working Group D. Ewell, Ed.
Internet-Draft Consultant Internet-Draft Consultant
Intended status: Informational November 1, 2008 Intended status: Informational November 26, 2008
Expires: May 5, 2009 Expires: May 30, 2009
Update to the Language Subtag Registry Update to the Language Subtag Registry
draft-ietf-ltru-4645bis-07 draft-ietf-ltru-4645bis-08
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 May 5, 2009. This Internet-Draft will expire on May 30, 2009.
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 3, line 11 skipping to change at page 3, line 11
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 946 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 946
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 947 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 947
Intellectual Property and Copyright Statements . . . . . . . . . 948 Intellectual Property and Copyright Statements . . . . . . . . . 948
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-18] expands on [RFC4646] by adding support [draft-ietf-ltru-4646bis-19] 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-18]. [draft-ietf-ltru-4646bis-19].
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-18], Section 3. In its Internet-Draft [draft-ietf-ltru-4646bis-19], 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 52 skipping to change at page 4, line 52
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 was Table 3,
"Language families and groups ordered by identifier," from the PDF "Language families and groups ordered by identifier", from the PDF
version of the standard. version of the standard.
Language code elements that were already retired in [ISO639-3] prior Language code elements that were already retired in [ISO639-3] prior
to IESG approval of this memo were not listed in these files, and to IESG approval of this memo were not listed in these files, and
consequently were not considered in this update. 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
skipping to change at page 7, line 8 skipping to change at page 7, line 8
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] that was already represented in the
Language Subtag Registry, the Description field was adjusted as Language Subtag Registry, the Description field was adjusted as
necessary to match the "English name" field in [ISO639-5]. Names in necessary to match the "English name" field in [ISO639-5]. Names in
inverted form were rearranged to remove the inversion. Each of these inverted form were rearranged to remove the inversion. Each of these
languages was assigned a Scope value of "collection". Existing languages was assigned a Scope value of "collection". Existing
language subtags whose code elements were assigned prior to the language subtags whose code elements were assigned prior to the
publication of [ISO639-3] or [ISO639-5] and which were identified by publication of [ISO639-3] or [ISO639-5] and which were identified by
the [ISO639-3] Registration Authority as representing collections 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].
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].
As a result of discussions with officials from the [ISO639-2] and As a result of discussions with officials from the [ISO639-2] and
[ISO639-3] registration agencies, it was determined that the existing [ISO639-3] registration agencies, it was determined that the existing
language subtag 'car' would retain its existing Description, "Galibi language subtag 'car' would retain its existing Description, "Galibi
skipping to change at page 7, line 32 skipping to change at page 7, line 32
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-18] expands the scope of region subtags by [draft-ietf-ltru-4646bis-19] 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-18], Section 3.4, item 15 (D) states that [draft-ietf-ltru-4646bis-19], 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-18], "grandfathered" and As stated in [draft-ietf-ltru-4646bis-19], "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-18] may cause a grandfathered tag to be [draft-ietf-ltru-4646bis-19] 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 39
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-18], Section 3.1.7 provides for the value of [draft-ietf-ltru-4646bis-19], 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
skipping to change at page 11, line 29 skipping to change at page 11, line 29
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-18], Section 2.1.1. This has no effect on [draft-ietf-ltru-4646bis-19], 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-18], Section 3.1.2. This ordering is not [draft-ietf-ltru-4646bis-19], Section 3.1.2. This ordering is not
required by [draft-ietf-ltru-4646bis-18] and may not necessarily be required by [draft-ietf-ltru-4646bis-19] 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 26, line 26 skipping to change at page 26, line 26
Subtag: mn Subtag: mn
Description: Mongolian Description: Mongolian
Added: 2005-10-16 Added: 2005-10-16
Scope: macrolanguage Scope: macrolanguage
%% %%
Type: language Type: language
Subtag: mo Subtag: mo
Description: Moldavian Description: Moldavian
Description: Moldovan Description: Moldovan
Added: 2005-10-16 Added: 2005-10-16
Preferred-Value: ro
Deprecated: 2008-11-22
Suppress-Script: Latn Suppress-Script: Latn
%% %%
Type: language Type: language
Subtag: mr Subtag: mr
Description: Marathi Description: Marathi
Added: 2005-10-16 Added: 2005-10-16
Suppress-Script: Deva Suppress-Script: Deva
%% %%
Type: language Type: language
Subtag: ms Subtag: ms
skipping to change at page 30, line 15 skipping to change at page 30, line 17
%% %%
Type: language Type: language
Subtag: rn Subtag: rn
Description: Rundi Description: Rundi
Added: 2005-10-16 Added: 2005-10-16
Suppress-Script: Latn Suppress-Script: Latn
%% %%
Type: language Type: language
Subtag: ro Subtag: ro
Description: Romanian Description: Romanian
Description: Moldavian
Description: Moldovan
Added: 2005-10-16 Added: 2005-10-16
Suppress-Script: Latn Suppress-Script: Latn
%% %%
Type: language Type: language
Subtag: ru Subtag: ru
Description: Russian Description: Russian
Added: 2005-10-16 Added: 2005-10-16
Suppress-Script: Cyrl Suppress-Script: Cyrl
%% %%
Type: language Type: language
skipping to change at page 938, line 8 skipping to change at page 938, 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-18]. and the use of language tags, see [draft-ietf-ltru-4646bis-19].
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-18]. [draft-ietf-ltru-4646bis-19].
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
skipping to change at page 944, line 24 skipping to change at page 944, line 24
[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-18] [draft-ietf-ltru-4646bis-19]
Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", October 2008, <http://www.ietf.org/ Languages", November 2008, <http://www.ietf.org/
internet-drafts/draft-ietf-ltru-4646bis-18.txt>. internet-drafts/draft-ietf-ltru-4646bis-19.txt>.
[iso-639-3-macrolanguages_20080218] [iso-639-3-macrolanguages_20080218]
International Organization for Standardization, "ISO 639-3 International Organization for Standardization, "ISO 639-3
Macrolanguage Mappings", January 2008, <http:// Macrolanguage Mappings", January 2008, <http://
www.sil.org/iso639-3/ www.sil.org/iso639-3/
iso-639-3-macrolanguages_20080218.tab>. iso-639-3-macrolanguages_20080218.tab>.
[iso-639-3_20081023] [iso-639-3_20081023]
International Organization for Standardization, "ISO 639-3 International Organization for Standardization, "ISO 639-3
Code Set", October 2008, Code Set", October 2008,
skipping to change at page 945, line 36 skipping to change at page 945, line 36
[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.
[RFC4645] Ewell, D., "Initial Language Subtag Registry", RFC 4645, [RFC4645] Ewell, D., "Initial Language Subtag Registry", RFC 4645,
September 2006. September 2006.
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 4646, September 2006. Languages", BCP 47, RFC 4646, September 2006.
[UN_M.49] Statistics Division, United Nations, "Standard Country or [UN_M.49] Statistics Division, United Nations, "Standard Country or
Area Codes for Statistical Use", UN Standard Country or Area Codes for Statistical Use", Revision 4 (United
Area Codes for Statistical Use, Revision 4 (United Nations Nations publication, Sales No. 98.XVII.9, June 1999.
publication, Sales No. 98.XVII.9), June 1999.
Appendix A. Acknowledgements Appendix A. Acknowledgements
This memo is a collaborative work of the Language Tag Registry Update This memo is a collaborative work of the Language Tag Registry Update
(LTRU) Working Group. All of its members have made significant (LTRU) Working Group. All of its members have made significant
contributions to this memo and to its predecessor, [RFC4645]. contributions to this memo and to its predecessor, [RFC4645].
Specific contributions to this memo were made by Stephane Bortzmeyer, Specific contributions to this memo were made by Stephane Bortzmeyer,
John Cowan, Mark Davis, Martin Duerst, Frank Ellermann, Debbie John Cowan, Mark Davis, Martin Duerst, Frank Ellermann, Debbie
Garside, Kent Karlsson, Gerard Lang, Addison Phillips, Randy Presuhn, Garside, Kent Karlsson, Gerard Lang, Addison Phillips, Randy Presuhn,
 End of changes. 23 change blocks. 
26 lines changed or deleted 29 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/