Subject: Advancing the Voucher drafts and ECMLv2
From: Eastlake III Donald-LDE008 <[email-masked]>
To: "[email-masked]'" <[email-masked]>
Date: Thu, 29 Apr 2004 16:19:56 -0400
List-Id: <ietf-trade.lists.elistx.com>

Just to update you on what is happening, since the Last Call on them is over and there were no negative comments, I have requested on behalf of the working group, that
	draft-ietf-trade-voucher-lang-06.txt and
	draft-ietf-trade-voucher-vtsapi-06.txt
be published as Informational RFCs and I have submitted a new version of the ECMLv2 draft:
	draft-ietf-trade-ecml2-spec-09.txt

Donald
===========================================================
 Donald E. Eastlake III       [email-masked]
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA

Date: Thu, 29 Apr 2004 15:50:17 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-ecml2-spec-09.txt
Sender: [email-masked]
To: [email-masked]
Cc: [email-masked]

--NextPart

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		: Electronic Commerce Modeling Language (ECML):Version 2 Specification
	Author(s)	: D. Eastlake
	Filename	: draft-ietf-trade-ecml2-spec-09.txt
	Pages		: 27
	Date		: 2004-4-29
	
Electronic commerce frequently requires a substantial exchange of
   information in order to complete a purchase or other transaction,
   especially the first time the parties communicate. A standard set of
   hierarchically organized payment related information field names in
   an XML syntax are defined so that this task can be more easily
   automated. This is the second version of an Electronic Commerce
   Modeling Language (ECML) and is intended to meeting the requirements
   of RFC 3505.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-ecml2-spec-09.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ecml2-spec-09.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:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-ecml2-spec-09.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-ecml2-spec-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-trade-ecml2-spec-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Content-return: allowed
Date: Wed, 28 Apr 2004 13:43:30 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: RE: ECML DTD
To: 'Jeremiah Andrick' <[email-masked]>
Cc: "[email-masked]'" <[email-masked]>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C42D48.51BECAD0
Content-Type: text/plain

Jeremiah,
 
The IETF TRADE working group is currenting working on the ECML standard. IETF working groups do not have a defined membership but do most of their work by mailing list. If you haven't yet subscribed, you are welcome to do so using the directions on the WG charter page at http://www.ietf.org/html.charters/trade-charter.html <http://www.ietf.org/html.charters/trade-charter.html>  and post any comments or suggestions. (For IETF Working Group Guidelines an Procedures, see http://www.ietf.org/rfc/rfc2418.txt <http://www.ietf.org/rfc/rfc2418.txt> .)
 
When a document is being developed in the IETF, one would normally expect considerable discussion and comment on the relavent mailing list. The lack of traffic on the TRADE WG mailing list and the fact that almost all of the few messages there come from me is the primary reason that IETF management (the IESG) thinks the TRADE WG is pretty much dead.
 
