[rfc-dist] RFC 5198 on Unicode Format for Network Interchange

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Mar 27 14:49:56 PDT 2008

A new Request for Comments is now available in online RFC libraries.

        RFC 5198

        Title:      Unicode Format for Network Interchange 
        Author:     J. Klensin, M. Padlipsky
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    john-ietf at jck.com, 
                    the.map at alum.mit.edu
        Pages:      19
        Characters: 45708
        Obsoletes:  RFC0698
        Updates:    RFC0854

        I-D Tag:    draft-klensin-net-utf8-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5198.txt

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]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list