Re: [mmox] 3-world OGP interop scenario

On Thu, Mar 12, 2009 at 5:05 PM, Rob Lanphier <robla@lindenlab.com> wrote:

>
> Yes, one can assume client A can talk to servers B and C if we actually go
> about the work of defining a standard client-server protocol spelling out
> how the client is expected to behave in that transaction.
>
>
>
That sounds very reasonable to me Rob.  It is after all the job of protocol
makers to define means of machine interaction for pathways that may not have
existed before.

I would go further and say that this is even compatible with Jon's models,
given a willingness to be flexible.  Current OLIVE clients may not be able
to talk to other systems, but this is no bar to new clients of OLIVE being
able to do so.

In particular, the open source community is very good at capturing existing
network protocols and building them into new libraries and applications, so
an OLIVE client that works with more than just OLIVE could certainly be
envisaged.  All it would take is one open source developer who also uses
OLIVE to feel the need and be willing to scratch it.  Whether the OLIVE
organization would allow this or not is immaterial to us here --- we are in
the business of defining mechanisms, not policies.

And there are other solutions as well.  Nothing precludes OLIVE servers from
performing the role of a client in an OGP endpoint.  Some detailed analysis
of inbuilt assumptions would be required to be sure that this can work, but
in principle an OLIVE (or LESS) server could obtain all the necessary data
in this way from which to build a local simulation for its clients.

Morgaine.

On Thu, Mar 12, 2009 at 5:05 PM, Rob Lanphier <robla@lindenlab.com> wrote:

> On 3/12/09 9:13 AM, Jon Watte wrote:
> > For example, the assumption that client A can even talk to servers B
> > and C seems to be totally implicit, but can't be assumed in the
> > general world.
>
> Yes, one can assume client A can talk to servers B and C if we actually
> go about the work of defining a standard client-server protocol spelling
> out how the client is expected to behave in that transaction.
>
> Rob
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>