Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000009752D
Original Publication Date: 2002-Sep-01
Included in the Prior Art Database: 2002-Sep-17
Document File: 30 page(s) / 60K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Harding: AUTHOR [+3]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � T. Harding

Request for Comments: 3335� � � � � � � � � � � � � � � � � � � � � � � � � � � � � Cyclone Commerce

Category: Standards Track� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � R. Drummond

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Drummond Group

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � C. Shih

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Gartner Group

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � September 2002

� � � � � � � � � � � � � � � � � � � � MIME-based Secure Peer-to-Peer

� � � � � � � � � � � � � Business Data Interchange over the Internet

Status of this Memo

� � 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.

Copyright Notice

� � Copyright (C) The Internet Society (2002).� All Rights Reserved.

Abstract

� � 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.

Harding, et. al.� � � � � � � � � � � Standards Track� � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3335� � � � � � � � � � � � � � � � MIME-based Secure EDI� � � � � � � � � � � September 2002

Table of Contents

� � 1.0� � Introduction .................................................3

� � 2.0� � Overview .....................................................4

� � 2.1� � Purpose of a Security Guideline for MIME EDI .................4

� � 2.2� � Definitions ..................................................4

� � 2.2.1 Terms ........................................................4

� � 2.2.2 The Secure Transmission Loop .................................5

� � 2.2.3 Definition of Receipts .......................................5

� � 2.3� � Assumptions ..................................................6

� � 2.3.1 EDI Process Assumptions ......................................6

� �...