RFC1615, RTR9 on Migrating from X.400(84) to X.400(88)

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 19 May 1994 21:58 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12948; 19 May 94 17:58 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa20404; 19 May 94 17:58 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12865; 19 May 94 17:58 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12713; 19 May 94 17:51 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa20271; 19 May 94 17:51 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-16) id <AA17525>; Thu, 19 May 1994 14:51:25 -0700
Message-Id: <199405192151.AA17525@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1615, RTR9 on Migrating from X.400(84) to X.400(88)
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 19 May 1994 14:51:40 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1615:
	RTR 9:

        Title:      Migrating from X.400(84) to X.400(88)
        Author:     J. Houttuin & J. Craigie
        Mailbox:    houttuin@rare.nl, J.Craigie@jnt.ac.uk
        Pages:      17
        Characters: 39,693
        Updates/Obsoletes:  none


This document compares X.400(88) to X.400(84) and describes what
problems can be anticipated in the migration, especially considering
the migration from the existing X.400(84) infrastructure created by
the COSINE MHS project to an X.400(88) infrastructure. It not only
describes the technical complications, but also the effect the
transition will have on the end users, especially concerning
interworking between end users of the 84 and the 88 services.

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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1615.txt"><ftp://ds.internic.net/rfc/rfc1615.txt>