Re: Use of multipart/encrypted with S/MIME

We will be using the standard pkcs-7/encrypted form from
smime.....whoever we will be using as the smime spec say the multipart
signed as our many structure for signature....by  doing this the
receipent can read a signed message if they do not have smime.....hope
that helps....

Karen Rosenthal wrote:
> 
> +----------------------------------------------------------------------+
> This message was addressed to:  edipilot <at> lists.commerce.net
> +----------------------------------------------------------------------+
> 
> I am looking for some clarification on the (intended?) use of the
> multipart/encrypted Content-Type with S/MIME.
> 
> It is my understanding from the edipilot conference call this past
> Wednesday, that rather than supporting directed adherence to the S/MIME
> v2 specification (using application/x-pkcs7-mime body parts), the ediint
> working group is suggesting adherence to RFC1847 (Security Multiparts
> for MIME - Multipart/Signed and Multipart/Encrypted).  (If I am mistaken
> here, please let me know!)
> 
> The usage of multipart/signed is well detailed in the S/MIME v2
> specification, but use of multipart/encrypted is not mentioned, nor is
> it accounted for in design.  So for a vendor that supports S/MIME, but
> not PGP or MOSS, what should be used for the multipart/encrypted
> protocol, and what will the MIME message look like?
> 
> Regards,
> --
> Name:   Karen Rosenthal
> E-mail: karenr <at> premenos.com
> Phone:  (510)688-2928
> Fax:    (510)602-2133
> -------------------------------------------------------------------------
> This message was sent by a majordomo-based automatic list manager.
> Subscriptions to and archives of this list are available to CommerceNet
> members, partners, and invited guests.  For further information send a
> mail message to 'edipilot-request <at> lists.commerce.net' with 'help'
> (no quotations) contained in the body of your message.