ietf-openproxy
[Top] [All Lists]

Re: Callout (was Re: WG Last Call: draft-ietf-opes-architecture-00

2002-05-22 15:23:15

At 1:12 PM -0400 5/22/02, Mark Baker wrote:
On Wed, May 22, 2002 at 09:18:25AM -0700, Marshall Rose wrote:
> mark - the reason that callout is in the architecture is because we standardize a callout protocol. if we didn't care to have the protocol standardized, then you and i are in agreement; however, everyone i talk to in this space tells me that a standardized callout protocol is a real-world requirement. so, there you have it.

Thanks, that explains why it's in the document.  I just don't get why
people think one is needed.

If it's "obvious" to so many here, then I'll just save my breath for the
callout requirements gathering phase.

MB
--

I would add an additional reason to address callouts. As I read it, the potential privacy implications of the use of callouts was one of the concerns addressed by the IAB. When the IAB wrote as a consideration:

   (5.1) Privacy: The overall OPES framework must provide for mechanisms
   for end users to determine the privacy policies of OPES
   intermediaries.

I think this means that the end user must be able to evaluate the privacy policies of any callout entity as well as as any OPES dispatcher. Thus, the OPES architecture needs to anticipate the existance of OPES callouts.

John

--------------------------------------------------
John Morris // CDT // http://www.cdt.org/standards
--------------------------------------------------

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