Technical Summary
The EDI-INT AS1, AS2 and AS3 messages were designed specifically for
the transport of EDI documents. Since multiple interchanges could be
placed within a single EDI document, there was not a need for sending
multiple EDI documents in a single message. As adoption of EDI-INT
grew, other uses developed aside from single EDI document transport.
Some transactions required multiple attachments to be interpreted
together and stored in a single message. This informational draft
describes how multiple documents, including non-EDI payloads, can be
attached and transmitted in a single EDI-INT transport message. The
attachments are stored within the MIME Multipart/Related structure.
A minimal list of content-types to be supported as attachments is
provided.
Working Group Summary
This is not a WG document. It was originally submitted as an Independent Submission
to RFC Editor, but after a discussion between the author, sponsoring AD and ISE it was
decided that it is suitable for the IETF stream.
Document Quality
There are at least 8 different implementations of this extension.
Personnel
Pete Resnick is the Responsible Area Director.
RFC Editor Note
In Section 2.5, please add to the end of the 1st paragraph:
Existing text:
Documents of the following MIME media types MAY be found in a
multipart/related envelope and MUST be accepted by the user agent.
However, any media type can be used depending upon industry need, and
other media types MAY be accepted depending upon trading partner
agreement.
ADD:
Please see [MIMEREG] for the definitions of the Media Types listed below.
In Section 2.5 delete:
DELETE:
application/vnd.ms-excel, application/x-msexcel
DELETE:
image/bmp
In Section 3, in the example:
OLD:
protocol="application/pkcs7-signature"; micalg=sha1;
NEW:
protocol="application/pkcs7-signature"; micalg=sha-1;
Add the following reference to the list of Normative References:
[MIMEREG] http://www.iana.org/assignments/media-types/index.html