RFC 4646: Tags for Identifying Languages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5646.
Current document in this lineage: RFC 3282 — Content Language Headers; RFC 4647 — Matching of Language Tags; RFC 5646 — Tags for Identifying Languages
In plain English — editorial summary, not part of the RFC
This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document, in combination with RFC 4647, replaces RFC 3066, which replaced RFC 1766. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4646
- Published
- September 2006
- Authors
- A. Phillips; M. Davis
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- app
- Pages
- 59
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4647Matching of Language TagsCurrent
September 2006
- RFC 1766Tags for the Identification of LanguagesObsoleted
March 1995
- RFC 4645Initial Language Subtag RegistryCurrent
September 2006
- RFC 4644Network News Transfer Protocol (NNTP) Extension for Streaming FeedsCurrent
October 2006
- RFC 4643Network News Transfer Protocol (NNTP) Extension for AuthenticationCurrent
October 2006
- RFC 4642Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)Updated
October 2006
- RFC 4698IRIS: An Address Registry (areg) Type for the Internet Registry Information ServiceCurrent
October 2006
- RFC 4551IMAP Extension for Conditional STORE Operation or Quick Flag Changes ResynchronizationObsoleted
June 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?