metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 1342: Representation of Non-ASCII Text in Internet Message Headers

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1522.

Current document in this lineage: RFC 2045 — Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies; RFC 2046 — Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types; RFC 2047 — MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text; RFC 2049 — Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples; RFC 4289 — Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures; RFC 6838 — Media Type Specifications and Registration Procedures

In plain English — editorial summary, not part of the RFC

This memo describes an extension to the message format defined in [1] (known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC 822 message headers. [STANDARDS-TRACK]

Document record

Document ID
RFC1342
Published
June 1992
Authors
K. Moore
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
7
Also known as
—
Obsoleted by:
RFC 1522

Topics

Standards lineage

This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.

  1. RFC 1341 (1992)
  2. RFC 1342 (1992)
  3. RFC 1521 (1993)
  4. RFC 1522 (1993)
  5. RFC 1590 (1994)
  6. RFC 2045 (1996)
  7. RFC 2046 (1996)
  8. RFC 2047 (1996)
  9. RFC 2048 (1996)
  10. RFC 2049 (1996)
  11. RFC 4288 (2005)
  12. RFC 4289 (2005)
  13. RFC 6838 (2013) ✓

Read the full history of Media Type Specifications and Registration Procedures →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/1342-representation-of-non-ascii-text-in-internet-message-headers