From: dptom(_at_)cybersource(_dot_)com (Tom Arnold)
The SCMP message content (referred to as message payload) is not
intended to be defined or specified.
The only specification about the payload is that it be identified to
the receiver utilizing a naming convention similar to standard MIME
naming and formatting [MIME] is used to identify the type of payload
contained in the SCMP data area.
Tom,
It would be helpful if you described the manner in which the S/MIME WG
charter would need to be modified to accommmodate SCMP. We all hope and
expect that S/MIME will be useful and used for carrying all types of
protected content, including commerce messages in standard or proprietary
transaction formats.
But if you are not intending to specify the content format, and the
existing CMS specification allows any content type (treats encapsulated
content as an opaque blob), what more needs to be done in this WG?
And instead of using a naming format "similar to standard MIME", why
not just define real standard MIME types for commerce data objects,
enabling SCMP messages to be carried by any MIME software?
I haven't seen the entire SCMP draft, but it seems that this basic
statement of purpose should appear in the abstract.
Dave Kemp