Browse Prior Art Database

MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME (RFC2156)

IP.com Disclosure Number: IPCOM000002713D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2019-Feb-15

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kille: AUTHOR

Related Documents

10.17487/RFC2156: DOI

Abstract

This document relates primarily to the ITU-T 1988 and 1992 X.400 Series Recommendations / ISO IEC 10021 International Standard. This ISO/ITU-T standard is referred to in this document as "X.400", which is a convenient shorthand. [STANDARDS-TRACK]

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

Network Working Group S. Kille Request for Comments: 2156 Isode Ltd. Obsoletes: 987, 1026, 1138, 1148, 1327, 1495 January 1998 Updates: 822 Category: Standards Track

MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Table of Contents

1 - Overview ...................................... 3 1.1 - X.400 ......................................... 3 1.2 - RFC 822 and MIME .............................. 3 1.3 - The need for conversion ....................... 4 1.4 - General approach .............................. 4 1.5 - Gatewaying Model .............................. 5 1.6 - Support of X.400 (1984) ....................... 8 1.7 - X.400 (1992) .................................. 8 1.8 - MIME .......................................... 8 1.9 - Body Parts .................................... 8 1.10 - Local and Global Scenarios .................... 9 1.11 - Compatibility with previous versions .......... 10 1.12 - Aspects not covered ........................... 10 1.13 - Subsetting .................................... 11 1.14 - Specification Language ........................ 11 1.15 - Related Specifications ........................ 11 1.16 - Document Structure ............................ 12 1.17 - Acknowledgements .............................. 12 2 - Service Elements .............................. 13 2.1 - The Notion of Service Across a Gateway ........ 13 2.2 - RFC 822 ....................................... 15 2.3 - X.400 ......................................... 18 3 - Basic Mappings ................................ 27 3.1 - Notation ...................................... 27

Kille Standards Track [Page 1]

RFC 2156 MIXER January 1998

3.2 - ASCII and IA5 ................................. 29 3.3 - Standard Types ................................ 29 3.4 - Encoding ASCII in Printable String ............ 33 3.5 - RFC 1522 ...................................... 34 4 - Addressing and Message IDs .................... 35 4.1 - A textual representation of MTS.ORAddress ..... 36 4.2 - Global Address Mapping ........................ 43 4.3 - EBNF.822-address <-> MTS.ORAddress ............ 46 4.4 - Repeated Mappings ............................. 59 4.5 - Directory Names ............................... 62 4.6 - MTS Mappings .................................. 62 4.7 - IPMS Mappings ................................. 67 5 - Detailed Mappings ............................. 71 5.1 - RFC 822 -> X.400: Detailed Mappings ........... 71 5.2 - Return of Contents ............................ 86 5.3 - X.400 -> RFC 822:...

Processing...
Loading...