Update

We have taken comments on draft 3 (currently posted) and have produced
draft 04. The primary changes are in two areas:

- Some wordsmithing related to non-repudiation

- Added an XML payload example. This has actually been a hot issue in that
our original intent was to define a protocol that was completely payload
independent. That being said, we went ahead and produced a section
describing how a XML DTD and data would be encapsulated and transported in
an SCMP message. We have struck a compromise in that we illustrated how an
XML message would be delivered, not defining any type of message taxonomy.
Groups like Rosetta Net, CompTIA, DISA, EDIInt, IOTP, OBI, and others using
private protocols are responsible for providing actual message definition.

Our intent and belief is that this version is ready to become an
Informational RFC. Once I receive confirmation that the draft has been
posted, I'll notify the list.



Thomas A. Arnold                                CyberSource Corporation
Chief Technical Officer                         550 S. Winchester Bl. #301
                                                San Jose, CA 95128
[email protected]                            Direct: 1.408.260.6010
http://www.cybersource.com/                     Main: 1.408.556.9100
---------------------------------------------------------------------------
This Email and any attached files are confidential and may also be 
privileged. It is intended only for the individual or entity to whom 
it is addressed. If you are not the recipient or an authorized agent 
of the recipient, you are hereby notified that any use, dissemination, 
distribution or copying of this communication is strictly prohibited. 
If you have received this message in error, please contact CyberSource 
Corporation immediately at (408) 556-9100.

Thank you.