Re: [ogpx] verbiage : domain, agent domain, region domain, trust domain , service, etc.

[Meadhbh Hamrick <[e-mail]>]

if you're saying "we shouldn't dictate how services are deployed" then
you're missing the point of a domain.

a domain is an abstraction which represents characteristics of a
collection of machines that are operating in concert to provide a
service. some of these characteristics are:

  * what service does the domain provide?
  * what end entities on the network does it trust?
  * which are trusted by it?
  * who is the responsible party for the domain?

there is nothing in the definition of a domain that REQUIRES a domain
to deploy services in any way. just because you deploy an
authentication service in a domain, it does not mean that you MUST
deploy a group IM service; or that if you do provide a capability for
a group IM service that it be deployed in the same domain.

in the context of user authentication, the term "agent domain" is used
to describe the collection of network hosts that share trust
characteristics with the host that responds to the request. we could,
when talking about this use case, instead say, "the hosts that share
trust characteristics with the host that implements the authentication
service," but this is a much more unwieldy term.

so if you wanted to operate a grid like the linden grid, then the
hosts that respond to auth, IM, inventory requests would be in a
linden agent domain. if you wanted to operate a tourist instance, then
the agent domain would be the group of machines operated by the person
responsible for granting access to the instance.
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * [e-mail]