RFC 4647: Matching of Language Tags
In plain English — editorial summary, not part of the RFC
This document describes a syntax, called a "language-range", for specifying items in a user's list of language preferences. It also describes different mechanisms for comparing and matching these to language tags. Two kinds of matching mechanisms, filtering and lookup, are defined. Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag. Possible applications include language negotiation or content selection. This document, in combination with RFC 4646, 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
- RFC4647
- Published
- September 2006
- Authors
- A. Phillips; M. Davis
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- app
- Pages
- 20
- Also known as
- BCP47
- Obsoletes:
- RFC 3066
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4646Tags for Identifying LanguagesObsoleted
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?