Novannet, LLC LogoThe 10-10-EDISM of B2B Transport

MIME ENCODED EDI

EDI data, whether X12, UN/EDIFACT or HL7, is encoded as a MIME object when it is sent over the Internet. EDIINT AS1, which uses the SMTP e-mail mechanism, includes the MIME object as an e-mail attachment. EDIINT AS2 directly sends the MIME object to the recipient with an HTTP POST.

MIME, or Multipurpose Internet Mail Extensions, is simply an IETF standard for packaging non-textual or binary messages, such as audio files, PDFs, Microsoft Word documents... or even EDI. MIME is described by IETF RFCs 2045, 2046, 2047, 2048 and 2049. The MIME payloads used to package EDI for e-mail or HTTP are described by RFC 3335 and MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet Using HTTP AS2, respectively.

Likewise, ebXML Messaging services uses identical wrapping techniques for EDI payloads as used by EDIINT. The EDI business message is encapsulated as a MIME object, which is included as a payload attachment in the ebXML message package. The general structure of an ebXML message is displayed in Figure 2: Message Anatomy within The ebXML Messaging Service. The ebXML message package can be sent directly using HTTP, or - less usually - as an e-mail attachment itself.

The Novannet 10-10-EDISM system always signs and encrypts EDI payloads by adding Cryptographic signature and encryption services to MIME messages, using the S/MIME standards described in RFCs 2630 and 2633. Optional compression is applied to the EDI contents before signing and encryption.

Valid XHTML 1.0!