RE: headers - rfc2706

[David Burdett <david.burdett@commerceone.com>]

ECML adresses a slightly different space to IOTP.

ECML aims to provide information hidden inside an HTML page that can be used
by software running on the browser to populate fields required for credit
card payment such as credit card no, card holder, etc from data previously
entered by the user.

There is also the idea that the one of the hidden fields could be used to
indicate whether the Merchant supports protocols such as SET or IOTP. In
this case, this could be used to initiate the appropriate SET, IOTP, etc
software at the browser.

As far as the names in ECML and IOTP are concerned, they are similar but not
the same and mappings between the two are easy. Since version 1.0 of the
IOTP spec has just been finalized I doubt they will be aligned in the short
term (that's why we need a core components group !!). Although in later
versions this is quite possible.

I also don't think that there is anything in the ECML specification that is
relevant to the work of the TP&R group since there no fields that
conventionally could be described as "message headers".

Regards

Davidh

-----Original Message-----
From: Dick Brooks [mailto:dick@8760.com]
Sent: Friday, February 11, 2000 12:41 PM
To: Rik Drummond; Ebxml Transport
Subject: RE: headers - rfc2706


Rik, when I attended the ECML session at the last IETF meeting in Washington
the consensus was that ECML's header information related closely to IOTP's
header info and should be aligned with that effort. Perhaps Dave knows if
the ECML names are being sync'd with IOTP.

Dick


-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of Rik
Drummond
Sent: Thursday, February 10, 2000 11:24 PM
To: Ebxml Transport
Subject: headers - rfc2706


  john is this some of the work from ibm you referenced? best regards, rik

 rfc2706