Re: [ogpx] resolving the name issue

Dave CROCKER <dhc@dcrocker.net> Fri, 28 August 2009 15:17 UTC

Return-Path: <dhc@dcrocker.net>
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 10EF23A6F88 for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599]
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 j239BSHjXEKF for <ogpx@core3.amsl.com>; Fri, 28 Aug 2009 08:17:03 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id D3C9B3A6E10 for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:17:02 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n7SFH3fn027888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ogpx@ietf.org>; Fri, 28 Aug 2009 08:17:08 -0700
Message-ID: <4A97F4EA.2030803@dcrocker.net>
Date: Fri, 28 Aug 2009 08:16:58 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ogpx@ietf.org
References: <3a880e2c0908211129l7d9defa5od81261e3e5805714@mail.gmail.com> <479011.65903.qm@web111210.mail.gq1.yahoo.com> <f72742de0908270926o6991317cw8d140a7f371e7245@mail.gmail.com> <3a880e2c0908270937j73fe7567t8779d193135d0b5f@mail.gmail.com>
In-Reply-To: <3a880e2c0908270937j73fe7567t8779d193135d0b5f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 28 Aug 2009 08:17:08 -0700 (PDT)
Subject: Re: [ogpx] resolving the name issue
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Fri, 28 Aug 2009 15:17:04 -0000

Infinity Linden wrote:
> but yeah, i think what i'm saying is while we can separate the
> protocol name from the group name and we might be able to get away
> with not mentioning the protocol name in the charter, we'll need a
> protocol name pretty quick so we can use it in the IDs.


If the working group were going to deal with a number of independent (but 
related) specifications, each of which would have their own name, then giving 
the working group yet-a-different name would make sense.  And no, it's not the 
end of the world one way or the other, but it IS less confusing to have the wg 
name and the primary specification name match.

The comment about a name that is too common a word, like ABOVE, is well-taken.

I think vwrap is reasonable.

(It also permits flights of analogy and other whimsy.  Not essential, of course, 
but can add some entertainment to a community effort...)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net