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 specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5646
- Published
- September 2009
- Authors
- A. Phillips; M. Davis
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- app
- Pages
- 84
- Also known as
- BCP47
- Obsoletes:
- RFC 4646
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 5645Update to the Language Subtag RegistryCurrent
September 2009
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5608Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport ModelsCurrent
August 2009
- RFC 5689Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)Current
September 2009
- RFC 5698Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)Current
November 2009
- RFC 5592Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)Current
June 2009
- RFC 5591Transport Security Model for the Simple Network Management Protocol (SNMP)Current
June 2009
- RFC 5590Transport Subsystem for the Simple Network Management Protocol (SNMP)Current
June 2009
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?