I am about to post a revised version of the ECML v2 draft which primarily responds to the comments from the IESG (see http://lists.elistx.com/archives/ietf-trade/200402/msg00001.html <http://lists.elistx.com/archives/ietf-trade/200402/msg00001.html> ) but a further revision or revisions to incorporate a schema or fix other problems seems reasonable.
 
I prefer not to send out messages with attachments to the mailing list. If you like, I (or you) could post your hierarchy and .xsd attachments on a web page and post the URL to the mailing list.
 
Thanks,
Donald
===========================================================
 Donald E. Eastlake III       [email-masked] <mailto:[email-masked]> 
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752

-----Original Message-----
From: Jeremiah Andrick [mailto:[email-masked]] 
Sent: Wednesday, April 28, 2004 8:44 AM
To: Eastlake III Donald-LDE008
Subject: RE: ECML DTD

Thanks for your reply, Last night I created a Hierarchy based on our needs using the ECML field spec.

Maybe this would help. Our developers are going to use this as a base until we generate a more formal

XML Schema you can read the included word file to see how I generated the Hierarchy. 

Also, how can I join in on the development of the ECML standard? 

My company is very interested in the ECML standards and would like to be involved.

Jeremiah Andrick        

KBAM! Product Manager          

Kinetic.theTechnologyAgency(tm)

200 Distillery Commons, Suite 200

Louisville, KY  40206-1990

502.719.9587  direct

502.719.9569  fax

[email-masked]

 <http://www.kinetic.distillery.com/> Kinetic.theTechnologyAgency.com

  _____  

From: Eastlake III Donald-LDE008 [mailto:[email-masked]] 
Sent: Tuesday, April 27, 2004 11:32 PM
To: Jeremiah Andrick
Cc: [email-masked]'
Subject: RE: ECML DTD

You are probably right that a namesapce should be allocated and a schema provided

as well as a DTD. Anyone willing to volunteer to help my convert the DTD?

Thanks,

Donald

===========================================================
 Donald E. Eastlake III       [email-masked] <mailto:[email-masked]> 
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752

-----Original Message-----
From: Jeremiah Andrick [mailto:[email-masked]] 
Sent: Tuesday, April 27, 2004 5:58 PM
To: Eastlake III Donald-LDE008
Subject: ECML DTD

I have a question about the ECML document that expired in July. Spec 8.

The DTD included doesn't seem to have a namespace attached to it. 

I have tried converting it to a schema with no luck. And it really isn't clear to

Me, who is not familiar with DTD's, that this is very unusable in its current form.

Have you all developed a XML schema of this DTD?

Jeremiah Andrick        

KBAM! Product Manager          

Kinetic.theTechnologyAgency(tm)

200 Distillery Commons, Suite 200

Louisville, KY  40206-1990 

502.719.9587  direct

502.719.9569  fax

[email-masked]

 <http://www.kinetic.distillery.com/> Kinetic.theTechnologyAgency.com

------_=_NextPart_001_01C42D48.51BECAD0
Content-Type: text/html
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C42D48.51BECAD0--

Content-return: allowed
Date: Tue, 27 Apr 2004 23:32:23 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: RE: ECML DTD
To: 'Jeremiah Andrick' <[email-masked]>
Cc: "[email-masked]'" <[email-masked]>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C42CD1.6B2AF682
Content-Type: text/plain

You are probably right that a namesapce should be allocated and a schema provided
as well as a DTD. Anyone willing to volunteer to help my convert the DTD?
 
Thanks,
Donald
===========================================================
 Donald E. Eastlake III       [email-masked] <mailto:[email-masked]> 
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752

-----Original Message-----
From: Jeremiah Andrick [mailto:[email-masked]] 
Sent: Tuesday, April 27, 2004 5:58 PM
To: Eastlake III Donald-LDE008
Subject: ECML DTD

I have a question about the ECML document that expired in July. Spec 8.

The DTD included doesn't seem to have a namespace attached to it. 

I have tried converting it to a schema with no luck. And it really isn't clear to

Me, who is not familiar with DTD's, that this is very unusable in its current form.

Have you all developed a XML schema of this DTD?

Jeremiah Andrick        

KBAM! Product Manager          

Kinetic.theTechnologyAgency(tm)

200 Distillery Commons, Suite 200

Louisville, KY  40206-1990

502.719.9587  direct

502.719.9569  fax

[email-masked]

 <http://www.kinetic.distillery.com/> Kinetic.theTechnologyAgency.com

------_=_NextPart_001_01C42CD1.6B2AF682
Content-Type: text/html
Content-Transfer-Encoding: base64

------_=_NextPart_001_01C42CD1.6B2AF682--

Content-return: allowed
Date: Mon, 26 Apr 2004 12:20:34 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: RE: Submission of Last Called documents as Informational
To: 'Ko Fujimura' <[email-masked]>, [email-masked]
Cc: Masayuki Terada <[email-masked]>

OK, I'll confirm that that registration will still be OK if voucher-lang is Informational.

Thanks,
Donald
===========================================================
 Donald E. Eastlake III       [email-masked]
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA

-----Original Message-----
From: Ko Fujimura [mailto:[email-masked]] 
Sent: Monday, April 26, 2004 6:53 AM
To: Donald Eastlake 3rd; [email-masked]
Cc: Ko Fujimura; Masayuki Terada
Subject: Re: Submission of Last Called documents as Informational

Donald Eastlake 3rd wrote:

>As for voucher-lang, what I said in the last call was: "This document
>was intended to become a Proposed Standard but if there isn't a higher
>volume of comments, favorable or otherwise, it may be very hard to get
>it approved as other than Informational." Based on the lack of response,
>there is reallyl no chance of getting it approved as Proposed, so I plan
>to submit it as Informational.
>  

I generally agree to publish it as Informational. One of my concerns is 
that the document includes IANA registration requests for the vts-lang 
XML namespace and the schema. My understanding is that, even if it is 
Informational, they are registered in the IANA directory below, 
am I right?

http://www.iana.org/assignments/xml-registry/ns.html
http://www.iana.org/assignments/xml-registry/schema.html

Another note is that the discussion in the IETF was almost finished
after its implementation demonstration at the 54th IETF meeting.
But, related specification, the Infrared Voucher Profile specification
(IrVoucher), is still actively discussing in IrDA (Infrared Data 
Association) and the spec will refer to the vts-lang spec.
So, I would like to have it published as soon as possible even if
it is Informational.

Regards,

Ko
--------------------------------------------------------------
Dr. Ko Fujimura, NTT Information Sharing Platform Laboratories
1-1 Hikarinooka, Yokosuka-shi, Kanagawa 239-0847, JAPAN
Tel: +81-(0)46-859-3814, Fax: +81-(0)46-859-8329
Email: [email-masked]

Date: Mon, 26 Apr 2004 19:53:08 +0900
From: Ko Fujimura <[email-masked]>
Subject: Re: Submission of Last Called documents as Informational
To: Donald Eastlake 3rd <[email-masked]>, [email-masked]
Cc: Ko Fujimura <[email-masked]>, Masayuki Terada <[email-masked]>

Donald Eastlake 3rd wrote:

>As for voucher-lang, what I said in the last call was: "This document
>was intended to become a Proposed Standard but if there isn't a higher
>volume of comments, favorable or otherwise, it may be very hard to get
>it approved as other than Informational." Based on the lack of response,
>there is reallyl no chance of getting it approved as Proposed, so I plan
>to submit it as Informational.
>  
>
I generally agree to publish it as Informational. One of my concerns is 
that the document includes IANA registration requests for the vts-lang 
XML namespace and the schema. My understanding is that, even if it is 
Informational, they are registered in the IANA directory below, 
am I right?

http://www.iana.org/assignments/xml-registry/ns.html
http://www.iana.org/assignments/xml-registry/schema.html

Another note is that the discussion in the IETF was almost finished
after its implementation demonstration at the 54th IETF meeting.
But, related specification, the Infrared Voucher Profile specification
(IrVoucher), is still actively discussing in IrDA (Infrared Data 
Association) and the spec will refer to the vts-lang spec.
So, I would like to have it published as soon as possible even if
it is Informational.

Regards,

Ko
--------------------------------------------------------------
Dr. Ko Fujimura, NTT Information Sharing Platform Laboratories
1-1 Hikarinooka, Yokosuka-shi, Kanagawa 239-0847, JAPAN
Tel: +81-(0)46-859-3814, Fax: +81-(0)46-859-8329
Email: [email-masked]

Date: Sun, 25 Apr 2004 16:45:20 -0400 (EDT)
From: Donald Eastlake 3rd <[email-masked]>
Subject: Submission of Last Called documents as Informational
To: [email-masked]

Hi,

The working group last call on documents

	draft-ietf-trade-voucher-lang-06.txt
and
	draft-ietf-trade-voucher-vtsapi-06.txt

reached its nominal end date during last week. There were no objections
but there weren't any other comments as well. This sort of lack of
response is what makes the IESG think the TRADE working group is pretty
much dead.

voucher-vtsapi was intended to be Informational.

As for voucher-lang, what I said in the last call was: "This document
was intended to become a Proposed Standard but if there isn't a higher
volume of comments, favorable or otherwise, it may be very hard to get
it approved as other than Informational." Based on the lack of response,
there is reallyl no chance of getting it approved as Proposed, so I plan
to submit it as Informational.

I'll wait a couple of days before doing this if anyone has any comments
on this move or on the drafts.

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       [email-masked]
 155 Beaver Street              +1-508-634-2066(h) +1-508-786-7554(w)
 Milford, MA 01757 USA                   [email-masked]

Date: Sun, 25 Apr 2004 16:30:35 -0400 (EDT)
From: Donald Eastlake 3rd <[email-masked]>
Subject: spam leaking through to ietf-trade list
To: [email-masked]

As you may have noticed, a few spams have leaked through to the
ietf-trade mailing list. In particular, the messages with subjects

	Hey, dude, it's me ^_^ :P
and
	Notify from e-mail technical support.

are obvious fogeries. I wish I could promise this sort of thing would
stop but the tide of spam just keeps rising, the spammers keep getting
more clever about how they practice their inherently criminal acticity,
and utility of email just keeps dropping day by day.

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       [email-masked]
 155 Beaver Street              +1-508-634-2066(h) +1-508-786-7554(w)
 Milford, MA 01757 USA                   [email-masked]

Date: Fri, 23 Apr 2004 22:41:26 +0700
From: [email-masked]
Subject: Hey, dude, it's me ^_^ :P
To: [email-masked]

----------msojtaruhqneeexllhxk
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

I don't bite, weah!

password -- 23163

----------msojtaruhqneeexllhxk
Content-Type: application/octet-stream; name="TextFile.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TextFile.zip"

----------msojtaruhqneeexllhxk--

Date: Thu, 22 Apr 2004 23:57:39 -0400 (EDT)
From: Donald Eastlake 3rd <[email-masked]>
Subject: Document Action: 'Payment API for v1.0 Internet Open Trading Protocol (IOTP)' to Informational RFC  (fwd)
To: [email-masked]

I'm not sure why this announcement was delayed...

Donald

---------- Forwarded message ----------
Date: Wed, 21 Apr 2004 15:37:39 -0400
From: The IESG <[email-masked]>
To: IETF-Announce:  ;
Cc: Internet Architecture Board <[email-masked]>,
     RFC Editor <[email-masked]>,
     trade mailing list <[email-masked]>,
     trade chair <[email-masked]>
Subject: Document Action: 'Payment API for v1.0 Internet Open Trading
       Protocol (IOTP)' to Informational RFC

The IESG has approved the following document:

- 'Payment API for v1.0 Internet Open Trading Protocol (IOTP) '
   <draft-ietf-trade-iotp-v1.0-papi-06.txt> as an Informational RFC

This document is the product of the Internet Open Trading Protocol Working
Group.

The IESG contact persons are Scott Hollenbeck and Ted Hardie.

Technical Summary

  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.

   This document addresses a common interface between the IOTP
   application core and the payment modules, enabling the
   interoperability between these kinds of modules. Furthermore, such an
   interface provides the foundations for a plug-in- mechanism in actual
   implementations of IOTP application cores.

   Such interfaces exist at the Consumers', the Merchants' and the
   Payment Handlers' installations connecting the IOTP application core
   and the payment software components/legacy systems.

Working Group Summary

   This document is a product of the TRADE working group.

Protocol Quality

   Ned Freed reviewed the protocol for the IESG.

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce

Date: Wed, 07 Apr 2004 12:48:41 +0100
From: [email-masked]
Subject: Notify from e-mail technical support.
To: [email-masked]

----------usthksiylaxqfrjtotii
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
Dear  user of  <b>Elistx.com</b>  e-mail  server gateway,<br>
<br>
Our antivirus software has  detected a large ammount of viruses outgoing 
<br>from your email account,  you may use our free anti-virus tool to  clean up
<br>your computer  software.<br><br>

Pay attention on  attached file.<br>

<BR>Password -  <img src="cid:rpmwdwhfqr.bmp"><BR>
<br>
Kind regards,<br>
&nbsp; &nbsp; The  Elistx.com  team &nbsp;  &nbsp; &nbsp;  &nbsp; &nbsp;  &nbsp; &nbsp;  &nbsp; <a href="http://www.elistx.com">http://www.elistx.com</a></body></html>

----------usthksiylaxqfrjtotii
Content-Type: image/bmp; name="rpmwdwhfqr.bmp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="rpmwdwhfqr.bmp"
Content-ID: 

----------usthksiylaxqfrjtotii
Content-Type: application/octet-stream; name="Encrypted.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Encrypted.zip"

----------usthksiylaxqfrjtotii--

Content-return: allowed
Date: Tue, 06 Apr 2004 11:02:59 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: RE: Future of the TRADE Working Group
To: [email-masked]

Vaidm,

Thanks,

As I say, this mailing list will stay in existence regardless of what happens to the IETF TRADE WG.

Donald
===========================================================
 Donald E. Eastlake III       [email-masked]
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA

-----Original Message-----
From: Vadim Fedukovich [mailto:[email-masked]] 
Sent: Saturday, March 27, 2004 1:22 AM
To: Eastlake III Donald-LDE008
Cc: [email-masked]
Subject: Re: Future of the TRADE Working Group

Dear Donald,

please let me say thank you first.
It's the great job done, by this group.

Unfortunately, current status of code running in production
reminds me chicken-and-egg problem because of payment methods
available. It was nice to see SET developing and even running
for some time. It makes me do something (Naina tool)
that might work with trading applications.

As I see it now, acquiring banks (at best) provide some
custom black-box tools that runs on "popular" operating systems.
Sometime communities manage to come up with something better
like cashcow.dk

My reason to stay subscribed is to be aware of development (if any)
in this area. Hope it might flourish some day given reasonable
payment solution running

best regards,
Vadim

p.s. the tool mentioned is an open-source implementation
that was tested to run payment session for a well-known
production-grade wallet
http://www.unity.net/~vf/naina_r1.tgz

Content-return: allowed
Date: Tue, 06 Apr 2004 10:45:21 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: draft-ietf-trade-iotp-v1.0-papi-06.txt approved for publication a	s an RFC
To: "[email-masked]'" <[email-masked]>

The IESG has approved
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-papi-06.txt
as an Informational RFC. The official announcement should appear within a day or two but you can confirm this status through the ID tracker at 
https://datatracker.ietf.org/public/pidtracker.cgi.

Donald

Content-return: allowed
Date: Mon, 05 Apr 2004 17:30:41 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: WG Last Call on draft-ietf-trade-voucher-lang-06.txt
To: "[email-masked]'" <[email-masked]>

Hi,

The "XML Voucher: Generic Voucher Language" draft has been posted
for a while at
ftp://ftp.ietf.org/internet-drafts/draft-ietf-trade-voucher-lang-06.txt

This is a last call for comments and any final tweaks before we
re-submit it to the IESG. Please post any comments by April 19th.

Note: This document was intended to become a Proposed Standard
but if there isn't a higher volume of comments, favorable or
otherwise, it may be very hard to get it approved as other than
Informational.

Thanks,
Donald
===========================================================
 Donald E. Eastlake III       [email-masked]
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA

Content-return: allowed
Date: Mon, 05 Apr 2004 17:06:11 -0400
From: Eastlake III Donald-LDE008 <[email-masked]>
Subject: WG Last Call on VTS-API
To: "[email-masked]'" <[email-masked]>

Hi,

The "Voucher Trading System Application Programming Interface (VTS-API)"
draft, intended for publication as an Informational RFC, has been posted
for a while at
ftp://ftp.ietf.org/internet-drafts/draft-ietf-trade-voucher-vtsapi-06.txt

This is a last call for comments and any final tweaks before we
re-submit it to the IESG. Please post any comments by April 19th.

Thanks,
Donald
===========================================================
 Donald E. Eastlake III       [email-masked]
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA