RFC 1685: Writing X.400 O/R Names
In plain English — editorial summary, not part of the RFC
There is a need for human beings who use X.400 systems to be able to write down O/R names in a uniform way. This memo is a discussion of this topic. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind.
Document record
- Document ID
- RFC1685
- Published
- August 1994
- Authors
- H. Alvestrand
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1711Classifications in E-mail RoutingCurrent
October 1994
- RFC 1725Post Office Protocol - Version 3Obsoleted
November 1994
- RFC 1806Communicating Presentation Information in Internet Messages: The Content-Disposition HeaderObsoleted
June 1995
- RFC 1563The text/enriched MIME Content-typeObsoleted
January 1994
- RFC 2183Communicating Presentation Information in Internet Messages: The Content-Disposition Header FieldUpdated
August 1997
- RFC 2184MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsObsoleted
August 1997
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 1802Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingCurrent
June 1995
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?