8-bit clean
Template:Short description Template:More citations needed
8-bit clean is an attribute of computer systems, communication channels, and other devices and software, that process 8-bit character encodings without treating any byte as an in-band control code.
HistoryEdit
Until the early 1990s, many programs and data transmission channels were character-oriented and treated some characters, e.g., ETX, as control characters. Others assumed a stream of seven-bit characters, with values between 0 and 127; for example, the ASCII standard used only seven bits per character, avoiding an 8-bit representation in order to save on data transmission costs. On computers and data links using 8-bit bytes, this left the top bit of each byte free for use as a parity, flag bit, or metadata control bit. 7-bit systems and data links are unable to directly handle more complex character codes which are commonplace in non-English-speaking countries with larger alphabets.
Binary files of octets cannot be transmitted through 7-bit data channels directly. To work around this, binary-to-text encodings have been devised which use only 7-bit ASCII characters. Some of these encodings are uuencoding, Ascii85, SREC, BinHex, kermit and MIME's Base64. EBCDIC-based systems cannot handle all characters used in UUencoded data.Template:Clarify However, the base64 encoding does not have this problem.
SMTP and NNTP 8-bit cleannessEdit
Historically, various media were used to transfer messages, some of them only supporting 7-bit data, so an 8-bit message had high chances to be garbled during transmission in the 20th century. But some implementations really did not care about formal discouraging of 8-bit data and allowed high bit set bytes to pass through. Such implementations are said to be 8-bit clean. In general, a communications protocol is said to be 8-bit clean if it correctly passes through the high bit of each byte in the communication process.
Many early communications protocol standards, such as Template:IETF RFC (for SMTP), Template:IETF RFC (for NNTP) and Template:IETF RFC, were designed to work over such "7-bit" communication links. They specifically require the use of ASCII character set "transmitted as an 8-bit byte with the high-order bit cleared to zero" and some of these<ref>Template:IETF RFC: Appendix A, Template:IETF RFC: 4.5.2., Template:IETF RFC: Appendix B, Template:IETF RFC: 4.</ref> explicitly restrict all data to 7-bit characters.
For the first few decades of email networks (1971 to the early 1990s), most email messages were plain text in the 7-bit US-ASCII character set.<ref> John Beck. "Email Explained". 2011.</ref>
The Template:IETF RFC definition of SMTP, like its predecessor Template:IETF RFC, limits Internet Mail to lines (1000 characters or less) of 7-bit US-ASCII characters.<ref>Template:Cite RFC </ref><ref>Template:Cite RFC </ref><ref> Dan Sugalski. "E-mail with Attachments". "The Perl Journal". Summer 1999. "When mail was standardized way back in 1982 with RFC822, ... The only limits placed on the body were the character set (7-bit ASCII) and the maximum line length (1000 characters)."</ref><ref name="RFC2045" />
Later, the format of email messages was redefined in order to support messages that are not entirely US-ASCII text (text messages in character sets other than US-ASCII, and non-text messages, such as audio and images).<ref name="RFC2045">Template:Cite RFC </ref> The header field Content-Transfer-Encoding=binaryTemplate:Efn requires an 8-bit clean transport.
Template:IETF RFC<ref>Template:Cite IETF </ref> specifies that "NNTP operates over any reliable bi-directional 8-bit-wide data stream channel", and changes the character set for commands to UTF-8. However, Template:IETF RFC<ref>Template:Cite IETF </ref> still limits the character set to ASCII, including Template:IETF RFC<ref>Template:Cite RFC </ref> and Template:IETF RFC<ref>Template:Cite IETF </ref> MIME encoding of non-ASCII data.
The Internet community generally adds features by extension, allowing communication in both directions between upgraded machines and not-yet-upgraded machines, rather than declaring formerly standards-compliant legacy software to be "broken" and insisting that all software worldwide be upgraded to the latest standard. The recommended way to take advantage of 8-bit-clean links between machines is to use the ESMTP (Template:IETF RFC) 8BITMIME extension<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref><ref>{{#invoke:citation/CS1|citation |CitationClass=web }} </ref> for message bodies and the SMTP SMTPUTF8<ref>Template:Cite IETF </ref> extension for message headers. Despite this, some mail transfer agents, notably Exim and qmail, relay mail to servers that do not advertise 8BITMIME without performing the conversion to 7-bit MIME (typically quoted-printable, "Q-P conversion") required by Template:IETF RFC. This "just-send-8" attitude does not, in fact, cause problems in practice because virtually all modern email servers are 8-bit clean.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>