Frequently Asked Questions (FAQ): EDI Meets
the Internet by W. Houser (Department of Veteran Affairs Washington D.C. , January
1996. This paper is very basic; asking and answering questions such as How fast is the
Internet? , What about security? , What are the ways that EDI files could be transfered
via the Internet?
Department of Energy web site on the Electric industry Real time information Networks , strangely enough there is discussion of EDI at this site by Bill Johnson (Department of Energy Washington D.C.
RFC 821 SMTP - J. Postel, "Simple
Mail Transfer Protocol", STD 10, RFC 821, August 1, 1982.
This is the core mail transfer standard that all MTA's need to adhere to.
RFC 822 Text Message Format - D. Crocker,
"Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822,
August 13, 1982.
Defines message header fields and the parts making up a message.
RFC 1521 MIME - N. Borenstein, N.Freed,
"MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and
Describing the Format of Internet Message Bodies", RFC 1521, September 23, 1993.
This is the basic MIME standard, upon which all MIME related RFCs build, including this one. Key contributions include definition of "content type" and sub-type "multipart", in addition to encoding guidelines, which establish 7-bit US-ASCII as the lowest common denominator used.
RFC 1847 MIME Security Multiparts - J.
Galvin, S. Murphy, S. Crocker, N. Freed, "Security Multiparts for MIME:
Multipart/Signed and Multipart/Encrypted", RFC 1847, 1995
This document defines security multiparts for MIME: multipart/encrypted and multipart/signed.
RFC 1892 Multipart/report - G.
Vaudreuil, "The Multipart/Report Content Type for the Reporting of Mail System
Administrative Messages", RFC 1892, January 15, 1996.
This RFC defines the use of Multipart/report content type, something that the MDN draft (fajman) relies on for the receipt functionality.
RFC 1767 EDI Content - D. Crocker,
"MIME Encapsulation of EDI Objects", RFC 1767, March 2, 1995.
This RFC defines the use of content type "application" for ANSI X12 (application/EDI-X12), EDIFACT (application/EDIFACT) and mutually defined EDI (application/EDI-Consent).
RFC 2015 PGP/MIME -(M. Elkins,
"MIME Security With Pretty Good Privacy (PGP)", RFC 2015, Sept. 1996.
This RFC defines the use of content types "multipart/encrypted", "multipart/signed", "application/pgp encrypted" and "application/pgp-signature" for defining MIME PGP content.
(fajman): Message Disposition Notification - R. Fajman, "An
Extensible Message Format for Message Disposition Notifications",
draft-ietf-receipt-mdn-06.txt, October 22, 1997.
This Internet draft defines how a "signed receipt" is requested, and the structure of the signed receipt, also called message disposition notification.
Specifications - S/MIME (RSA Security, Inc.) - RSA Laboratories, "S/MIME Message Specification; PKCS
Security Services for MIME", Version of February 23, 1996.
This specification describes how MIME shall carry PKCS7 envelope information.
Internet draft from the Internet Engineering Task Force (IETF) subgroup on Internet EDI covering Requirements for Inter-operable Internet EDI (72141 bytes) which addresses many of the technical and security issues facing the FTTF (C. Shih, "Requirements for Inter-operable Internet EDI", July 8, 1997.).
Internet draft from the Internet Engineering Task Force (IETF) subgroup on Internet EDI covering MIME-based Secure EDI (51613 bytes).
Return to GISB's Home Page
Send e-mail to: email@example.com
Copyright © 1995, 1996, 1997 Gas Industy Standards Board, Inc. All Rights Reserved. This material may not be reproduced in any form without permission.