< draft-ietf-edi-mime-00.txt		draft-ietf-edi-mime-01.txt >
	Network Working Group D. Crocker		Network Working Group D. Crocker
	Internet-Draft: Brandenburg Consulting		Internet-Draft: DRAFT-IETF-EDI-MIME-01.{txt,ps} Brandenburg Consulting
	DRAFT-IETF-EDI-MIME-00.{txt,ps} 13 December 1994
	Expiration <6/95>		Expiration <6/95>
	MIME Encapsulation of EDI Objects		MIME Encapsulation of EDI Objects
	STATUS OF THIS MEMO		STATUS OF THIS MEMO
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its		documents of the Internet Engineering Task Force (IETF), its
	areas, and its working groups. Note that other groups may also		areas, and its working groups. Note that other groups may also
	distribute working documents as Internet-Drafts.		distribute working documents as Internet-Drafts.
	skipping to change at line 28 ¶		skipping to change at line 27 ¶
	documents at any time. It is inappropriate to use Internet-		documents at any time. It is inappropriate to use Internet-
	Drafts as reference material or to cite them other than as ``work		Drafts as reference material or to cite them other than as ``work
	in progress.''		in progress.''
	To learn the current status of any Internet-Draft, please check		To learn the current status of any Internet-Draft, please check
	the ``1id-abstracts.txt'' listing contained in the Internet-		the ``1id-abstracts.txt'' listing contained in the Internet-
	Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net		Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
	(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East		(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East
	Coast), or ftp.isi.edu (US West Coast).		Coast), or ftp.isi.edu (US West Coast).
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	TABLE OF CONTENTS		TABLE OF CONTENTS
	1. Introduction		1. Introduction
	2. Application/EDI-X12 specification		2. Application/EDIFACT specification
	3. Application/EDIFACT specification		3. Application/EDI-X12 specification
	4. Application/EDI-Consent specification		4. Application/EDI-Consent specification
	5. Sample EDI usage in MIME-based email		5. Sample edi usage in MIME-based email
	6. References		6. References
	7. Security considerations		7. Security considerations
	8. Acknowledgments		8. Acknowledgments
	9. Contact		9. Contact
	A. Appendix - MIME for EDI users		10. Appendix - MIME for EDI users
	1. Introduction		D. Crocker 1
			Introduction
	Electronic Data Interchange (EDI) provides a means of conducting		Electronic Data Interchange (EDI) provides a means of conducting
	structured transactions between trading partners. The delivery		structured transactions between trading partners. The delivery
	mechanism for these types of transactions in a paper world has		mechanism for these types of transactions in a paper world has
	been the postal system, so it is to be expected that electronic		been the postal system, so it is to be expected that electronic
	mail would serve as a natural delivery mechanism for electronic		mail would serve as a natural delivery mechanism for electronic
	transactions. This specification permits formatted electronic		transactions. This specification permits formatted electronic
	business interchanges to be encapsulated within MIME messages		business interchanges to be encapsulated within MIME messages
	[Bore92]. For the specification effort, the basic building block		[Bore92]. For the specification effort, the basic building block
	from EDI is an interchange.		from EDI is an interchange.
	This specification pertains only to the encapsulation of EDI		This specification pertains only to the encapsulation of EDI
	objects within the MIME environment. It intends no changes in		objects within the MIME environment. It intends no changes in
	those objects from the primary specifications that define the		those objects from the primary specifications that define the
	syntax and semantics of them. EDI transactions take place		syntax and semantics of them. EDI transactions take place
	through a variety of carriage and exchange mechanisms. This		through a variety of carriage and exchange mechanisms. This
	specification adds to that repertoire, by permitting convenient		specification adds to that repertoire, by permitting convenient
	carriage through Internet email.		carriage through Internet email.
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	Since there are many different EDI specifications, the current		Since there are many different EDI specifications, the current
	document defines three distinct categories as three different		document defines three distinct categories as three different
	MIME content-types. One is Application/EDI-X12, indicating that		MIME content-types. One is Application/EDI-X12, indicating that
	the contents conform to the range of specifications developed		the contents conform to the range of specifications developed
	through the X12 standards organization [X125, X126, X12V].		through the X12 standards organization [X125, X126, X12V].
	Another is Application/EDIFACT, indicating that the contents		Another is Application/EDIFACT, indicating that the contents
	conform to the range of specifications developed by the United		conform to the range of specifications developed by the United
	Nations Working Party 4 Group of Experts 1 EDIFACT boards [FACT,		Nations Working Party 4 Group of Experts 1 EDIFACT boards [FACT,
	FACV]. The last category covers all other specifications; it is		FACV]. The last category covers all other specifications; it is
	Application/EDI-consent.		Application/EDI-consent.
	2. APPLICATION/EDI-X12 SPECIFICATION		2. APPLICATION/EDIFACT SPECIFICATION
	The Application/EDI-X12 MIME body-part contains data as specified		The Application/EDIFACT MIME body-part contains data as specified
	for electronic data interchange by [X125, X12.6, EDIV].		for electronic data interchange by [FACT, FACV].
	Within MIME, EDI-X12 information is specified by:		D. Crocker 2
			Within EDIFACT, information is specified by:
	MIME type name: Application		MIME type name: Application
	MIME subtype name: EDI-X12		MIME subtype name: EDIFACT
	Required parameters: none		Required parameters: none
	Optional parameters: CHARSET, as defined for MIME		Optional parameters: CHARSET, as defined for MIME
	Encoding considerations: May need BASE64 or QUOTED-PRINTABLE		Encoding considerations: May need BASE64 or QUOTED-PRINTABLE
	transfer encoding		transfer encoding
	Security considerations: See separate section in the		Security considerations: See separate section in the
	document.		document.
	Published specification: Contained in the following section.		Published specification: Contained in the following section.
	Internet Draft EDI in MIME (Expiration: 6/95)		Rationale: The EDIFACT specifications are
	D. Crocker x
	Rationale: The ASC X12 EDI specifications are
	accepted standards for a class of		accepted standards for a class of
	inter-organization transactions;		inter-organization transactions;
	this permits their transmission		this permits their transmission
	over the Internet, via email.		over the Internet, via email.
	Contact-info: See Contact section, below.		Contact-info: See Contact section, below.
	Detail specific to MIME-based usage:		Detail specific to MIME-based usage:
	This is a generic mechanism for sending any ASC X12		This is a generic mechanism for sending any EDIFACT
	interchange. The object is self-defining, in terms of		interchange. The object is self-defining, in terms of
	indicating which specific EDI objects are included. Most		indicating which specific EDI objects are included. Most
	EDI data is textual, but special characters such as some		EDI data is textual, but special characters such as some
	delimiters may be non-printable ASCII or some data may be		delimiters may be non-printable ASCII or some data may be
			D. Crocker 3
	pure binary. For EDI objects containing such data, the MIME		pure binary. For EDI objects containing such data, the MIME
	transfer mechanism may need to encode the object in Content-		transfer mechanism may need to encode the object in Content-
	Transfer-Encoding:quoted-printable or base64.		Transfer-Encoding:quoted-printable or base64.
	3. APPLICATION/EDIFACT SPECIFICATION		3. APPLICATION/EDI-X12 SPECIFICATION
	The Application/EDIFACT MIME body-part contains data as specified		The Application/EDI-X12 MIME body-part contains data as specified
	for electronic data interchange by [FACT, FACV].		for electronic data interchange by [X125, X12.6, EDIV].
	Within EDIFACT, information is specified by:		Within MIME, EDI-X12 information is specified by:
	MIME type name: Application		MIME type name: Application
	MIME subtype name: EDIFACT		MIME subtype name: EDI-X12
	Required parameters: none		Required parameters: none
	Optional parameters: CHARSET, as defined for MIME		Optional parameters: CHARSET, as defined for MIME
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	Encoding considerations: May need BASE64 or QUOTED-PRINTABLE		Encoding considerations: May need BASE64 or QUOTED-PRINTABLE
	transfer encoding		transfer encoding
	Security considerations: See separate section in the		Security considerations: See separate section in the
	document.		document.
	Published specification: Contained in the following section.		Published specification: Contained in the following section.
	Rationale: The EDIFACT specifications are		Rationale: The ASC X12 EDI specifications are
	accepted standards for a class of		accepted standards for a class of
	inter-organization transactions;		inter-organization transactions;
	this permits their transmission		this permits their transmission
	over the Internet, via email.		over the Internet, via email.
	Contact-info: See Contact section, below.		Contact-info: See Contact section, below.
			D. Crocker 4
	Detail specific to MIME-based usage:		Detail specific to MIME-based usage:
	This is a generic mechanism for sending any EDIFACT		This is a generic mechanism for sending any ASC X12
	interchange. The object is self-defining, in terms of		interchange. The object is self-defining, in terms of
	indicating which specific EDI objects are included. Most		indicating which specific EDI objects are included. Most
	EDI data is textual, but special characters such as some		EDI data is textual, but special characters such as some
	delimiters may be non-printable ASCII or some data may be		delimiters may be non-printable ASCII or some data may be
	pure binary. For EDI objects containing such data, the MIME		pure binary. For EDI objects containing such data, the MIME
	transfer mechanism may need to encode the object in Content-		transfer mechanism may need to encode the object in Content-
	Transfer-Encoding:quoted-printable or base64.		Transfer-Encoding:quoted-printable or base64.
	4. APPLICATION/EDI-CONSENT SPECIFICATION		4. APPLICATION/EDI-CONSENT SPECIFICATION
	The Application/EDI-consent MIME body-part contains data as		The Application/EDI-consent MIME body-part contains data as
	specified for electronic data interchange with the consent of		specified for electronic data interchange with the consent of
	explicit, bilateral trading partner agreement exchanging the EDI-		explicit, bilateral trading partner agreement exchanging the EDI-
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	consent traffic. As such, use of EDI-consent only provides a		consent traffic. As such, use of EDI-consent only provides a
	standard mechanism for "wrapping" the EDI objects but does not		standard mechanism for "wrapping" the EDI objects but does not
	specify any of the details about those objects.		specify any of the details about those objects.
	Within MIME, EDI-consent information is specified by:		Within MIME, EDI-consent information is specified by:
	MIME type name: Application		MIME type name: Application
	MIME subtype name: EDI-consent		MIME subtype name: EDI-consent
	Required parameters: none		Required parameters: none
	Optional parameters: CHARSET, as defined for MIME		Optional parameters: CHARSET, as defined for MIME
	Encoding considerations: May need BASE64 or QUOTED-PRINTABLE		Encoding considerations: May need BASE64 or QUOTED-PRINTABLE
	transfer encoding		transfer encoding
	Security considerations: See separate section in the		Security considerations: See separate section in the
	document.		document.
			D. Crocker 5
	Published specification: Contained in the following section.		Published specification: Contained in the following section.
	Rationale: Existing practice for exchanging		Rationale: Existing practice for exchanging
	EDI includes a very wide range of		EDI includes a very wide range of
	specifications which are not part		specifications which are not part
	of the usual, accredited standards		of the usual, accredited standards
	world. Nevertheless, this traffic		world. Nevertheless, this traffic
	is substantial and well-		is substantial and well-
	established. This content type		established. This content type
	provides a means of delimiting such		provides a means of delimiting such
	content in a standard fashion.		content in a standard fashion.
	Contact-info: See Contact section, below.		Contact-info: See Contact section, below.
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	Detail specific to MIME-based usage:		Detail specific to MIME-based usage:
	This is a generic mechanism for sending any EDI object		This is a generic mechanism for sending any EDI object
	explicitly agreed to by the trading partners. X12 and		explicitly agreed to by the trading partners. X12 and
	EDIFACT object must be sent using their assigned MIME		EDIFACT object must be sent using their assigned MIME
	content type. EDI-consent is for all other EDI objects, but		content type. EDI-consent is for all other EDI objects, but
	only according to trading partner agreements between the		only according to trading partner agreements between the
	originator and the recipient. Most EDI data is textual,		originator and the recipient. Most EDI data is textual,
	but special characters such as some delimiters may be non-		but special characters such as some delimiters may be non-
	printable ASCII or some data may be pure binary. For EDI		printable ASCII or some data may be pure binary. For EDI
	objects containing such data, the MIME transfer mechanism		objects containing such data, the MIME transfer mechanism
	may need to encode the object in Content-Transfer-		may need to encode the object in Content-Transfer-
	Encoding:quoted-printable or base64.		Encoding:quoted-printable or base64.
	5. SAMPLE EDI USAGE IN MIME-BASED EMAIL		5. SAMPLE EDI USAGE IN MIME-BASED EMAIL
	Actual use of EDI within MIME-based mechanisms requires attention		Actual use of EDI within MIME-based mechanisms requires attention
	to considerable detail. This section is intended as an example		to considerable detail. This section is intended as an example
	of the gist of the formatting required to encapsulate EDI objects		of the gist of the formatting required to encapsulate EDI objects
	within Internet mail, using MIME. To send a single X12-EDI
			D. Crocker 6
			Internet Draft EDI in MIME (Expiration: 6/95)
			within Internet mail, using MIME. To send a single EDIFACT
	interchange:		interchange:
	To: <<recipient organization EDI email address>>		To: <<recipient organization EDI email address>>
	Subject:		Subject:
	From: <<sending organization EDI email address>>		From: <<sending organization EDI email address>>
	Date:		Date:
	Mime-Version: 1.0		Mime-Version: 1.0
	Content-Type: Application/EDI-X12		Content-Type: Application/EDIFACT
	Content-Transfer-Encoding: QUOTED-PRINTABLE		Content-Transfer-Encoding: QUOTED-PRINTABLE
	<<standard ASC X12 EDI Interchange goes here>>		<<standard EDIFACT Interchange goes here>>
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	6. REFERENCES		6. REFERENCES
	[Bore92] Borenstein, N. & Freed, N., "Mime (Multipurpose		[Bore92] Borenstein, N. & Freed, N., "Mime (Multipurpose
	Internet Mail Extensions): Mechanisms for		Internet Mail Extensions): Mechanisms for
	Specifying and Describing The Format of Internet		Specifying and Describing The Format of Internet
	Message Bodies". March, 1992, Network Information		Message Bodies". March, 1992, Network Information
	Center, RFC 1341.		Center, RFC 1341.
	[Brad89] Braden, R.T., "Requirements for Internet hosts -		[Brad89] Braden, R.T., "Requirements for Internet hosts -
	application and support". October, 1989, Network		application and support". October, 1989, Network
	Information Center, RFC 1321.		Information Center, RFC 1321.
	skipping to change at line 279 ¶		skipping to change at line 260 ¶
	Text Messages". September, 1982, Network		Text Messages". September, 1982, Network
	Information Center, RFC 822.		Information Center, RFC 822.
	[Rose93] Rose, M., "The Internet Message: Closing the Book		[Rose93] Rose, M., "The Internet Message: Closing the Book
	with Electronic Mail". PTR Prentice Hall, Englewood		with Electronic Mail". PTR Prentice Hall, Englewood
	Cliffs, N.J. (1993)		Cliffs, N.J. (1993)
	[Post82] Postel, J., "Simple Mail Transfer Protocol".		[Post82] Postel, J., "Simple Mail Transfer Protocol".
	October, 1982, Network Information Center, RFC 821.		October, 1982, Network Information Center, RFC 821.
			D. Crocker 7
	[X12V] Data Interchange Standards Association; sets of		[X12V] Data Interchange Standards Association; sets of
	specific EDI standards are ordered by their version		specific EDI standards are ordered by their version
	number; Washington D.C.		number; Washington D.C.
	[X125] ANSI X12.5 Interchange Control Structure for		[X125] ANSI X12.5 Interchange Control Structure for
	Electronic Data Interchange, Washington D.C.: DISA		Electronic Data Interchange, Washington D.C.: DISA
	[X126] ANSI X12.6 Applications Control Structures for		[X126] ANSI X12.6 Applications Control Structures for
	Electronic Data Interchange, Washington D.C.: DISA		Electronic Data Interchange, Washington D.C.: DISA
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	[FACT] United Nations Economic Commission (UN/EC)		[FACT] United Nations Economic Commission (UN/EC)
	Electronic Data Interchange For Administration,		Electronic Data Interchange For Administration,
	Commerce and Transport (EDIFACT) - Application Level		Commerce and Transport (EDIFACT) - Application Level
	Syntax Rules (ISO 9735), 1991.		Syntax Rules (ISO 9735), 1991.
	[FACV] Version sets contains the specific syntax documents,		[FACV] Version sets contains the specific syntax documents,
	the element and segment dictionaries, and the		the element and segment dictionaries, and the
	transaction/message specifications.		transaction/message specifications.
	7. SECURITY CONSIDERATIONS		7. SECURITY CONSIDERATIONS
	EDI transactions typically include sensitive data, so that		EDI transactions typically include sensitive data, so that
	transmission often needs to attend to authentication, data		transmission often needs to attend to authentication, data
	integrity, privacy, access control and non-repudiation concerns.		integrity, privacy, access control and non-repudiation concerns.
	This specification permits transmission of such sensitive data		This specification permits transmission of such sensitive data
	via Internet mail and other services which support MIME object		via Internet mail and other services which support MIME object
	encapsulation. For transmission of sensitive data, it is		encapsulation. For transmission of sensitive data, it is
	essential that appropriate security services, such as		essential that appropriate security services, such as
	authentication, privacy and/or non-repudiation be provided.		authentication, privacy and/or non-repudiation be provided.
	This specification does NOT, itself, provide any security-related		This specification does NOT, itself, provide any security-related
	mechanisms. As needed and appropriate, such mechanisms MUST be		mechanisms. As needed and appropriate, such mechanisms MUST be
	added, either via Internet MIME-based security services or any		added, either via Internet MIME-based security services or any
			D. Crocker 8
	other services which are appropriate to the user requirements,		other services which are appropriate to the user requirements,
	such as those provided EDI-based standards.		such as those provided by EDI-based standards.
	8. ACKNOWLEDGMENTS		8. ACKNOWLEDGMENTS
	Tom Jones offered introductory text and descriptions of candidate		Tom Jones offered introductory text and descriptions of candidate
	header options. Numerous working group participants provided		header options. Numerous working group participants provided
	review and comment, especially Walt Houser, Gail Jackson, and Jim		review and comment, especially Walt Houser, Gail Jackson, and Jim
	Amster.		Amster.
	Internet Draft EDI in MIME (Expiration: 6/95)		9. CONTACT
	D. Crocker x
	9. CONTACT
	David H. Crocker		David H. Crocker
	Brandenburg Consulting		Brandenburg Consulting
	675 Spruce Dr.		675 Spruce Dr.
	Sunnyvale, CA 94086 USA		Sunnyvale, CA 94086 USA
	<dcrocker@mordor.stanford.edu>		<dcrocker@mordor.stanford.edu>
	Phone: +1 408 246 8253		Phone: +1 408 246 8253
	Fax: +1 408 249 6205		Fax: +1 408 249 6205
	A. APPENDIX - MIME FOR EDI USERS		10. APPENDIX - MIME FOR EDI USERS
	To assist those familiar with EDI but not with Internet		To assist those familiar with EDI but not with Internet
	electronic mail, this Appendix is provided as a very brief		electronic mail, this Appendix is provided as a very brief
	introduction, primarily to give pointers to the relevant		introduction, primarily to give pointers to the relevant
	specifications. This section is in no way intended to be a		specifications. This section is in no way intended to be a
	thorough introduction. An excellent introductory text is		thorough introduction. An excellent introductory text is
	[Rose93].		[Rose93].
			D. Crocker 9
	Internet electronic mail follows the classic user agent/mail		Internet electronic mail follows the classic user agent/mail
	transfer agent model. In this model, user software produces a		transfer agent model. In this model, user software produces a
	standardized object which is transferred via standard exchange		standardized object which is transferred via standard exchange
	protocols.		protocols.
	An Internet electronic mail object comprises a collection of		An Internet electronic mail object comprises a collection of
	headers, followed by a (possibly structured) body. The headers		headers, followed by a (possibly structured) body. The headers
	specify such information as author and recipient addresses,		specify such information as author and recipient addresses,
	subject summary, creation date, handling node names, and so on,		subject summary, creation date, handling node names, and so on,
	and are defined by RFC822 and RFC1123 [Croc82, Brad89]. If the		and are defined by RFC822 and RFC1123 [Croc82, Brad89]. If the
	body is structured, it conforms to the rules of the Multipurpose		body is structured, it conforms to the rules of the Multipurpose
	Internet Draft EDI in MIME (Expiration: 6/95)
	D. Crocker x
	Internet Message Exchange (MIME) [Bore92]. A structured body may		Internet Message Exchange (MIME) [Bore92]. A structured body may
	have parts encoded in different text character sets, or even of		have parts encoded in different text character sets, or even of
	entirely different types of data, such as voice or graphics.		entirely different types of data, such as voice or graphics.
	The Simple Mail Transfer Protocol (SMTP) [Post82, Brad89]		The Simple Mail Transfer Protocol (SMTP) [Post82, Brad89]
	performs the primary task of message transmission. User posting		performs the primary task of message transmission. User posting
	and delivery interactions, between the user agent and the message		and delivery interactions, between the user agent and the message
	transfer agent, on the same machine, are not standardized and are		transfer agent, on the same machine, are not standardized and are
	platform-specific.		platform-specific.
	An EDI-related use of Internet Mime email will have (at least)		An EDI-related use of Internet Mime email will have (at least)
	the following components:		the following components:
	Business Program/Data base -> EDI Translator ->		Business Program/Data base -> EDI Translator ->
	-> MIME encapsulation -> RFC822 packaging ->		-> MIME encapsulation -> RFC822 packaging -> mail
	-> mail submission -> SMTP relaying ->		submission ->
			-> SMTP relaying ->
	-> mail delivery -> RFC822 & Mime stripping ->		-> mail delivery -> RFC822 & Mime stripping ->
	-> EDI Translator -> Business processing		-> EDI Translator -> Business processing
	The first and last lines show components normal to all EDI		The first and last lines show components normal to all EDI
	activities, so that it is only the EDI "transmission" components		activities, so that it is only the EDI "transmission" components
	that are replaced with Internet modules.		that are replaced with Internet modules.
			D. Crocker 10
			--------------------
			Dave Crocker
			Brandenburg Consulting +1 408 246 8253
			675 Spruce Dr. fax: +1 408 249 6205
			Sunnyvale, CA 94086 dcrocker@mordor.stanford.edu
End of changes. 43 change blocks.
	77 lines changed or deleted		50 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/