ietf-openproxy
[Top] [All Lists]

RE: Comparison of ICAP and SOAP

2001-07-10 12:56:34

As I noted, other devices may choose to fiddle with SOAP messages (as
with any other payload); however, they're not interposed by SOAP.
This 'failing' is perhaps why one of the first SOAP Modules submitted
was for XML digital signatures [2], and it's more than likely that it
will be joined by XML Encryption ASAP.

W3C's Digital Signature Rec wasn't ready yet when SOAP was published as a
W3C Note.  Digital Signature is almost to Rec now.  Encryption should follow
fairly soon.  I think this is a matter of layering, not a failure for one
spec to include everything.

-----Original Message-----
From: Mark Nottingham [mailto:mnot(_at_)akamai(_dot_)com]
Sent: Tuesday, July 10, 2001 10:34 AM
To: Carr, Wayne
Cc: Brian E Carpenter; Keith Moore; Tomlinson, Gary; Randy Bush; Lloyd
Wood; John Martin; ietf(_at_)ietf(_dot_)org; ietf-openproxy(_at_)imc(_dot_)org
Subject: Re: Comparison of ICAP and SOAP



Wayne,

On Tue, Jul 10, 2001 at 10:13:21AM -0700, Carr, Wayne wrote:
SOAP intermediaries don't have to be explicitly targetted. 
Anything along the way could read and act on a soap message.  If
you do use the soap actor attribute, how you use it is very
flexible.  You can ask the next node to act on it.  You can use a
uri that indicates a specific node or you can use a URI that
indicates some action you want and you don't care who does it.

What you describe isn't a SOAP intermediary by the WG's definition -
see [1]. Of course the actor which nominiates the intermediary
doesn't have to be tied to the network identity of that node; my
point was that there must be an explicit targetting of the block for
a SOAP intermediary to be able to process it.

As I noted, other devices may choose to fiddle with SOAP messages (as
with any other payload); however, they're not interposed by SOAP.
This 'failing' is perhaps why one of the first SOAP Modules submitted
was for XML digital signatures [2], and it's more than likely that it
will be joined by XML Encryption ASAP.

Cheers,

[1]  http://www.w3.org/TR/2001/WD-soap12-20010709/#_Toc478382082
[2]  http://www.w3.org/TR/SOAP-dsig/


-- 
Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)



<Prev in Thread] Current Thread [Next in Thread>