Skip to main content

MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3335.
Authors Terry Harding , Rik Drummond , Chuck Shih
Last updated 2015-10-14 (Latest revision 2002-04-05)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3335 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ned Freed
IESG note
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3335

        Title:      MIME-based Secure Peer-to-Peer Business Data
                    Interchange over the Internet
        Author(s):  T. Harding, R. Drummond, C. Shih
        Status:     Standards Track
        Date:       September 2002
        Pages:      29
        Characters: 59687
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ediint-as1-17.txt


This document describes how to exchange structured business data
securely using SMTP transport for Electronic Data Interchange,
(EDI - either the American Standards Committee X12 or UN/EDIFACT,
Electronic Data Interchange for Administration, Commerce and
Transport), XML or other data used for business to business data
interchange.  The data is packaged using standard MIME content-types.
Authentication and privacy are obtained by using Cryptographic Message
Syntax (S/MIME) or OpenPGP security body parts.  Authenticated
acknowledgements make use of multipart/signed replies to the original
SMTP message.

This document is a product of the Electronic Data Interchange-Internet
Integration 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.