[mmox] Scalability considerations / BCP95, BCP22

Morgaine <morgaine.dinova@googlemail.com> Mon, 09 March 2009 10:42 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Z9Z//2WT89w7Bx4WoQdmHbIRLIjOOZOJlde+sZFOcC8DNrGJlRg6jPPTEIRdMxkHlj n0zZo2HWVeyurUWs3MqTdqJN2Knd9FkafGR/7zechI77Wbu93U9v+0G8/y/tltsdm8ma SExWv5vXgTZiQIUTuMuvL8zHWdEKG33Cev7yM=
MIME-Version: 1.0
Date: Mon, 09 Mar 2009 10:42:34 +0000
Message-ID: <e0b04bba0903090342k292a919bw23e4589eba043797@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: MMOX-IETF <mmox@ietf.org>
Content-Type: multipart/alternative; boundary="0015174c1778d227740464ad4a23"
Subject: [mmox] Scalability considerations / BCP95, BCP22
Precedence: list

As the term "*Massively Multi-Participant*" in *MM*OX suggests, scalability
is one of the primary destinations along the interop road that we have begun
to tread.  Indeed, interop and scalability cannot be divorced, since both
are strongly tied to the growth of the VW universe and are in turn affected
by it.

Scalability is one of my personal areas of interest, both here and
previously in the AWG group of Second Life, and I expect to devote much time
to issues of scalability in MMOX protocols as they arise in the forthcoming
months.  To kick off this aspect of our work, I would like to highlight the
IETF's own special interest in scalability.

Most vividly, scalability forms part of the IETF Mission Statement
(BCP95/RFC3935) <http://www.ietf.org/rfc/rfc3935.txt>:

*In attempting to resolve the question of the IETF's scope, perhaps the
fairest balance is struck by this formulation: "protocols and practices for
which secure and scalable implementations are expected to have wide
deployment and interoperation on the Internet, or to form part of the
infrastructure of the Internet."*

Underlining further the importance of scalability within the Best Current
Practice for IETF standards, <http://tools.ietf.org/html/bcp22>
BCP22/RFC2360 <http://tools.ietf.org/html/rfc2360>'s Guide for Internet
Standards Writers makes this pertinent recommendation:

*2.15  Scalability Considerations

The standard should establish the limitations on the scale of use, e.g.,
tens of millions of sessions, gigabits per second, etc., and establish
limits on the resources used, e.g., round trip time, computing resources,
etc.  This is important because it establishes the ability of the network to
accommodate the number of users and the complexity of their relations.  The
STD 53/RFC 1939 has an example of such a section.  If this is not applicable
to the protocol, an explanation of why not should be included.*


This should come as no surprise of course.  The Internet is a big place,
gathering together a substantial proportion of humanity in shared
information exchange, and in many cases in direct interactive engagement.
The latter will be especially true in our case.

I hope to see a lot of interest and attention given to scalability within
MMOX discussions.  If we are successful in achieving good levels of
interoperation between virtual worlds, and if the metaverse does indeed
bloom as we hope and expect, then it will be far too late to start
addressing scalability only after systems start to feel the pain of massive
growth.  Protocol features that enhance scalability need to be promoted, and
conversely features that tend to limit scalability need to be viewed with
suspicion, or the future will be a hard one.

I look forward to the task! :-)


Morgaine.

[mmox] Scalability considerations / BCP95, BCP22 Morgaine
Re: [mmox] Scalability considerations / BCP95, BC… Kajikawa Jeremy
Re: [mmox] Scalability considerations / BCP95, BC… Shun-Yun Hu