RFC 1649: Operational Requirements for X.400 Management Domains in the GO-MHS Community
In plain English — editorial summary, not part of the RFC
The goal of this document is to unite regionally operated X.400 services on the various continents into one GO-MHS Community (as seen from an end-user's point of view). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1649
- Published
- July 1994
- Authors
- R. Hagens; A. Hansen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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
- RFC 1836Representing the O/R Address hierarchy in the X.500 Directory Information TreeObsoleted
August 1995
- RFC 1837Representing Tables and Subtrees in the X.500 DirectoryObsoleted
August 1995
- RFC 1838Use of the X.500 Directory to support mapping between X.400 and RFC 822 AddressesObsoleted
August 1995
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 2178OSPF Version 2Obsoleted
July 1997
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?