RE: S/MIME

[David Fischer <david@drummondgroup.com>]

Agreed, my only concern is that S/MIME has an impact on Manifest.  Off the top
of my head I can't think of any other payload which would do this (maybe
compression?).

What if the entire envelope were S/MIME encrypted?  I expect someone will try
this and I don't see anything intrinsically wrong with it nor do I see anything
in the spec which would prohibit something like this.

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Dan Weinreb [mailto:dlw@exceloncorp.com]
Sent: Friday, August 17, 2001 12:15 PM
To: david@drummondgroup.com
Cc: dmoberg@cyclonecommerce.com; ebxml-msg@lists.oasis-open.org
Subject: Re: S/MIME


   Date: Fri, 17 Aug 2001 09:24:14 -0500
   From: David Fischer <david@drummondgroup.com>

	   Since SMIME is in the payload, we should probably support it
   indefinitely -- its just another payload (which unfortunately impacts the
   Manifest).

But isn't this addressed by what Chris Ferris said in earlier mail:

  The ebMS spec doesn't say anything about the payload intentionally.
  The reference to S/MIME means that the payload, not the overall
  "envelope" can be S/MIME encrypted.

As for the CPP/A, it's possible that (I don't know enough about S/MIME
yet) nothing new is needed; maybe you can express S/MIME encryption
just by putting in the appropriate Packaging/CompositeList/Encapsulation
element.

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>