Browse Prior Art Database

Mapping between X.400(1988) / ISO 10021 and RFC 822 (RFC1148)

IP.com Disclosure Number: IPCOM000001959D
Original Publication Date: 1990-Mar-01
Included in the Prior Art Database: 2000-Sep-12

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S.E. Kille: AUTHOR

Abstract

Service [CCITT/ISO88c]. The MT Abstract Service provides the following three basic services:

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

Network Working Group S. Kille

Request for Comments 1148 University College London

Updates: RFCs 822, 987, 1026, 1138 March 1990

Mapping between X.400(1988) / ISO 10021 and RFC 822

Status of this Memo

This RFC suggests an electronic mail protocol mapping for the

Internet community and UK Academic Community, and requests discussion

and suggestions for improvements. This memo does not specify an

Internet standard. This edition includes material lost in editing.

Distribution of this memo is unlimited.

This document describes a set of mappings which will enable

interworking between systems operating the CCITT X.400 (1988)

Recommendations on Message Handling Systems / ISO IEC 10021 Message

Oriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], 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 document is based on RFC 987 and RFC 1026 [Kille86a, Kille87a],

which define a similar mapping for X.400 (1984). This document does

not obsolete the earlier ones, as its domain of application is

different.

Specification

This document specifies a mapping between two protocols. This

specification should be used when this mapping is performed on the

Internet or in the UK Academic Community. This specification may be

modified in the light of implementation experience, but no

substantial changes are expected.

Table of Contents

1. Overview ............................................... 2

1.1 X.400 ................................................. 2

1.2 RFC 822 ............................................... 3

1.3 The need for conversion ............................... 4

1.4 General approach ...................................... 4

1.5 Gatewaying Model ...................................... 5

1.6 RFC 987 ............................................... 7

1.7 Aspects not covered ................................... 8

1.8 Subsetting ............................................ 9

1.9 Document Structure .................................... 9

1.10 Acknowledgements ..................................... 10

2. Service Elements ....................................... 10

2.1 The Notion of Service Across a Gateway ................ 10

2.2 RFC 822 ............................................