RFC 5646: Tags for Identifying Languages

This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language…

Read RFC 5646 on the RFC Editor

Outgoing relationships (21 related RFCs)

Obsoletes, Informative reference — RFC 4646: Tags for Identifying Languages
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 2026: The Internet Standards Process -- Revision 3
Normative reference — RFC 3339: Date and Time on the Internet: Timestamps
Normative reference — RFC 2277: IETF Policy on Character Sets and Languages
Normative reference — RFC 4647: Matching of Language Tags
Informative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 3552: Guidelines for Writing RFC Text on Security Considerations
Informative reference — RFC 1766: Tags for the Identification of Languages
Informative reference — RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Informative reference — RFC 2781: UTF-16, an encoding of ISO 10646
Informative reference — RFC 3066: Tags for the Identification of Languages
Informative reference — RFC 2028: The Organizations Involved in the IETF Standards Process
Informative reference — RFC 3282: Content Language Headers
Informative reference — RFC 4645: Initial Language Subtag Registry
Informative reference — RFC 5645: Update to the Language Subtag Registry

Incoming relationships (54 related RFCs)

Showing 50 of 54 related RFCs.

Normatively referenced by — RFC 6350: vCard Format Specification
Normatively referenced by — RFC 5988: Web Linking
Normatively referenced by — RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Normatively referenced by — RFC 6690: Constrained RESTful Environments (CoRE) Link Format
Normatively referenced by — RFC 8866: SDP: Session Description Protocol
Normatively referenced by — RFC 7095: jCard: The JSON Format for vCard
Normatively referenced by — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol
Normatively referenced by — RFC 5985: HTTP-Enabled Location Delivery (HELD)
Normatively referenced by — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Normatively referenced by — RFC 5914: Trust Anchor Format
Normatively referenced by — RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 6031: Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type
Normatively referenced by — RFC 6030: Portable Symmetric Key Container (PSKC)
Normatively referenced by — RFC 7483: JSON Responses for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Normatively referenced by — RFC 5804: A Protocol for Remotely Managing Sieve Scripts
Normatively referenced by — RFC 6533: Internationalized Delivery Status and Disposition Notifications
Normatively referenced by — RFC 8845: Framework for Telepresence Multi-Streams
Normatively referenced by — RFC 8846: An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
Normatively referenced by — RFC 6545: Real-time Inter-network Defense (RID)
Normatively referenced by — RFC 7643: System for Cross-domain Identity Management: Core Schema
Normatively referenced by — RFC 9244: Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
Normatively referenced by — RFC 9810: Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP)
Normatively referenced by — RFC 5721: POP3 Support for UTF-8
Normatively referenced by — RFC 6231: An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework
Normatively referenced by — RFC 6505: A Mixer Control Package for the Media Control Channel Framework
Normatively referenced by — RFC 6856: Post Office Protocol Version 3 (POP3) Support for UTF-8
Normatively referenced by — RFC 9553: JSContact: A JSON Representation of Contact Data
Normatively referenced by — RFC 6170: Internet X.509 Public Key Infrastructure -- Certificate Image
Normatively referenced by — RFC 6787: Media Resource Control Protocol Version 2 (MRCPv2)
Normatively referenced by — RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters
Normatively referenced by — RFC 8794: Extensible Binary Meta Language
Normatively referenced by — RFC 9264: Linkset: Media Types and a Link Relation Type for Link Sets
Normatively referenced by — RFC 9290: Concise Problem Details for Constrained Application Protocol (CoAP) APIs
Normatively referenced by — RFC 9554: vCard Format Extensions for JSContact
Normatively referenced by — RFC 9555: JSContact: Converting from and to vCard
Normatively referenced by — RFC 9559: Matroska Media Container Format Specification
Normatively referenced by — RFC 5698: Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)
Normatively referenced by — RFC 5854: The Metalink Download Description Format
Normatively referenced by — RFC 7940: Representing Label Generation Rulesets Using XML
Normatively referenced by — RFC 8255: Multiple Language Content Type
Normatively referenced by — RFC 8748: Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
Normatively referenced by — RFC 9167: Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)
Normatively referenced by — RFC 9399: Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates
Normatively referenced by — RFC 9676: LEX: A Uniform Resource Name (URN) Namespace for Sources of Law
Informatively referenced by — RFC 6365: Terminology Used in Internationalization in the IETF
Informatively referenced by — RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
Informatively referenced by — RFC 6501: Conference Information Data Model for Centralized Conferencing (XCON)
Informatively referenced by — RFC 9911: Common YANG Data Types
Informatively referenced by — RFC 8877: Guidelines for Defining Packet Timestamps