Subject: RE: Transport and packaging security standards?
Scott, All the security related verbiage was moved from the TRP spec to the security spec, which Maryann Hondo mailto:email@example.com is leading up. Dick Brooks Group 8760 110 12th Street North Birmingham, AL 35203 firstname.lastname@example.org 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: 'email@example.com' > 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:firstname.lastname@example.org> > List-Post: <mailto:email@example.com> > List-Subscribe: > <mailto:firstname.lastname@example.org?body=subscribe> > List-Unsubscribe: > <mailto:email@example.com?body=unsubscribe> > List-Archive: <http://lists.ebxml.org/archives/ebxml-transport> > List-Help: <http://lists.ebxml.org/doc/email-manage.html>, > <mailto:firstname.lastname@example.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
Powered by eList eXpress LLC