Electronic Data Interchange-Internet Integration (ediint) Charter

NOTE: This charter is accurate as of the 37th IETF Meeting in San Jose. It may now be out-of-date. (Consider this a "snapshot" of the working group from that meeting.) Up-to-date charters for all active working groups can be found elsewhere in this Web server.

Chair(s)

Rik Drummond <drummond@onramp.net>

Applications Area Director(s):

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

Area Advisor

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

Mailing List Information

General Discussion:ietf-ediint@imc.org
To Subscribe: ietf-ediint-request@imc.org
- In Body: subscribe
Archive: http://ftp.sterling.com/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. 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 Requirements Document.

Efforts by the working group will focus on a single deliverable: ---------------------------------------------------------------- Define the use of security and associated processes for exchanging EDI transactions in MIME in a manner which supports core, functional, transport services requirements.

Additional Administrative information: -------------------------------------- Editor: Chuck Shih Mats Jansson First Readers: Lincoln Yarbrough Rik Drummond

Goals and Milestones

Mar 96: Submit outline for the informationl requirements document.
Jul 96: Submit informational requirements document as an Internet-Draft.
Oct 96: Submit both Applicability Statement documents as Internet-Drafts.
Nov 96: Submit requirements document Internet-Draft to IESG for consideration as an Informational RFC.
Nov 96: Submit AS Internet-Draft documents to IESG for consideration as Proposed Standards.