RFC 5198: Unicode Format for Network Interchange
In plain English — editorial summary, not part of the RFC
The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET. This document specifies that format, using UTF-8 with normalization and specific line-ending sequences. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5198
- Published
- March 2008
- Authors
- J. Klensin; M. Padlipsky
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
- RFC 5335Internationalized Email HeadersObsoleted
September 2008
- RFC 4396RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed TextCurrent
February 2006
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 3629UTF-8, a transformation format of ISO 10646Current
November 2003
- RFC 6856Post Office Protocol Version 3 (POP3) Support for UTF-8Current
March 2013
- RFC 9839Unicode Character Repertoire SubsetsCurrent
August 2025
- RFC 6055IAB Thoughts on Encodings for Internationalized Domain NamesCurrent
February 2011
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?