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

Harding, T. Swann; Drummond, R. J.; Shih, Connie

doi:10.17487/rfc3335

Cited by 9 publications

(6 citation statements)

References 11 publications

(11 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[FTP Server] FTP and retaining as much as possible from the [5] functionality, the ftpurl must be present.…”

Section: Message Disposition Notifications (Mdn)mentioning

confidence: 99%

“…Previous work on Internet EDI focused on specifying MIME content types for EDI data [2] and extending this work to support secure EC/EDI transport over SMTP [5]. This document expands on RFC 1767 to specify a comprehensive set of data security features, specifically, data privacy, data integrity, authenticity, non-repudiation of origin, and non-repudiation of receipt over FTP.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

Harding¹,

Scott²

2007

Self Cite

View full text Add to dashboard Cite

“…[FTP Server] FTP and retaining as much as possible from the [5] functionality, the ftpurl must be present.…”

Section: Message Disposition Notifications (Mdn)mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

Harding¹,

Scott²

2007

Self Cite

View full text Add to dashboard Cite

“…The primary work of the EDIINT working group (WG) was to develop a secure means of transporting EDI documents over the Internet. This was described in the three WG-developed standards for secure transport over SMTP AS1 [RFC3335], HTTP AS2 [RFC4130], and FTP AS3 [RFC4823]. For most uses of EDI, all relevant information to complete a single business transaction could be stored in a single document.…”

Section: Introductionmentioning

confidence: 99%

Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)

Meadors¹

2011

View full text Add to dashboard Cite

The Electronic Data Interchange -Internet Integration (EDIINT) AS1, AS2, and AS3 messages were designed specifically for the transport of EDI documents. Since multiple interchanges could be placed within a single EDI document, there was not a need for sending multiple EDI documents in a single message. As adoption of EDIINT grew, other uses developed aside from single EDI document transport. Some transactions required multiple attachments to be interpreted together and stored in a single message. This Informational RFC describes how multiple documents, including non-EDI payloads, can be attached and transmitted in a single EDIINT transport message. The attachments are stored within the MIME multipart/related structure. A minimal list of content-types to be supported as attachments is provided.

show abstract

“…Historically, electronic messages produced by systems following the guidelines as outlined in the IETF EDIINT Working Group specifications AS1 [AS1], AS2 [AS2], and AS3 [AS3] did not have a way to provide a standardized transport neutral mechanism for compressing large payloads. However, with the development of RFC 3274, "Compressed Data Content Type for Cryptographic Message Syntax (CMS)", we now have a transport-neutral mechanism for compressing large payloads.…”

Section: Introductionmentioning

confidence: 99%

Compressed Data within an Internet Electronic Data Interchange (EDI) Message

Harding¹

2010

View full text Add to dashboard Cite

This document explains the rules and procedures for utilizing compression (RFC 3274) within an Internet EDI (Electronic Data Interchange) 'AS' message, as defined in RFCs 3335, 4130, and 4823. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5402. IESG Note The content of this RFC was at one time considered by the IETF, and therefore it may resemble a current IETF work in progress or a published IETF work. This RFC is not a candidate for any level of Internet Standard. Readers of this RFC should exercise caution in evaluating its value for implementation and deployment.

show abstract

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

Cited by 9 publications

References 11 publications

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)

Compressed Data within an Internet Electronic Data Interchange (EDI) Message

Contact Info

Product

Resources

About