[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3335 on MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet
A new Request for Comments is now available in online RFC libraries.
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
I-D Tag: draft-ietf-ediint-asl-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
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@xxxxxxxxx Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@xxxxxxxxxxxxxxx Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@xxxxxxxxxxxxxxx Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.