OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: S/MIME


The technical report http://www.ebxml.org/specs/secRISK.pdf contains
examples of how to specify S/MIME encryption and S/MIME signature
packaging using the Packaging element defined in the CPP/A spec.

See line 1051 S/MIME profile for application encryption of payload
and line 1076 S/MIME profile for application signing of payload.

(There's probably a bug on line 1065 as it references a part named
payload that's not defined within the enclosing Packaging element.)


-----Original Message-----
From: Dan Weinreb <dlw@exceloncorp.com>
To: david@drummondgroup.com <david@drummondgroup.com>
Cc: dmoberg@cyclonecommerce.com <dmoberg@cyclonecommerce.com>;
ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Date: Friday, August 17, 2001 10:17 AM
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
>   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
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC