RE: Transport and packaging security standards?

[Dick Brooks <dick@8760.com>]

Scott,

All the security related verbiage was moved from the TRP spec to the
security spec, which Maryann Hondo mailto:mhondo@us.ibm.com is leading up.

Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

> -----Original Message-----
> From: Parnell, Scott [mailto:Scott.Parnell@usa.xerox.com]
> Sent: Friday, January 12, 2001 9:06 AM
> To: 'ebxml-transport@lists.ebxml.org'
> Subject: Transport and packaging security standards?
>
>
> Message-id:
>  <B08661D21F0FD311A21A00805FC7D6500154D5F5@usa0845ms1.svcdoc.mc.xerox.com>
> MIME-version: 1.0
> X-Mailer: Internet Mail Service (5.5.2650.21)
> Content-type: text/plain
> Content-transfer-encoding: 7BIT
> List-Owner: <mailto:ebxml-transport-help@lists.ebxml.org>
> List-Post: <mailto:ebxml-transport@lists.ebxml.org>
> List-Subscribe:
> <mailto:ebxml-transport-request@lists.ebxml.org?body=subscribe>
> List-Unsubscribe:
>  <mailto:ebxml-transport-request@lists.ebxml.org?body=unsubscribe>
> List-Archive: <http://lists.ebxml.org/archives/ebxml-transport>
> List-Help: <http://lists.ebxml.org/doc/email-manage.html>,
>  <mailto:ebxml-transport-request@lists.ebxml.org?body=help>
>
> I found this quote apparently originating from Dick Brooks:
>
> >- The ebXML packaging spec references S/MIME (RFC 2633) and PGP/MIME (RFC
> >2015) standards for encryption and digital signature and the ebXML header
> >spec references XML Dsig for more granular signature requirements than
> >provided by RFC 2633 and RFC 2015;
>
> at: http://lists.ebxml.org/archives/ebxml-awareness/200007/msg00010.html
>
> but when I couldn't find any reference to specific security mechanisms in
> the 0.8 release of the Transport, Routing, and Packaging spec. The closest
> reference I could find was to a document titled "ebXML Message Services
> Security Specification." and a comment that it is under
> development If this
> is where it will be defined, is there any outlook on when this
> document will
> be publically available?
>
> Regards,
> Scott