[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [end points comm] OPES System
At 22:32 18/08/03, Markus Hofmann wrote:
please stop confusing system and domains!
Not sure wheher I'm the one who's confusing things...
I refered to "OPES domain" as a collection of OPES entities operated by a
single carrier, while an "OPES system" is rather described by trust
boundaries. Depending on how we define tracing, we probably need only one
of the terms.
The OPES system is the system providing me/I organize to provide me a
service. I need to reference it. But I can have several OPES system
providing me the same service.
Each of theses OPES system can be actually built in using system bu
different operators with different responsibilities.
Example: My ISP provides me translating services of the web pages I access.
He calls on several services depending on the language: this is his
He also provide the same translation service for mail he names
Translate-mailSystem. These are two different systems and I need to
Now WEBTS uses different translation servers, so does Te-mS. One is BBC and
one is CNN. I does not like CNN, so I want to bar the CNN domain. As he
does not want to lose me my ISP accepts to trim the load and to permit me
to use BBC on both System but with a markup on Te-mS as it is a special
service. Now I may decide to degrade to CNN on option for low importance
mails. I obviously want to automate all that and be able to make
Now, CNN can come with a special deal: if I accept some delays they will
permit me to use some of their processors @ lower cost, etc....
The system is my/someone decided construct. Like an Airline System.
The domain is the processor owner accepted area of responsiblity? Like an
Now to know if this is runway 31 or runway 33, (identifiying each
processor) this may or not be of used and disclosed by the domain owner,
potentially to who they want (crypted).
Two totally different things.