Electronic Data Interchange-Internet Integration (ediint) --------------------------------------------------------- Charter Last Modified: 2005-05-26 Current Status: Active Working Group Chair(s): Rik Drummond Applications Area Director(s): Ted Hardie Scott Hollenbeck Applications Area Advisor: Scott Hollenbeck Mailing Lists: General Discussion:ietf-ediint@imc.org To Subscribe: ietf-ediint-request@imc.org In Body: subscribe Archive: http://www.imc.org/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. Many believe these heading fields are best described in XML. 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. Deliverables: AS1 - Applicability Statement describing how current Internet standards can be used to achieve this functionality for MIME and SMTP. Security supported is object signature and object based encryption only. RFC3335. AS2 - Applicability Statement describing how current Internet standards can be used to achieve this functionality for Process-to-Process (real-time) EDI based on MIME and HTTP. Security supported is object signature, and both session and object encryption.(draft-ietf-ediint-as2-xx.txt) AS3 - Applicability Statement describing how current Internet standards can be used to achieve the transfer of EDI or XML data over internet in a secure manner based on FTP. Security supported is object signature, and both session and object encryption.(draft-ietf-ediint-as3-xx.txt) Goals and Milestones: Done Submit outline for the informationl requirements document. Done Submit informational requirements document as an Internet-Draft. Done Submit both Applicability Statement documents as Internet-Drafts. Done Submit AS Internet-Draft documents to IESG for consideration as Proposed Standards. Done Submit requirements document Internet-Draft to IESG for consideration as an Informational RFC. Done Submit second applicability statement(AS#2)and the Security document as Internet-Drafts. Done Submit AS#2 and Security Document to IESG for consideration as Internet-Draft documents for Proposed Standard. Done Submit draft-ietf-ediint-req to the IESG for consideration as an proposed standard Done Submit draft-ietf-ediint-as1 to the IESG for consideration as a proposed standard Done Submit draft-ietf-ediint-hl7 to the IESG for consideration as a Proposed Standard Done Submit draft-ietf-ediint-as2 to the IESG for consideration as a Proposed Standard Done Submit AS1 Internet-Draft document to IESG for consideration as Proposed Standard Done Submit AS2 Internet-Draft document to IESG for consideration as Proposed Standard. Dec 2005 Submit AS3 Internet-Draft document to IESG for consideration as Proposed Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jun 2003 Jan 2006 FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC3335 PS Sep 2002 MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet RFC4130Standard Jul 2005 MIME-based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)