Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000002149D
Original Publication Date: 1992-May-01
Included in the Prior Art Database: 2000-Sep-12

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Hardcastle-Kille: AUTHOR

Abstract

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 a revision based on RFCs 987, 1026, 1138, and 1148 [Kille86a,Kille87a] which it obsoletes.

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

Network Working Group S. Hardcastle-Kille

Request for Comments: 1327 University College London

Obsoletes: RFCs 987, 1026, 1138, 1148 May 1992

Updates: RFC 822

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

Status of this Memo

This RFC specifies an IAB standards track protocol for the Internet

community, and requests discussion and suggestions for improvements.

Please refer to the current edition of the "IAB Official Protocol

Standards" for the standardization state and status of this protocol.

Distribution of this memo is unlimited.

Abstract

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 a revision based on RFCs 987, 1026, 1138, and 1148

[Kille86a,Kille87a] which it obsoletes.

This document specifies a mapping between two protocols. This

specification should be used when this mapping is performed on the

DARPA 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 ...................................... 3

1.1 - X.400 ......................................... 3

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

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

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

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

1.6 - X.400 (1984) .................................. 8

1.7 - Compatibility with previous versions .......... 8

1.8 - Aspects not covered ........................... 8

1.9 - Subsetting .................................... 9

1.10 - Document Structure ............................ 9

1.11 - Acknowledgements .............................. 9

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

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

2.2 - RFC 822 ....................................... 11

2.3 - X.400 ......................................... 15

3 - Basic Mappings ................................ 24

3.1 - Notation ...................................... 24

3.2 - ASCII and IA5 ................................. 26

3.3 - Standard Types ................................ 26

3.4 - Encoding A...