I-D ACTION:draft-ietf-trade-iotp-v1.0-papi-06.txt

Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com> Fri, 26 March 2004 16:26 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HV600C02YZNVD@elistx.com> (original mail from Donald.Eastlake@motorola.com); Fri, 26 Mar 2004 11:26:11 -0500 (EST)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HV600C01YZNVC@elistx.com> for ietf-trade@lists.elistx.com; Fri, 26 Mar 2004 11:26:11 -0500 (EST)
Received: from motgate8.mot.com (motgate8.mot.com []) by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0HV6009I7YZNEK@elistx.com> for ietf-trade@lists.elistx.com; Fri, 26 Mar 2004 11:26:11 -0500 (EST)
Received: from il06exr06.mot.com (il06exr06.mot.com []) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i2QGQ5sh004077 for <ietf-trade@lists.elistx.com>; Fri, 26 Mar 2004 09:26:05 -0700 (MST)
Received: from ma19exm01.e6.bcs.mot.com (ma19exm01.e6.bcs.mot.com []) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i2QGP8RD024208 for <ietf-trade@lists.elistx.com>; Fri, 26 Mar 2004 10:25:58 -0600
Received: by ma19exm01.e6.bcs.mot.com with Internet Mail Service (5.5.2657.2) id <F561ZFV9>; Fri, 26 Mar 2004 11:25:08 -0500
Content-return: allowed
Date: Fri, 26 Mar 2004 11:25:05 -0500
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
Subject: I-D ACTION:draft-ietf-trade-iotp-v1.0-papi-06.txt
To: ietf-trade@lists.elistx.com
Message-id: <62173B970AE0A044AED8723C3BCF23810408B35B@ma19exm01.e6.bcs.mot.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-type: text/plain
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
List-Id: <ietf-trade.lists.elistx.com>

I thought things were fixed so ID announcements would come through on the TRADE WG
mailing list but I guess not or I wouldn't have to forward this...

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		: Payment API for v1.0 Internet Open Trading Protocol (IOTP)
	Author(s)	: W. Hans,  et al.
	Filename	: draft-ietf-trade-iotp-v1.0-papi-06.txt
	Pages		: 103
	Date		: 2004-3-25
The Internet Open Trading Protocol provides a data exchange format
for trading purposes while integrating existing pure payment
protocols seamlessly. This motivates the multiple layered system
architecture which consists of at least some generic IOTP application
core and multiple specific payment modules.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-iotp-v1.0-papi-06.txt".

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

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

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-v1.0-papi-06.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.