Re: [ogpx] Second Life

Morgaine <morgaine.dinova@googlemail.com> Mon, 11 January 2010 22:44 UTC

Return-Path: <morgaine.dinova@googlemail.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 E40763A6839 for <ogpx@core3.amsl.com>; Mon, 11 Jan 2010 14:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 lCiwb6Hrp1t4 for <ogpx@core3.amsl.com>; Mon, 11 Jan 2010 14:44:15 -0800 (PST)
Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by core3.amsl.com (Postfix) with ESMTP id 0D4B93A6803 for <ogpx@ietf.org>; Mon, 11 Jan 2010 14:44:14 -0800 (PST)
Received: by ewy1 with SMTP id 1so3832643ewy.28 for <ogpx@ietf.org>; Mon, 11 Jan 2010 14:44:07 -0800 (PST)
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:content-type; bh=QhC4lIbClsVXxrvV/ukiJlSVkTyCSkdrwNAemVmL+Sg=; b=iAyhUq4W88CbpbI/C4YRYYMG4iRE1AqG0QBqwRfONiXnc5oX9x4KB9A/38KUkZAXij TuxJ0F6uZU3ZAB3MiOaWi2pAz0gQY7jWVvOjMq4QCALHn451csr+i4b62NTyXHiz8+C4 z6ELorch4tuOTBMS7NrmWqbu4U9MXqeOq3flU=
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 :content-type; b=escUxH5eJAVqmVENDl1RYhZM9/+duBn6jfFbQ1AiXBam2SygiLvSLCdabzJF99HtoL JNuII+UmWE5kmZ5dsTkFgXdLIhWHgJ6xB04x7VkIwZoGLrY8Le90rdGxY2b/9i6LFGVc 94cE71k7scFGbSXw6150D/T5BhWPn7z6oyEZY=
MIME-Version: 1.0
Received: by 10.213.24.21 with SMTP id t21mr4090740ebb.56.1263249845198; Mon, 11 Jan 2010 14:44:05 -0800 (PST)
In-Reply-To: <f72742de1001110847o1ea371dt95ab8e4d388b2f22@mail.gmail.com>
References: <20100106142220.GA11321@alinoe.com> <e0b04bba1001072033y223be42pf31b1e014674d665@mail.gmail.com> <9b8a8de41001080324l6a76df7fp63df7d94aa6f220f@mail.gmail.com> <20100108135734.GA24975@alinoe.com> <9b8a8de41001081358r3c3c52a9se40c4786b8efa76@mail.gmail.com> <698969.35231.qm@web111213.mail.gq1.yahoo.com> <9b8a8de41001100651w66c58f1m7ae1591c36e12454@mail.gmail.com> <f72742de1001110847o1ea371dt95ab8e4d388b2f22@mail.gmail.com>
Date: Mon, 11 Jan 2010 22:44:05 +0000
Message-ID: <e0b04bba1001111444l7f7aa60bt3ef6ddb4b15670ba@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary="000e0cdff9bc49207b047ceb46e4"
Subject: Re: [ogpx] Second Life
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: Mon, 11 Jan 2010 22:44:17 -0000

Joshua,

On Mon, Jan 11, 2010 at 4:47 PM, Joshua Bell <josh@lindenlab.com> wrote:

>
> (The caveat being that submitting a revision to another author's draft
without consent or discussion about hand-off is considered bad form, and
leads to extreme difficulties in tracking changes.)

That would be necessary only if an author were unwilling to take the group's
suggested modifications into account when making new revisions.  That's not
the current position as far as I know.

IETF protocol work is not a war between competing drafts (or at least it's
not supposed to be).  It's intended to be a cooperative analysis of problems
and a group discussion of possible solutions, from which new and better
versions of protocol specs are honed.

To achieve quality teamwork requires that the authors of drafts take the
group's discussions into account when making new versions, otherwise the WG
is undermined.  When nothing is heard because documents are being updated
silently behind closed doors, its sends the wrong message, even if all is
well.  I recommend talking to the group while working on revisions, so that
changes are known to be on roughly the right track throughout the process.

*Traceability* is very important to avoid elements of progress being lost.
Before a new draft is issued, the areas of change really need to be
enumerated first so that it is easy to check that they have been addressed
in the new revision.  Pumping out new revisions without first agreeing on
what is being updated can look like teamwork avoidance, and makes the
group's efforts a lot more difficult.

I think we were on a very positive track in Q4 of last year, and it would be
sad to see a regression.


Morgaine.






=============================

On Mon, Jan 11, 2010 at 4:47 PM, Joshua Bell <josh@lindenlab.com> wrote:

> On Sun, Jan 10, 2010 at 6:51 AM, Vaughn Deluca <vaughn.deluca@gmail.com>wrote:
>
>>
>> But anyhow, i do not  think we have much options other than wait, (or we
>> would have to do the work ourselfs..). Personally i do not feel the time for
>> such drastic steps (starting to write our own drafts) is their yet.
>>
>
> If there was ever any implication that documents from other authors would
> not be welcome, let me dispel that now: within the charter of the working
> group, please please please contribute your thoughts and suggestions as
> informally or formally as you see fit (within the auspices of the NOTE WELL
> yadda yadda). Additional drafts from new authors are explicitly welcome.
>
> (The caveat being that submitting a revision to another author's draft
> without consent or discussion about hand-off is considered bad form, and
> leads to extreme difficulties in tracking changes.)
>
> The charter page http://www.ietf.org/dyn/wg/charter/vwrap-charter provides
> a roadmap of the expected pieces of the protocol, with completion dates for
> some of them estimated as two years from now. No work has begun on many of
> them, nor is it established that the list is sufficient for defining the
> sort of interop VWRAP envisions.
>
> There are also several chunks mentioned in the charter that are reasonably
> independent of the others that could be tackled now with little dependency
> on other work. I'd encourage list contributors to pick those up, either to
> begin discussion or start documenting and providing sample implementations.
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>