On Mon, 18 Aug 2003, jfcm wrote:
At 19:41 18/08/03, Alex Rousskov wrote:
On Fri, 15 Aug 2003, jfcm wrote:
I name an OPES domain the area of reponsibility of an operator.
What's an operator or operator responsibility? When Disney-owned
content is created on and made available via Akamai servers, is Disney
an operator? Is Akamai? Is Disney+Akamai?
This is where you are confusing the issues by pleasure.
The responsible operator is the one saying he is responsible.
Stick to your airline image and do not make too many layer violation.
NO processor should be without domain operator. And no processor can be
with two separate domain owner. Otherwise I will/people will _NEVER_
trust.use an OPES.
This means that every processor MUST be something and that something
is to be decided by its operator. And as a SYSTEM user I must be
able to say/decide if I trust or not an operator for who he is or
for the information he discloses or for the cost of his services.
That's fine, but you need a better definition of a domain and/or
operator. The original "OPES domain is the area of reponsibility of an
operator" does not imply the above explanation.
Also, since you leave domain boundaries for the operator to decide,
you need to explain how conflicts (two operators think they are
responsible for the same domain and instruct their processors to
update the trace accordingly) and misses (no operator claims
responsibility for a domain/processor).
Alex.