A new Request for Comments is now available in online RFC libraries.


        RFC 1649:

        Title:      Operational Requirements for X.400 Management
                    Domains in the GO-MHS Community
        Author:     R. Hagens & A. Hansen
        Mailbox:    hagens@ans.net, Alf.Hansen@uninett.no
        Pages:      14
        Characters: 28,138
        Updates/Obsoletes:  none


There are several large, operational X.400 services currently
deployed. Many of the organizations in these services are connected to
the Internet.  A number of other Internet-connected organizations are
beginning to operate internal X.400 services (for example, U.S.
government organizations following U.S. GOSIP).  The motivation for
this document is to foster a Global Open Message Handling System
(GO-MHS) Community that has full interoperability with the existing
E-mail service based on RFC-822 (STD-11).  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).  Examples of such regional services are the COSINE MHS
Service in Europe and the XNREN service in the U.S.  This RFC is the
product of the X.400 Operations Working Group of the IETF.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute