Browse Prior Art Database

Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages (RFC1496)

IP.com Disclosure Number: IPCOM000002324D
Original Publication Date: 1993-Aug-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 4 page(s) / 8K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Alvestrand: AUTHOR [+3]

Abstract

Interworking between X.400(88) and MIME is achieved by [4], which complements RFC-1327 [2], which in turn specifies the interworking between X.400(88) and RFC-822 based mail.

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

Network Working Group H. Alvestrand

Request for Comments: 1496 SINTEF DELAB

Updates: 1328 J. Romaguera

NetConsult AG

K. Jordan

Control Data Systems, Inc.

August 1993

Rules for Downgrading Messages from X.400/88 to X.400/84 When

MIME Content-Types are Present in the Messages

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.

Table of Contents

1. Introduction ............................................... 1

2. Basic approach ............................................. 2

3. Conversion rules ........................................... 3

3.1 EBP conversions to Basic .................................. 3

3.2 Encapsulation format ...................................... 3

4. Implications ............................................... 4

5. Security Considerations .................................... 4

6. Authors' Addresses ......................................... 4

7. References ................................................. 5

1. Introduction

Interworking between X.400(88) and MIME is achieved by [4], which

complements RFC-1327 [2], which in turn specifies the interworking

between X.400(88) and RFC-822 based mail.

Interworking between X.400(88) and X.400 (84) is achieved by RFC-1328

[3]. That document does not describe what to do in the case where

body parts arrive at the gateway that cannot be adequately

represented in the X.400(84) system.

This document describes how RFC-1328 must be modified in order to

provide adequate support for the scenarios:

SMTP(MIME) -> X.400(84)

X.400(84) -> SMTP(MIME)

It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT

obsoleted.

NOTE: A desireable side-effect of HARPOON is that a standardized

method for the identification and transmission of multimedia and

binary data (like spreadsheets) between X.400/84 UAs is achieved.

While this method is not compatible with current proprietary

approaches, we believe that it requires less invasive changes to

current UAs than other possible methods.

This memo updates RFC 1328. HARPOON is a pure name, and has no

meaning. Please send comments to the MIME-MHS mailing list

.

2. Basic approach

The approach is to imagine that the connection X.400(84) <->

SMTP(MIME) never happens. This, of course, is an illusion, but can ...