CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 19:56:51 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=TUl44Qwc6xD3AFFic3VH6tPzE_3LQ2W3GqIU7efZzek-1759953411-1.0.1.1-8XiImIb0emTyYJF.Gf8lfxLomIjEKuJCjTy..gJ75YwrF_I2crqCMCXuBEoK8uNhz9soOF5ZnvK6vs2szFC0soGaYX8W9u5Sgz49Kv7_GIc; path=/; expires=Wed, 08-Oct-25 20:26:51 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b83430cde6b22e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8266 » RFC Editor
Search RFCs
RFC 8266
Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames, October 2017
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 7700
- Author:
- P. Saint-Andre
- Stream:
- IETF
- Source:
- precis (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8266
Discuss this RFC: Send questions or comments to the mailing list precis@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8266
Abstract
This document describes methods for handling Unicode strings representing memorable, human-friendly names (called "nicknames", "display names", or "petnames") for people, devices, accounts, websites, and other entities. This document obsoletes RFC 7700.
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