1. Referring to the "coloring schema" proposed in part 3.1
I'd suggest to limit notification requests by the area
of the requesting party color. If the company or school
administrator stops sport news and banner ads he/she has
full right to do so - and has no obligation to report
internal network settings nor to news media nor to
advertisers.
Attempt to mandate otherwise will just result in
limiting OPES applicability area or in proprietary
modifications that may be more dangerous to security
and privacy than controlled standardized provisions.
2. "Coloring schema": I see a problem in starting
authority propagation from the data consumer or initial
data provider.
In company/school/library case final data consumer has
no authority, in CDN case authority is delegated to
the CDN distribution points.
I'd suggest to have a separate "start of authority"
points for the color propagation.
Oskar
-----Original Message-----
From: owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org]On Behalf Of
Markus Hofmann
Sent: Thursday, May 23, 2002 12:09 PM
To: John Morris
Cc: OPES Group
Subject: Re: [ OPES architecture] Final Points of Discussion: Tracing
John Morris wrote:
Unless I've missed something (which is certainly possible), the draft
may want to suggest how the OPES architecture will respond to the
following IAB consideration:
(3.1) Notification: The overall OPES framework needs to assist
content providers in detecting and responding to client-centric
actions by OPES intermediaries that are deemed inappropriate by the
content provider.
Section 2.6 of the draft should extend to include some form of
notification of the OPES action to the originating party *when
requested* by the originating party. Implicit notification mechanisms
would not scale, but a content provider should be able to explicitly
request notification in some form.
......................
-Markus