Search RFCs

RFC Editor

File formats:

Status:

BEST CURRENT PRACTICE

Author:

J. Klensin

Stream:

IETF

Source:

NON WORKING GROUP

Cite this BCP:TXT  | XML

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC

Abstract

There are a number of circumstances in which an escape mechanism isneeded in conjunction with a protocol to encode characters thatcannot be represented or transmitted directly. With ASCII coding,the traditional escape has been either the decimal or hexadecimalnumeric value of the character, written in a variety of differentways. The move to Unicode, where characters occupy two or moreoctets and may be coded in several different forms, has furthercomplicated the question of escapes. This document discusses someoptions now in use and discusses considerations for selecting one foruse in new IETF protocols, and protocols that are now beinginternationalized. This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.