CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 08:44:42 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=4Y2MedU1damqsYxsO0PsVAwadM.Yly0N1ULvAVtcDK0-1759999482-1.0.1.1-DqZJxiiqhYznPSxeUi_Gefg_j8RRU4Lhap9GvmtKBzU33wuTqi655hnjXJE1YdbISfTLjMbkpwwAMVgNBlshSAUiKvvHs55uHMAPOJdBdos; path=/; expires=Thu, 09-Oct-25 09:14:42 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc98f85abbaf3d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 1766 » RFC Editor
Search RFCs
RFC 1766
Tags for the Identification of Languages, March 1995
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 3066, RFC 3282
- Author:
- H. Alvestrand
- Stream:
- IETF
- Source:
- mailext (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC1766
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 1766
Abstract
This document describes a language tag for use in cases where it is desired to indicate the language used in an information object. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us