Re: [mmox] IETF policy question

Heiner Wolf <wolf.heiner@googlemail.com> Thu, 26 March 2009 01:21 UTC

Return-Path: <wolf.heiner@googlemail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D55CD3A67AD for <mmox@core3.amsl.com>; Wed, 25 Mar 2009 18:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.177
X-Spam-Level:
X-Spam-Status: No, score=-2.177 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yk+6Ghk1VxtC for <mmox@core3.amsl.com>; Wed, 25 Mar 2009 18:21:00 -0700 (PDT)
Received: from mail-fx0-f158.google.com (mail-fx0-f158.google.com [209.85.220.158]) by core3.amsl.com (Postfix) with ESMTP id 45F303A6805 for <mmox@ietf.org>; Wed, 25 Mar 2009 18:21:00 -0700 (PDT)
Received: by fxm2 with SMTP id 2so329440fxm.37 for <mmox@ietf.org>; Wed, 25 Mar 2009 18:21:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WpguCJbw70ngEPfhKANb19YNfjStjDiJWvGCmAkppL0=; b=Le9Rp5k9XbE27xHXXQ/bqpvAtrsEWpMroYRRrl8tpkWSun0lbDmSbXYWJtsiHzzY94 DkVFOZq1M1KiHI9S/zBsaQEzjy66AjM+5UUYqvM3yaYnLHudxiLRhCFF/u2kLhtnKz+R wZi/DOdYAk0a8bMN3ZgOa3/g8xdw5DxCCM3aI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TkpAK2n72jGcy1+OQG/BjvKL/7QGcGpQSy1+rhg3InuwqK9u4D1GlK7NusbRKEcgOR x53MsMnd5XLNnq5WJtl6HYVx9Kgw7coFVTAJjALm+Gcev4yt0o+hRtcTUbfvuqQz+jBC GkjT0u4CnW/LVE9zEk835sSiEVkaqAkqqHgbQ=
MIME-Version: 1.0
Received: by 10.223.105.9 with SMTP id r9mr185690fao.66.1238030512111; Wed, 25 Mar 2009 18:21:52 -0700 (PDT)
In-Reply-To: <7EB8CBA6B67A41F694A4D3D91B947CB4@KEVINPC>
References: <5f303cb80903251620k163ede14y38e8785d94a417b3@mail.gmail.com> <7EB8CBA6B67A41F694A4D3D91B947CB4@KEVINPC>
Date: Wed, 25 Mar 2009 18:21:52 -0700
Message-ID: <5f303cb80903251821x64b6b230j236cda45920939eb@mail.gmail.com>
From: Heiner Wolf <wolf.heiner@googlemail.com>
To: Mystical Demina <MysticalDemina@xrgrid.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: mmox@ietf.org
Subject: Re: [mmox] IETF policy question
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 01:21:01 -0000

Hi,

I am not
- suggesting,
- talking about 57 VWs.

I am
- trying to be balanced without implied tendency,
- asking experienced IETF members, e.g. ADs about proven policy.

Best
hw

On Wed, Mar 25, 2009 at 6:10 PM, Mystical Demina
<MysticalDemina@xrgrid.com> wrote:
> But I think you are wrong about the other 57 platforms out there.  Don't
> they all need to have a teleport location specification so that can jump
> between their own virtual worlds time they are able to interoperate.  And if
> they all move forward using the same specification the foundation is set for
> when a client can interoperate with different virtual worlds.
>
> But more than that, you suggest all 57 virtual worlds wait till they can all
> talk together.  I will suggest to you the market will not wait for that.  To
> me it better to have simple solution and grow it, than have no solution.
>
> But that is my opinion, maybe others feel different.
>
> Kevin
>
>
> -----Original Message-----
> From: mmox-bounces@ietf.org [mailto:mmox-bounces@ietf.org] On Behalf Of
> Heiner Wolf
> Sent: Wednesday, March 25, 2009 7:20 PM
> To: mmox@ietf.org
> Subject: [mmox] IETF policy question
>
> Hi,
>
> Assumed there are multiple systems with incompatible architecture,
> each sophisticated and with it's own protocols.
> Assumed that we as a WG do not know enough about the general problem space.
> Assumed that there are sub-groups which know enough about their
> problem and have working solutions.
>
> What would the IETF do?
> 1. task one of the sub-groups to standardize one of the
> protocol/architecture variants, although it might leave a large part
> of the community out of the loop, while having at least a hope to
> defeat fragmentation in the future
> ...or...
> 2. do not standardize at IETF level, which might be good for the
> competition of ideas and allows the community to learn more about the
> general problem space, but preserves fragmentation unless the market
> cleans it up.
>
> I am really undecided, but there is probably BCP in the IETF.
>
> Best
> --
> Dr. Heiner Wolf
> wolf.heiner@gmail.com
> www.wolfspelz.de
> www.virtual-presence.org
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>



-- 
Dr. Heiner Wolf
wolf.heiner@gmail.com
www.wolfspelz.de
www.virtual-presence.org