Browse Prior Art Database

MIME Encapsulation of EDI Objects (RFC1767)

IP.com Disclosure Number: IPCOM000004018D
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 6 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Crocker: AUTHOR

Abstract

Electronic Data Interchange (EDI) provides a means of conducting structured transactions between trading partners. The delivery mechanism for these types of transactions in a paper world has been the postal system, so it is to be expected that electronic mail would serve as a natural delivery mechanism for electronic transactions. This specification permits formatted electronic business interchanges to be encapsulated within MIME messages [Bore92]. For the specification effort, the basic building block from EDI is an interchange.

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

Network Working Group D. Crocker

Request for Comments: 1767 Brandenburg Consulting

Category: Standards Track March 1995

MIME Encapsulation of EDI Objects

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.

Table of Contents

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

2. Application/EDIFACT specification...................... 2

3. Application/EDI-X12 specification...................... 3

4. Application/EDI-Consent specification.................. 4

5. Sample edi usage in MIME-based email................... 5

6. References............................................. 5

7. Security Considerations................................ 6

8. Acknowledgments........................................ 6

9. Author's Address....................................... 6

10. Appendix - MIME for EDI users......................... 7

1. Introduction

Electronic Data Interchange (EDI) provides a means of conducting

structured transactions between trading partners. The delivery

mechanism for these types of transactions in a paper world has been

the postal system, so it is to be expected that electronic mail would

serve as a natural delivery mechanism for electronic transactions.

This specification permits formatted electronic business interchanges

to be encapsulated within MIME messages [Bore92]. For the

specification effort, the basic building block from EDI is an

interchange.

This specification pertains only to the encapsulation of EDI objects

within the MIME environment. It intends no changes in those objects

from the primary specifications that define the syntax and semantics

of them. EDI transactions take place through a variety of carriage

and exchange mechanisms. This specification adds to that repertoire,

by permitting convenient carriage through Internet email.

Since there are many different EDI specifications, the current

document defines three distinct categories as three different MIME

content-types. One is Application/EDI-X12, indicating that the

contents conform to the range of specifications developed through the

X12 standards organization [X125, X126, X12V]. Another is

Application/EDIFACT, indicating that the contents conform to the

range of specifications developed by the United Nations Working Party

4 Group of Experts 1 EDIFACT boards [FACT, FACV]. The last category

covers all other specifications; it is Application/EDI-consent.

2. APPLICATION/EDIFACT SPECIFICATION

The Application/EDIFACT MIME body-part contains data as specified for