Difference between revisions of "MMOX"

From Second Life Wiki
Jump to navigation Jump to search
 
(25 intermediate revisions by 2 users not shown)
Line 72: Line 72:
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-lentczner-ogp-base-00.txt Open Grid Protocol: Foundation] -- Aka. "OGP Base"
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-lentczner-ogp-base-00.txt Open Grid Protocol: Foundation] -- Aka. "OGP Base"
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-hamrick-ogp-auth-00.txt Open Grid Protocol: Authentication] -- Aka. "OGP Auth"
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-hamrick-ogp-auth-00.txt Open Grid Protocol: Authentication] -- Aka. "OGP Auth"
* '''MMOX Informational IETF draft:''' [http://www.ietf.org/proceedings/staging/draft-wolf-vp-identity-00.txt Virtual Presence Identity] -- Aka. "Welbin VPI"
* '''MMOX Informational IETF draft:''' [http://www.ietf.org/proceedings/staging/draft-wolf-vp-identity-00.txt Virtual Presence Identity] -- Aka. "Weblin VPI"
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-cscholz-mmox-architecture-00.txt MMOX Architecture Discussion] -- Problem spaces and architectures
* '''MMOX Protocol IETF draft:''' [http://www.ietf.org/internet-drafts/draft-cscholz-mmox-architecture-00.txt MMOX Architecture Discussion] -- Problem spaces and architectures
* '''MMOX Informational IETF draft:''' [http://tools.ietf.org/id/draft-jwatte-mmox-use-cases-00.txt MMOX Use Cases] -- JWatte on Use Cases
* '''MMOX Informational IETF draft:''' [http://tools.ietf.org/id/draft-jwatte-mmox-use-cases-00.txt MMOX Use Cases] -- JWatte on Use Cases
== Post-BoF Proposals and Materials ==
* ''Proposal'': [http://www.meerkatviewer.org/whitepaper.pdf Loosely Coupled Virtual Worlds] -- client-centric approach to interop, OGP-compatible


== Highlighted contributions ==
== Highlighted contributions ==
Line 85: Line 88:
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00657.html MMOX List moderator and participation info] -- clear statement by AD on participation
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00657.html MMOX List moderator and participation info] -- clear statement by AD on participation
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00627.html Taxonomy of topics] -- statement by Infinity that the intention of MMOX was to create an OGP standard
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00627.html Taxonomy of topics] -- statement by Infinity that the intention of MMOX was to create an OGP standard
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00724.html Taxonomy of topics, thread] -- examination of the implications of Infinity's post
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00724.html Taxonomy of topics, thread] -- examination of the implications of Infinity's post / group split
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00823.html Chartering for requirements only] -- follow up on the proposal for MMOX + OGP group split
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00923.html MMOX Progress Tracking] -- review of recent draft-centered activity @ 2009-Mar-4
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00923.html MMOX Progress Tracking] -- review of recent draft-centered activity @ 2009-Mar-4
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01016.html Debunking "Universal Client"] -- also explains why generic clients are completely inevitable
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01016.html Debunking "Universal Client"] -- also explains why generic clients are completely inevitable
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01053.html Managing model mismatches] -- methods for achieving interop despite model mismatches
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01053.html Managing model mismatches] -- methods for achieving interop despite model mismatches
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01067.html Scalability considerations / BCP95, BCP22] -- IETF statements on scalability, relevance to MMOX
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01114.html 3-world OGP interop scenario] -- description of an OGP-based interop scenario over 3 virtual worlds
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01114.html 3-world OGP interop scenario] -- description of an OGP-based interop scenario over 3 virtual worlds
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01193.html Creating walled gardens considered harmful] -- A plea to avoid totally non-interoperating segmentation under MMOX
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01208.html Decomposition of ''teleport'' into its essential components] -- details how ''teleport'' is applicable to all VWs
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01193.html Creating walled gardens considered harmful] -- a plea to avoid non-interop segmentation under MMOX
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01234.html James Kempf's horrifying (but entirely plausible) scenario] -- [http://www.ietf.org/mail-archive/web/mmox/current/msg01235.html should we abandon MMOX?]
* [https://lists.berlios.de/pipermail/opensim-dev/2009-March/005567.html "I don't know what OGP is", by Diva Canto] -- eye opening post from key Opensim developer


== Requirements tracking ==
== Requirements tracking ==
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00982.html Unifying object execution model] -- requirement to support both local and remote execution models
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00982.html Unifying object execution models] -- requirement to support both local and remote execution models
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00984.html Exposing regions] -- requirement that exposing implementation of regions not be mandatory
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00984.html Exposing regions] -- requirement that exposing implementation of regions not be mandatory
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01020.html Avatar diversity] -- requirement for transport of avatar visual information between virtual worlds
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01020.html Avatar diversity] -- requirement for transport of avatar visual information between virtual worlds
Line 99: Line 107:
* [http://www.ietf.org/rfc/rfc3935.txt A Mission Statement for the IETF] -- requirement for scalability, wide deployment, interoperation
* [http://www.ietf.org/rfc/rfc3935.txt A Mission Statement for the IETF] -- requirement for scalability, wide deployment, interoperation
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00850.html Interop Metrics and MMOX Goals] -- quantifying the interoperability requirement as a metric
* [http://www.ietf.org/mail-archive/web/mmox/current/msg00850.html Interop Metrics and MMOX Goals] -- quantifying the interoperability requirement as a metric
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01307.html Trust Agreements vs Secure Data Transfer], [http://www.ietf.org/mail-archive/web/mmox/current/msg01292.html prev] -- replacing security theater by actual security
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01243.html Decoupling Asset Storage] -- asset storage/inventory needs to reflect the diverse origins of objects
* [http://www.ietf.org/mail-archive/web/mmox/current/msg01171.html Basic region requirement to support portals] -- this also allows [http://www.ietf.org/mail-archive/web/mmox/current/msg01174.html user-defined region adjacency]


== IETF Information ==
== IETF Information ==
Line 143: Line 154:
* [http://www.secondlife.com/ Second Life] Largest current VW, Linden Lab + IBM founded MMOX
* [http://www.secondlife.com/ Second Life] Largest current VW, Linden Lab + IBM founded MMOX
* [http://www.solipsis.org/ Solipsis] -- P2P virtual world, contact active in AW Groupies
* [http://www.solipsis.org/ Solipsis] -- P2P virtual world, contact active in AW Groupies
* [http://www.weblin.com/ Weblin] -- Web-based avatar-oriented chat world, [http://www.ietf.org/proceedings/staging/draft-wolf-vp-identity-00.txt IETF draft], contact active in MMOX


== MMOX Chairs and IETF Contacts ==
== MMOX Chairs and IETF Contacts ==

Latest revision as of 16:15, 20 August 2009

"MMOX is an effort to collect best practices and develop consensus based standards for virtual world and MMO interoperability. The mmox@ietf.org mailing list is for technical discussions related to this objective and for coordinating administrative details of upcoming meetings." -- IETF MMOX listinfo


This page is intended as a useful container for gathering together links to MMOX resources.

Please expand it with other relevant links that could be helpful. (Don't lose any links. :P)


MMOX mailing list and other communications

Please note that all communications performed under the aegis of an IETF workgroup (this includes IETF email and Jabber) are logged and are permanently visible to the public. They are also considered "IETF Contributions", and as such are subject to the IETF rules on IPR Disclosure. Please read the relevant documents in the IETF Information section below to know what this means.

IETF Jabber Chat logs

MMOX In-World Chat logs

Note that only "special" transcripts which include non-SL/Opensim participants are linked here.

Links to the weekly SL+Opensim chat logs are maintained under AW Groupies Chat Logs.

  • February
19

Official IETF74 BoF materials

IETF74 and MMOX BoF Communication resources

MMOX drafts and working documents

MMOX Workgroup Charter Drafts

MMOX LLSD Drafts

MMOX Protocol Proposals and MMOX IETF Draft Protocols

In order of appearance on MMOX list: (Note that there is no current working name for an extensible MMOX Protocol).

Post-BoF Proposals and Materials

Highlighted contributions

Unavoidably, these reflect personal interests, but feel free to add your own to the set.

Requirements tracking

IETF Information

Virtual worlds with known/expected interest in interop

In alphabetic order:

MMOX Chairs and IETF Contacts

The contact addresses given here are those already made public here.

Other relevant resources