RFC 822

RFC 822
AlexanderVanLoon · CC BY-SA 3.0 · source
Name	RFC 822
Type	Technical Standard
Status	Historic
Author	David H. Crocker
Organization	Internet Engineering Task Force
Published	1982-08

RFC 822

RFC 822 is a 1982 Internet standard that defined the syntax for text messages that are sent using electronic mail on the early Internet. It specified the header fields, message structure, and addressing conventions that shaped interoperable mail systems across implementations such as Sendmail, SMTP servers, Usenet, and early ARPANET gateways. The document influenced later standards and was a cornerstone of messaging protocols in the development of the Internet and related services.

Background and Purpose

RFC 822 was produced during a period of rapid development in networking led by organizations and projects such as the Internet Engineering Task Force, Bolt Beranek and Newman, USENIX, and the Defense Advanced Research Projects Agency. It succeeded earlier specifications from the Request for Comments series and aimed to provide a uniform definition to promote interoperability among implementations like DECnet-based mailers, TOPS-20 systems, and VMS mail utilities. The purpose was to create a canonical representation for Internet mail that would be independent of particular mail transport agents developed by vendors such as Bell Labs, IBM, and Microsoft Corporation.

Syntax and Message Format

RFC 822 defined a formal grammar using augmented Backus–Naur form to describe lexical elements such as atoms, tokens, and quoted-strings, building on techniques used in specifications like ISO 8601 and earlier RFCs. The message format consists of a header section and a body separated by a single blank line; headers use the "name: value" construct common to standards from DEC, MIT, and Stanford University. The syntax addressed character encoding and folding rules influenced by protocols such as TELNET and by modeling approaches seen in Unix text conventions. RFC 822's formalism enabled parsers implemented in projects including GNU, Berkeley Software Distribution, and vendor mail libraries to handle complex constructs like comments and obsolete syntactic forms.

Header Fields

The specification enumerated standard header field names such as From, To, Subject, Date, Received, and Message-ID, drawing on conventions established by systems like Mail Transfer Agent implementations and services at institutions such as University of California, Berkeley and Massachusetts Institute of Technology. RFC 822 defined semantics for fields that influenced subsequent header extensions adopted by MIME authors and by standards bodies including the Internet Assigned Numbers Authority and the European Computer-Industry Research Centre. Implementations from vendors including Sun Microsystems, Hewlett-Packard, and Digital Equipment Corporation relied on these headers for routing, threading, and delivery reporting in environments ranging from campus mail systems to commercial gateways.

Addressing and Aliasing

Address syntax in RFC 822 detailed local-part and domain semantics, supporting forms used by domains managed by organizations such as Merit Network, World Wide Web Consortium, and early Network Solutions registrars. The document formalized addressing that interoperated with aliasing mechanisms in systems like Procmail, Listserv, and site-specific forwarding managed by institutions including Carnegie Mellon University and Stanford Research Institute. This addressing model underpinned directory and routing efforts tied to services such as X.400 gateways, LU6.2 connectors, and commercial mail exchangers operated by companies like CompuServe and MCI Communications Corporation.

Extensions and Obsolescence

While RFC 822 provided a foundational model, later work from entities such as the Internet Engineering Task Force, Multipurpose Internet Mail Extensions authors, and standards groups at IETF Working Groups produced extensions and replacements including specifications that standardized MIME, internationalization, and updated syntactic rules. RFC 822 was eventually obsoleted by successor documents influenced by efforts from researchers and organizations like Jon Postel’s collaborators, Paul Mockapetris, and the Internet Architecture Board, reflecting changes in addressing, international character sets, and security considerations introduced by communities including CERT and Internet Society. Vendors including Microsoft Corporation and Google implemented backward-compatible support while adopting newer standards for richer content types.

Implementation and Impact

RFC 822's influence is visible in a wide array of implementations and services such as Sendmail, Postfix, Exim, Microsoft Exchange, and early Eudora clients, as well as in academic deployments at institutions like MIT and UC Berkeley. The specification shaped protocol development across the Internet Research Task Force and informed archival and forensic practices used by organizations such as National Institute of Standards and Technology and Library of Congress. RFC 822's legacy persists in modern message headers, addressing semantics, and the interoperability principles that continue to guide standards bodies including the IETF and the Internet Society.

Category:Internet standards