Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Mapping between X.400 and RFC-822/MIME Message Bodies (RFC2157)

IP.com Disclosure Number: IPCOM000002714D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 39 page(s) / 85K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Alvestrand: AUTHOR

Abstract

This document is a companion to [MIXER], which defines the principles and translation of headers for interworking between MIME-based RFC- 822 mail and X.400 mail.

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

Network Working Group H. Alvestrand

Request for Comments: 2157 UNINETT

Category: Standards Track January 1998

Mapping between X.400 and RFC-822/MIME Message Bodies

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 Introduction ........................................... 2

1.1 Glossary ............................................. 3

2 Basic rules for body part conversion ................... 4

2.1 Generating the IPM Body from MIME .................... 5

2.2 Generating the MIME Body from the IPMS.Body .......... 6

2.3 Mapping the EMA FTBP parameters ...................... 7

2.3.1 Mapping GraphicStrings ............................. 7

2.3.2 Mapping specific parameters ........................ 7

2.3.3 Summary of FTBP elements generated ................. 10

2.4 Information that is lost when mapping ................ 11

3 Encapsulation of body parts ............................ 11

3.1 Encapsulation of MIME in X.400 ....................... 12

3.1.1 FTBP encapsulating body part ....................... 12

3.1.2 BP15 encapsulating body part ....................... 13

3.1.3 Encapsulation using IA5 (HARPOON) .................. 15

3.1.4 Content passing using BP14 ......................... 16

3.2 Encapsulating X.400 Body Parts in MIME ............... 16

3.3 Encapsulating FTBP body parts in MIME ................ 17

4 User control over the gateway choice ................... 18

4.1 Conversion from MIME to X.400 ........................ 18

4.2 Conversion from X.400 to MIME ........................ 20

5 The equivalence registry ............................... 21

5.1 What information one must give about a mapping

..................................................... 21

5.2 Equivalence summary for known X.400 and MIME

Types ................................................ 22

5.3 MIME to X.400 Table .................................. 23

5.4 X.400 to MIME Table .................................. 23

5.5 Use of OBJECT IDENTIFIERs and ASN.1 MACROS ........... 24

6 Defined Equivalences ................................... 26

6.1 IA5Text - text/plain ................................. 26

6.2 GeneralText - text/plain (ISO-8859) .................. 27

6.3 BilaterallyDefined - application/octet-stream

...................................................... 29

6.4 FTBP EMA Unknown Attachment -

app...