The client or server can simply "not care".
The core is not having services executed on content (sending or recieving)
that is NOT wanted!! This is the idea of having our rule based
system were these wishes can be expressed from either end
and the policy will be allow for non-delivery/service to be
given if there is conflict.
At 11:57 AM 6/21/2001 -0400, Markus Hofmann wrote:
>Brian,
>
> > Because both the content originator and the content receiver should be
> > able to veto (say) ad insertion.
>
>What about services that are executed only on behalf of the content
>receiver? Virus scanning might be one example.
>
>Other examples might be services that are authorized and performed on
>the REQUEST issued by the content receiver (as opposed to the CONTENT
>itself). Here, it seems sufficient if only the content receiver
>authorizes the service.
>
>-Markus
Michael W. Condry
Director, Network Edge Technology
