Re: [ogpx] resolving the name issue

Joshua Bell <josh@lindenlab.com> Thu, 27 August 2009 16:26 UTC

Return-Path: <josh@lindenlab.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DEB43A6D65 for <ogpx@core3.amsl.com>; Thu, 27 Aug 2009 09:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.925
X-Spam-Level:
X-Spam-Status: No, score=-0.925 tagged_above=-999 required=5 tests=[AWL=-0.438, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 ACqOH+mwPifF for <ogpx@core3.amsl.com>; Thu, 27 Aug 2009 09:26:31 -0700 (PDT)
Received: from mail-px0-f202.google.com (mail-px0-f202.google.com [209.85.216.202]) by core3.amsl.com (Postfix) with ESMTP id 94AE928C1FB for <ogpx@ietf.org>; Thu, 27 Aug 2009 09:26:31 -0700 (PDT)
Received: by pxi40 with SMTP id 40so1164847pxi.5 for <ogpx@ietf.org>; Thu, 27 Aug 2009 09:26:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.48.9 with SMTP id a9mr4283077rvk.249.1251390395494; Thu, 27 Aug 2009 09:26:35 -0700 (PDT)
In-Reply-To: <479011.65903.qm@web111210.mail.gq1.yahoo.com>
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com> <479011.65903.qm@web111210.mail.gq1.yahoo.com>
Date: Thu, 27 Aug 2009 09:26:35 -0700
Message-ID: <f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd22bd2ffb1580472220760
Subject: Re: [ogpx] resolving the name issue
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 16:26:32 -0000

It seems like we're close on draft charter text; the recent discussion has
generated some good additions and clarifications to the text. We still need
a name, though.

Given a lack of consensus on any of the proposals for a protocol name, I
suggest we reduce the problem to just a group name, and defer any protocol
naming for now.

* The working group name is for "casual" use; i.e. it will never be
published in an RFC
* The working group should have a limited lifetime, and dissolve; so
something "eternal" or "ideal" is actually a bad idea
* It should be clear how to pronounce and spell, so that it can be
communicated in voice
* It should be recognizable when seen on an IETF agenda

I agree with Morgaine's points earlier on this thread about names, but feel
they primarily apply to protocol names, except for the excellent suggestion
that this be something relatively unique in Google searches. That is
somewhat in (healthy) conflict with the above points, though.

Going back to Infinity's suggestion of listing top choices, here are mine
from the floated proposals. I don't really have a #3. Again, I'm focusing on
proposed working group names only, so in context these would be

1. Agent Based Open Virtual Environments Working Group - ABOVE ("above")
2. Virtual World Region/Agent Protocol Working Group - VWRAP ("v-wrap")

If you believe that the latest rev of the draft charter text is acceptable
as a basis for forming a working group (and remember, a group can
re-charter!), please reply with your top picks.