Re: [ogpx] OGPX Draft Charter, 2009 08 25 edition

Infinity Linden <infinity@lindenlab.com> Thu, 27 August 2009 16:14 UTC

Return-Path: <infinity@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 0B61C3A6909 for <ogpx@core3.amsl.com>; Thu, 27 Aug 2009 09:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[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 NLsA1CTImSzM for <ogpx@core3.amsl.com>; Thu, 27 Aug 2009 09:14:52 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 1233A3A68EB for <ogpx@ietf.org>; Thu, 27 Aug 2009 09:14:51 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so280418eye.51 for <ogpx@ietf.org>; Thu, 27 Aug 2009 09:14:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.53.12 with SMTP id f12mr1901484wec.72.1251389693568; Thu, 27 Aug 2009 09:14:53 -0700 (PDT)
In-Reply-To: <3a880e2c0908251418h62303ecesefedcab32343dd71@mail.gmail.com>
References: <3a880e2c0908251418h62303ecesefedcab32343dd71@mail.gmail.com>
Date: Thu, 27 Aug 2009 09:14:53 -0700
Message-ID: <3a880e2c0908270914r185e9e93h3fa89b18c4372b8e@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: ogpx@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [ogpx] OGPX Draft Charter, 2009 08 25 edition
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:14:53 -0000

hmm, so we expanded the single sentence fragment describing the
existence of policy into a paragraph and got this...

On Tue, Aug 25, 2009 at 2:18 PM, Infinity Linden<infinity@lindenlab.com> wrote:
>
> Regions and  Services implemented according to  the specifications may
> be deployed by separate  organizations with varying policies and trust
> domains.  The OGPX  protocols will  provide the  mechanisms  for these
> virtual world  services to interoperate, when permitted  by policy and
> shared trust domains.
>

should we explicitly say that the work of the group will include
defining a non-exhaustive list of places in the protocol where policy
may be inserted?

so we would get something like this instead:

"Regions and  services implemented according to  the specifications
may be deployed by separate  organizations with varying policies and
trust domains.  The OGPX  protocols will  provide the  mechanisms  for
these virtual world  services to interoperate, when permitted  by
policy and  shared trust domains. To support the exegesis of the
specifications, the group may define a non-exhaustive set of
non-normative policies protocol participants may enforce."

so the idea here is that if it makes sense to define a policy for the
purpose of explaining the protocol, we will. but just because a policy
is described does not mean it must be implemented or that policies
other than the ones included in the text are invalid.

thoughts?