NOTE: This charter is accurate as of the 29th IETF Meeting in Seattle. 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.
Electronic Data Interchange (EDI) Charter
Chair(s)
- Dave Crocker <dcrocker@mordor.stanford.edu>
Mailing List Information
- General Discussion <ietf-edi@byu.edu>
- To Subscribe <listserv@byu.edu>
- In Body <sub ietf-edi >
- Archive <ftp.sterling.com:edi/lists>
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. The working group will produce specifications for the use
of EDI standards over the Internet, with an initial focus on the
transport of EDI via Internet e-mail. The EDI community is large,
diverse and well-established. This working group effort is explicitly
NOT intending to specify or modify any of the details of EDI protocols
themselves. Instead, it will focus on the requirements for proper
carriage of EDI over the Internet, attending only to issues of
encapsulation, addressing, security and the like.
Initial efforts by the working group will focus on two deliverables:
specification for the carriage of various EDI content via MIME-based
e-mail, and a discussion document, considering issues in the use of
EDI over the Internet. The usage document will cover such issues as
addressing and security.
Goals and Milestones
- Done
- Submit specification for carriage of various EDI "interchange" transactions via MIME-based e-mail as an Internet-Draft.
- Jun 1994
- Submit "specification for carriage..." document (EDI transport) to the IESG for consideration as a Proposed Standard.
- Jul 1994
- Complete outline for usage document and include it in the minutes from the Toronto IETF.
- Aug 1994
- Submit first the draft of the usage document as an Internet-Draft.
- Oct 1994
- Submit the finalized usage document for publication as an RFC.
Internet-Drafts
RFCs