RFC 1711: Classifications in E-mail Routing
In plain English — editorial summary, not part of the RFC
This paper presents a classification for e-mail routing issues. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1711
- Published
- October 1994
- Authors
- J. Houttuin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1725Post Office Protocol - Version 3Obsoleted
November 1994
- RFC 2635DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*)Current
June 1999
- RFC 1685Writing X.400 O/R NamesCurrent
August 1994
- RFC 1806Communicating Presentation Information in Internet Messages: The Content-Disposition HeaderObsoleted
June 1995
- RFC 1842ASCII Printable Characters-Based Chinese Character Encoding for Internet MessagesCurrent
August 1995
- RFC 1843HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII charactersCurrent
August 1995
- RFC 1563The text/enriched MIME Content-typeObsoleted
January 1994
- RFC 1922Chinese Character Encoding for Internet MessagesCurrent
March 1996
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?