Browse Prior Art Database

Proposed standard for message header munging (RFC0886) Disclosure Number: IPCOM000003935D
Original Publication Date: 1983-Dec-15
Included in the Prior Art Database: 2000-Sep-13
Document File: 13 page(s) / 30K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People


This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 9% of the total text.

Request For Comments: 886

Proposed Standard for Message Header Munging

Thu Dec 15 03:37:52 1983

Marshall T. Rose

Department of Information and Computer Science

University of California, Irvine

Irvine, CA 92717


This memo proposes a standard for the ARPA Internet community. If

this proposal is adopted, hosts on the ARPA Internet that do message

translation would be expected to adopt and implement this standard.

Request For Comments: 886 M. Rose

Proposed Standard for Message Header Munging UCI


This memo describes the rules that are to be used when mail is

transformed from one standard format to another. The scope of this

memo is limited to text messages (computer network mail, or

electronic mail) that traverse the ARPA Internet. This memo is not

presented as a replacement or amendment for the "Standard for the

Format of ARPA Internet Text Messages", RFC822. Rather, this memo

focuses on a particular aspect of mail, and provides a conceptual

and practical basis for implementors of transport agents and user

agents which support message munging.

Although this memo has been specifically prepared for use with the

822 standard, an understanding of the 822 standard is not required

to make use of this memo. The remainder of this section reminds

the reader of some key concepts presented in the 822 standard, and

how they relate to the perspective of this memo.

Messages are viewed as consisting of an envelope and contents. The

envelope is manipulated solely by transport agents, and contains

the information required by the transport agents to deliver the

message to its recipients. Although this memo does not address

itself directly to the envelope, we shall see that some of the

rules discussed later are applicable to the envelope.

The contents of the message consists of a rigorously structured

part, known as the headers, followed by a freely formated part,

called the body. The message body is completely uninteresting to

us. Our emphasis is strictly on the headers of the message. Each

header in the message consists of a field, its value, and a

terminating end-of-line sequence. The 822 standard discusses,

among other things, continuation lines, the syntax that is used to

distinguish between fields and values, and the syntax and semantics

of the values of various fields. For our part, we shall concern

ourselves only with the notion that the headers section consists of

one or more headers, which are divided into one or more fi...