idnits 2.17.1 draft-ietf-ediint-as1-17.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3335 5 Title: MIME-based Secure Peer-to-Peer Business Data 6 Interchange over the Internet 7 Author(s): T. Harding, R. Drummond, C. Shih 8 Status: Standards Track 9 Date: September 2002 10 Mailbox: tharding@cyclonecommerce.com, 11 chuck.shih@gartner.com, rik@drummondgroup.com 12 Pages: 29 13 Characters: 59687 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-ediint-as1-17.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3335.txt 20 This document describes how to exchange structured business data 21 securely using SMTP transport for Electronic Data Interchange, 22 (EDI - either the American Standards Committee X12 or UN/EDIFACT, 23 Electronic Data Interchange for Administration, Commerce and 24 Transport), XML or other data used for business to business data 25 interchange. The data is packaged using standard MIME content-types. 26 Authentication and privacy are obtained by using Cryptographic Message 27 Syntax (S/MIME) or OpenPGP security body parts. Authenticated 28 acknowledgements make use of multipart/signed replies to the original 29 SMTP message. 31 This document is a product of the Electronic Data Interchange-Internet 32 Integration Working Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for the 37 Internet community, and requests discussion and suggestions for 38 improvements. Please refer to the current edition of the "Internet 39 Official Protocol Standards" (STD 1) for the standardization state and 40 status of this protocol. Distribution of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.