Re: [ogpx] Fwd: VWRAP Draft Charter - 2009 09 01

[Joshua Bell <[e-mail]>]

Ah, I believe your point is clear now - there are policies that can be
enforced at a protocol level, and policies that cannot. Thanks for bringing
that up; it will be important to note so we don't make blanket statements.

I would point out that this occurs on both the agent side and region side,
just like access control; your agent domain may have a policy which states
"no kissing anyone with cooties"; the region domain you visit may allow such
hi-jinks, but the user would be violating the agent domain's policy by doing
so. This is also, presumably, unenforceable by protocol.

(One could imagine an extensible mechanism for machine-readable policy that
could be enforced by the domains, but us creative humans can always think of
examples that can't be encoded.)

On Thu, Oct 1, 2009 at 9:06 AM, Carlo Wood <[e-mail]> wrote:

> On Thu, Oct 01, 2009 at 02:16:42PM +0200, Vaughn Deluca wrote:
> > Its not clear to me what you mean Carlo. How does
> > "the RD making protocol-level policy decisions" differ from
> > "It is the destination (the region (domain) that the user is in) that
> > determines the ToS."
> >
> > Asume the RD is mature, and therefore states in its terms of service that
> any
> > agent present should be above 18.
> > An agent domain without age verification will be happy to TP its agents
> to that
> > RD
> > The RD will want to inform the AD its not going to happen.  In this
> example I
> > fail to see the destinction you mention above.
>
> Access restriction again...
>
> Take for example: some region demands that everyone is an alien of
> some sorts. Nobody can be rejected based on the AD they use, and no
> AD will refuse to teleport to the region either.
>
> Once there, the users must use an alien avatar. If they do not,
> then they break a local (region) rule and the administration of
> the region will want to warn/ban them. This is nothing to do
> with AD's, nor can VWRAP detect and enforce what avie you use.
>
> --
> Carlo Wood <[e-mail]>
> _______________________________________________
> ogpx mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ogpx
>