At 19:57 13/08/03, Alex Rousskov wrote:
On Tue, 12 Aug 2003, Markus Hofmann wrote:
Here is where I would start:
OPES system: OPES system is a set of OPES entities
defined for a given application message. The formation of an
OPES system is recursive: OPES system starts with either data
provider or data consumer (for the given message); OPES system
then includes any OPES entity trusted by (accepting authority
from) an entity already in the OPES system. The trust and
authority delegation is viewed in the context of the given
application message. As implied by the above definition, some
OPES entities in the system may not participate in the
processing of a given message.
OK for that definition with two provisions:
1. the recursiveness makes it potentially an illimited ectoplasm what I
accept in principle if you read Open in that sense.
Nevertheless I prefer my own approach of saying that a system is organized
by someone because of the differences in the system, usage and awareness
depending on who organize it. This permits me to qualify as a boarderless
system as most probably a structural bug?
2. I maintain the important interest of the notion of domain as belonging
to an operator. Because of the practical influence in terms of rates,
contracts, security, qos, etc. Sub-domains should be alluded to to show
that what count is the parameter decided by an authority.
jfc
Or we can use the "coloring" trick from
draft-ietf-opes-architecture-04. Just make sure that the end
(provider/consumer) is included in the OPES domain/system and that the
definition is based on a given message.
The above definition puts both Disney and Akamai into one OPES system,
for a given application message they may process. Moreover, if Disney
uses both Akamai and Mirror Image (or whatever) for content
distribution, the distinction would be made on a per-message
(per-content) basis, which is the right thing to do because Akamai and
Mirror Image do not necessarily belong to the same OPES domain/system.
Alex.
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.507 / Virus Database: 304 - Release Date: 04/08/03