I-D ACTION:draft-ietf-trade-xmlmsg-requirements-00.txt

Internet-Drafts@ietf.org Tue, 25 January 2000 15:56 UTC

Return-Path: <ietf-trade-errors@lists.eListX.com>
Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOW00A01EXU3H@eListX.com>; Tue, 25 Jan 2000 10:56:18 -0500 (EST)
Received: from FILTER-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOW00A01EXT3F@eListX.com> (original mail from services@eListX.com); Tue, 25 Jan 2000 10:56:17 -0500 (EST)
Received: from FILTER-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOW00A03EXR3D@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822; ietf-trade@lists.elistx.com); Tue, 25 Jan 2000 10:56:16 -0500 (EST)
Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-31 #39671) id <0FOW00A01EXQ3C@eListX.com> for ietf-trade@filter.eListX.com (ORCPT rfc822; ietf-trade@lists.elistx.com); Tue, 25 Jan 2000 10:56:14 -0500 (EST)
Received: from eListX.com by eListX.com (PMDF V5.2-31 #39671) id <0FOW00A01EXQ3B@eListX.com> for ietf-trade@lists.eListX.com; Tue, 25 Jan 2000 10:56:14 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V5.2-31 #39671) with ESMTP id <0FOW007AZ4JNZS@eListX.com> for ietf-trade@lists.eListX.com; Tue, 25 Jan 2000 07:11:48 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21836; Tue, 25 Jan 2000 07:10:25 -0500 (EST)
Resent-date: Tue, 25 Jan 2000 10:56:14 -0500
Date: Tue, 25 Jan 2000 07:10:25 -0500
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-trade-xmlmsg-requirements-00.txt
Sender: services@eListX.com
To: IETF-Announce:;
Cc: ietf-trade@lists.eListX.com
Reply-to: Internet-Drafts@ietf.org
Resent-message-id: <0FOW00A02EXQ3C@eListX.com>
Message-id: <200001251210.HAA21836@ietf.org>
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_nqcj9taOly7Lv8Ku/KtiDg)"

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Requirements for XML Messaging Version 1.0 Release 00
	Author(s)	: D. Burdett
	Filename	: draft-ietf-trade-xmlmsg-requirements-00.txt
	Pages		: 60
	Date		: 24-Jan-00
	
This specification contains requirements for a generic approach to
the reliable, resilient, secure, tamper resistant, authenticated
exchange of XML or other electronic documents over insecure transport
mechanisms.
The specification provides the requirements and framework for a set
of related specifications on XML Messaging covering:
o Requirements for XML Messaging (this paper)
o Common XML Message Elements
o Document Exchange and Transactions
o Reliable Messaging
o Secure Messaging
o Document Choreography Definitions
o Common Document Exchanges
o Transport Protocol Supplements
Although much work has been carried out on the other parts of the XML
Messaging specification described above, they are sill in development

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-xmlmsg-requirements-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-xmlmsg-requirements-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-xmlmsg-requirements-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-trade-xmlmsg-requirements-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-trade-xmlmsg-requirements-00.txt>