MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)

Drummond, R. J.

doi:10.17487/rfc4130

Cited by 21 publications

(10 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…MA-Feature-Name = "multiple-attachments" For a compressed but unsigned message, regardless of encryption, the MIC is calculated over the uncompressed multipart/related body including any applied Content-Transfer-Encoding. The body MUST be canonicalized according to the procedure described in the underlying transport protocol (e.g., HTTP AS2 [RFC4130]) before the MIC is calculated.…”

Section: Ediint-features Headermentioning

confidence: 99%

“…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%

See 1 more Smart Citation

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

Section: Ediint-features Headermentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

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

Meadors¹

2011

View full text Add to dashboard Cite

show abstract

“…To make the third aspect an even harder challenge, enterprises may also apply more than one communication technology for realizing B2Bi due to internal or external constraints. This may be the case because a single communication technology cannot be forced upon all integration partners or because of legal regulations, e.g., customs authorities may require enterprises to send customs declarations using AS2 [2]. Standardization organizations take this problem into account, too.…”

Section: Introductionmentioning

confidence: 99%

“…Standardization organizations take this problem into account, too. RosettaNet 1 , for example, as a leading international B2Bi consortium has released the "Multi Messaging Services" profiles 2 for describing how to exchange RosettaNet defined standard business documents via Web Services, AS2 and ebXML Messaging [3] in 2008. This situation amounts to the first research problem that is investigated in this paper: Problem 1: How can new complex business collaborations be built using more than one type of communication technology?…”

Section: Introductionmentioning

confidence: 99%

Using Variable Communication Technologies for Realizing Business Collaborations

Schönberger

Wirtz

2009

2009 World Conference on Services - II

View full text Add to dashboard Cite

In today's business world, enterprises are not only using Web Services for implementing B2Bi. Instead, AS2 for realizing Internet based EDI, ebXML Messaging and even SMTP and FTP are used for exchanging business documents. Harmonizing B2Bi communication technology in a way that solely uses Web Services is barely an option for large enterprises as this would result in losing investments in existing IT systems. Moreover, forcing a specific communication technology upon all business partners is neither intended nor realistic in practice. At the same time, existing business document exchanges frequently only implement B2Bi scenarios partly. This paper focuses on a method for composing existing and new business document exchanges without replacing communication technology already in use. First, ebXML BPSS is proposed for describing the choreography of business document exchanges in a technology agnostic way. Second, ebXML CPPA is used to define messaging characteristics at the level of ebBP BusinessTransactions. Third, an integration architecture for performing ebXML BPSS choreographies using BPEL processes that execute each integration partner's message exchanges is proposed. These BPEL processes assume Web service wrappers for reusing the functionality of messaging systems that are responsible for performing the actual business document exchanges and for providing sufficient status information to the caller. Different messaging systems then can be used for incorporating variable communication technologies in business collaborations.

show abstract

“…The original intent was for transport of a single EDI or XML document. However, as AS1 [RFC3335], AS2 [RFC4130], and AS3 [RFC4823] matured, other features and application logic were implemented upon EDIINT standards. Since these features go beyond (but do not violate) the basic premise of EDIINT, a means is needed to communicate to trading partners features that are supported by the originating user agent.…”

mentioning

confidence: 99%

Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field

Meadors¹

2010

View full text Add to dashboard Cite

With the maturity of the Electronic Data Interchange -Internet Integration (EDIINT) standards of AS1, AS2, and AS3, applications and additional features are being built upon the basic secure transport functionality. These features are not necessarily supported by all EDIINT applications and could cause potential problems with implementations. The EDIINT-Features header field provides a means to resolve these problems and support new functionality.

show abstract

MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)

Cited by 21 publications

References 19 publications

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

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

Using Variable Communication Technologies for Realizing Business Collaborations

Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field

Contact Info

Product

Resources

About