A new Request for Comments is now available in online RFC libraries.


        RFC 1767:

        Title:      MIME Encapsulation of EDI Objects
        Author:     D. Crocker
        Date:       March 1995
        Mailbox:    dcrocker@mordor.stanford.edu
        Pages:      7
        Characters: 15,293
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1767.txt


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.  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.  This RFC is the product
of the Electronic Data Interchange Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute