RFC 1154: Encoding header field for internet messages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1505.
Current version: RFC 1505 — Encoding Header Field for Internet Messages
In plain English — editorial summary, not part of the RFC
This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement).
Document record
- Document ID
- RFC1154
- Published
- April 1990
- Authors
- D. Robinson; R. Ullmann
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 1505
Referenced by
One later RFC formally updates or obsoletes part of this document.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?