Browse Prior Art Database

Mapping between X.400 and RFC 822 (RFC0987)

IP.com Disclosure Number: IPCOM000004985D
Original Publication Date: 1986-Jun-01
Included in the Prior Art Database: 2001-Jul-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S.E. Kille: AUTHOR

Abstract

Status of This Memo

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 3% of the total text.

UCL Technical Report 120 Mailgroup Note 19

Network Working Group S.E. Kille Request for Comments: 987 University College London

June 1986

Mapping between X.400 and RFC 822

Status of This Memo

This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 (1984) series of protocols [CCITT84a], and systems using the RFC 822 mail protocol [Crocker82a], or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings. The mappings should not require any changes to end systems.

This specification should be used when this mapping is performed on the ARPA-Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected.

Kille [Page 1]

RFC 987 June 1986 Mapping between X.400 and RFC 822

Chapter 1 Overview

1.1. X.400

The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. As well as the base standard (X.400), work is underway on various functional standards of profiles which specify how X.400 will be used in various communities. Many of the major functional standards (e.g. from CEPT, CEN/CENELEC, and NBS) are likely to be similar. Some of the decisions in this document are in the light of this work. No reference is given, as these documents are not currently stable.

1.2. RFC 822

RFC 822 evolved as a messaging standard on the DARPA (the US Defense Advanced Research Projects Agency) Internet. It is currently used on the ARPA-Internet in conjunction with two other standards: RFC 821, also known as Simple Mail Transfer Protocol (SMTP) [Postel82a], and RFC 920 which is a specification for a domain name system and a distributed name service [Postel84a]. RFC 822, or protocols derived from RFC 822 are used in a number of other networks. In particular:

UUCP Networks

UUCP is the UNIX to UNIX CoPy protocol <0>, which is usually used over dialup telephone networks to provide a simple message transfer mechanism. There are some extensions to RFC 822, particularly in the addressing. They are likely to use domains which conform to RFC 920, but not the corresponding domain nameservers [Horton86a].

CSNET

Some portions of CSNET will follow the ARPA-Internet protocols. The dialup portion of CSNET uses the Phonenet protocols as a replacement for RFC 821. This portion is likely to use domains which conform to RFC 920, but not the corresponding domain nameservers.

BITNET

Some parts of BITNET use RFC 822 related protocols, with EBCDIC encoding.

Kille [Page 2]

RFC 987 June 1986 Mapping between X.400 and RFC 822

JNT Mail Networks

A n...