The 'explicitly addressed' was added to explicitly address your concerns
that the IP addressing model might be violated. Now you appear to
be getting at application level addressing or 'targeting' (what do mean
by 'arbitrary content'?). The security model can encompass delegation
within the message to any degree of specificity, but it seems to me
that classes of delegation are the most useful principals - 'proxy',
'surrogate', 'edge proxy'.
For most publishers, these delegations, if required, likely will be added
by reverse proxies that modify content based on pattern matching.
Hilarie
Mark Nottingham <mnot(_at_)akamai(_dot_)com> 07/10/01 10:59AM >>>
On Tue, Jul 10, 2001 at 09:39:17AM -0700, Michael W. Condry wrote:
At 09:09 AM 7/10/2001 -0700, Mark Nottingham wrote:
SOAP intermediaries must be explicitly targetted by the message
(using the 'actor' attribute). In this respect, they are completely
unlike the OPES model.
The charter says the intermediaries are explicitly addressed. I am
a bit confused by your comment.
Does the charter state that they will be targetted by an in-message
mechanism (e.g., HTTP response header, arbitrary message content,
etc.)?
--
Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)