W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

RE: Draft registration of application/soap+xml

From: David Orchard <david.orchard@bea.com>
Date: Thu, 10 Jan 2002 17:18:04 -0800
To: "'Rich Salz'" <rsalz@zolera.com>
Cc: "'Mark Baker'" <distobj@acm.org>, <xml-dist-app@w3.org>
Message-ID: <01ba01c19a3d$d21e53d0$180ba8c0@beasys.com>
I'm not sure what the right way to design this would be.  You could encrypt
the entire header element.  Then when it's decrypted, whoever decrypted it
could see the actor, plus whatever else is in the header.  Unless we allow
nested encryption, which makes my brain hurt even more.

I see a rat's nest ahead as we tumble down the slippery slope.

I really believe we need more use cases on these various types.  Oh wait,
I'm supposed to write use cases.

Cheers,
Dave

> -----Original Message-----
> From: xml-dist-app-request@w3.org
> [mailto:xml-dist-app-request@w3.org]On
> Behalf Of Rich Salz
> Sent: Thursday, January 10, 2002 4:26 PM
> To: David Orchard
> Cc: 'Mark Baker'; xml-dist-app@w3.org
> Subject: Re: Draft registration of application/soap+xml
>
>
> The entire header element can be encrypted, including the actor?
> 	/r$
> --
> Zolera Systems, Securing web services (XML, SOAP, Signatures,
> Encryption)
> http://www.zolera.com
>
Received on Thursday, 10 January 2002 20:21:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT