Multiple Attachments for Electronic Data Interchange - Internet Integration
RFC 6362, “Multiple Attachments for Electronic Data Interchange - Internet Integration”, is an Informational document published in August 2011 by K. Meadors. The canonical text is published by the RFC Editor.
Abstract
The Electronic Data Interchange - Internet Integration (EDIINT) 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 EDIINT 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 RFC describes how multiple documents, including non-EDI payloads, can be attached and transmitted in a single EDIINT 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. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6362 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6361 PPP Transparent Interconnection of Lots of Links Protocol Control Protocol
- RFC 6363 Forward Error Correction Framework
- RFC 6360 Conclusion of FYI RFC Sub-Series
- RFC 6364 Session Description Protocol Elements for the Forward Error Correction Framework
- RFC 6359 Datatracker Extensions to Include IANA and RFC Editor Processing Information
- RFC 6365 Terminology Used in Internationalization in the IETF
- RFC 6366 Requirements for an Internet Audio Codec
- RFC 6357 Design Considerations for Session Initiation Protocol Overload Control