2.1.7 Electronic Data Interchange-Internet Integration (ediint)

NOTE: This charter is a snapshot of the 40th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 27-Oct-97


Rik Drummond <drummond@onramp.net>

Applications Area Director(s):

Keith Moore <moore@cs.utk.edu>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>

Applications Area Advisor:

Harald Alvestrand <Harald.T.Alvestrand@uninett.no>

Mailing Lists:

General Discussion:ietf-ediint@imc.org
To Subscribe: ietf-ediint-request@imc.org
In Body: subscribe
Archive: http://www.imc.org/edi/lists/ietf-ediint

Description of Working Group:

Electronic Data Interchange (EDI) is a set of protocols for conducting highly structured inter-organization exchanges, such as for making purchases or initiating loan requests. The initial RFC1767 defined the method for packaging the EDI X12 and UN/EDIFACT transactions sets in a MIME envelope. However, several additional requirements for obtaining multi- vendor, inter-operable service, over and above how the EDI transactions are packaged, have come to light since the effort concluded. These currently revolve around security issues such as EDI transaction integrity, privacy and non- repudiation in various forms. Additional requirements that mimic many of the heading fields found in X.435 EDI messages (e.g.; Interchange Sender, Interchange Recipient, interchange Control Reference, Communications Agreement ID, and Syntax Identifier) are also needed to support exchanges by point-to-point, FTP and SMTP protocols. Standards in these and other areas are necessary to ensure inter- operability between EDI packages over Internet. Various technologies already exist for these additional features and the primary requirement is to review and select a common set of components for use by the EDI community when it sends EDI over the Internet. In effect, the effort is to provide an EDI over the Internet Informational and Applicability Statement Document.


The group will produce Four documents:

1) An Informational document describing the requirements for interoperable EDI, with sufficient background material to give an explanation for the EDI community of the Internet-related issues.

2) A Applicability Statement describing how current Internet standards can be used to achieve this functionality for MIME and SMTP.

3) A Applicability Statement describing how current Internet standards can be used to achieve this functionality for Process-to-Process (real-time) EDI.

4) Security Issues for Inter-organizational EDI over Internet.

Additional Administrative information:

Editor: Chuck Shih <chuck@orville.premenos.com John DesJardins <jdesjard@nicom.com Marc Blanchet <Marc.Blanchet@viagenie.gc.ca First Readers: Rik Drummond <drummond@onramp.net

Goals and Milestones:



Submit outline for the informational requirements document.



Submit informational requirements document as an Internet-Draft.



Submit both Applicability Statement documents as Internet-Drafts.



Submit requirements document Internet-Draft to IESG for consideration as an Informational RFC.



Submit AS Internet-Draft documents to IESG for consideration as Proposed Standards.

Oct 97


Submit second applicability statement(AS#2)and the Security document as Internet-Drafts.

Apr 98


Submit AS#2 and Security Document to IESG for consideration as Internet-Draft documents for Proposed Standard.


No Request For Comments

Current Meeting Report

Minutes of the Electronic Data Interchange-Internet-Integration (EDIINT) WG

Rik Drummond, WG Chair, and Dale Moberg, Editor for the Secure EDI over HTTP Applicability Statement Draft, made presentations during the meeting.

Rik Drummond welcomed everyone and reviewed the WG status. Approximately 20% of the 30 attendees had read the three WG Drafts. We will submit the first two drafts to the Experimental RFC track as a holding action until the S/MIME issue is resolved one way or the other, since both drafts reference S/MIME. There are three Internet Drafts now available. A fourth, specific to the healthcare industry (HL7), is expected in January. The current drafts are: Requirements, Applicability Statement for Secure EDI over SMTP, and Applicability Statement for Secure EDI over HTTP.

Rik noted that Microsoft Exchange is still causing problems because of the way MIME / MAPI translations take place. It is not known if Exchange version 5.5 fixes the problem.

Dale Moberg presented the status of the Secure EDI over HTTP Draft. It follows closely the SMTP Draft, making only changes necessary to convert the SMTP-based recommendations to the HTTP protocol. Dale noted that one of the problems he found in a test implementation of Secure EDI over HTTP is that the servers timeout if the response takes too long. Einar Stefferud noted that maybe this makes the HTTP protocol inappropriate for this application and we should look for other transport technologies.

Several general comments were made during the meeting:

Keith Moore commented that we could modify the MDN and make it specific to EDI usage. This may help us in the definition of the MDN for the Healthcare HL7 Draft. This would allow a single message that contains the signed receipt and the transaction response data to be returned in response to an HL7 transaction.

Einar Stefferud noted that Content-ID was available as a MIME level header for identifying separate MIME parts for use in more complex receipts.

Finally we discussed the possible need for time-stamping of EDI transactions.

Submitted on January 2, 1998 by Rik Drummond Chair EDIINT WG.


None Received

Attendees List

go to list

Previous PageNext Page