Re: [ogpx] VWRAP Draft Charter - 2009 09 01

Morgaine <morgaine.dinova@googlemail.com> Sun, 04 October 2009 02:13 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 3D4153A685C for <ogpx@core3.amsl.com>; Sat, 3 Oct 2009 19:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.533
X-Spam-Level:
X-Spam-Status: No, score=-1.533 tagged_above=-999 required=5 tests=[AWL=0.443, 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 lmx4p+GNgzso for <ogpx@core3.amsl.com>; Sat, 3 Oct 2009 19:13:26 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 935373A67E7 for <ogpx@ietf.org>; Sat, 3 Oct 2009 19:13:25 -0700 (PDT)
Received: by ewy28 with SMTP id 28so2926001ewy.42 for <ogpx@ietf.org>; Sat, 03 Oct 2009 19:14: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; bh=4VhxSz6858iCQLQ1zGB2b4GwAs60Wr+ohm1Q9+7bJyM=; b=uCxrefgluR3RGOr8KfMPMz1Vq+5RiutKJSHeyi5PCX48gY8D5/7uj3rdjSASmMBJCG rUjtqbp7t6iXr6To+zgfvT4apdwh6dshOdFyp6rerPTzkRULMgJDcnfpuHtl/emq/QaN cCB3gvIy+ohy9mHbv6QlRD9cHr/mVda78wBrQ=
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; b=Mbv3g9on5qnB+qovIj3BQOFFFoUfFyKzZQXgWKXn4QLO87nN9hVtIGN4HRkrKIIC+w /SJoRlgR3jzDN/2NzIihKTNYhPnLzxz6gio/Llhy2BcZyHXAst0d/mZeeKsvy1tqvgVG CbNwP+Sj/hXYt/bIjUAUKtqZJlVjP9aCCKxPY=
MIME-Version: 1.0
Received: by 10.211.156.13 with SMTP id i13mr5303302ebo.22.1254622492822; Sat, 03 Oct 2009 19:14:52 -0700 (PDT)
In-Reply-To: <4646639E08F58B42836FAC24C94624DD771A0D8236@GVW0433EXB.americas.hpqcorp.net>
References: <e0b04bba0909291751g157d2043g1c15e8d8ac417ccf@mail.gmail.com> <e0b04bba0910011613w6f25b684w1b0f2e8c7187b3de@mail.gmail.com> <f72742de0910011632n3488ff6aqbf93edbda2a51637@mail.gmail.com> <e0b04bba0910012252v540dd170k4b81e30052e6c974@mail.gmail.com> <3a880e2c0910020932t5995c477qb0d798de1c2653f6@mail.gmail.com> <20091003192159.GA7474@alinoe.com> <e0b04bba0910031452o2a497effi57c4e92f8902b5df@mail.gmail.com> <20091003222118.GA16290@alinoe.com> <e0b04bba0910031633k2127d996v5ef5d3f356623a69@mail.gmail.com> <4646639E08F58B42836FAC24C94624DD771A0D8236@GVW0433EXB.americas.hpqcorp.net>
Date: Sun, 04 Oct 2009 03:14:52 +0100
Message-ID: <e0b04bba0910031914r26042a2chccf94ec1356d7230@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: "Dickson, Mike (ISS Software)" <mike.dickson@hp.com>
Content-Type: multipart/alternative; boundary="00504502d2ed030b6c04751290f4"
Cc: "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] VWRAP Draft Charter - 2009 09 01
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: Sun, 04 Oct 2009 02:13:27 -0000

On Sun, Oct 4, 2009 at 1:36 AM, Dickson, Mike (ISS Software) <
mike.dickson@hp.com> wrote:

>  The algorithm or mechanism to enforce an age related connection policy is
> outside the scope of the protocol, yes.  But its not at all  inconceivable
> that the protocol could carry age information as an attribute that an AD/RD
> pair could use to make a decision as to whether a connection is to be
> allowed.
>

As carried payload, sure.  Just like an SMTP message could carry a message
body or even a Subject line about the age of a mail user or about the ages
of the MTA sysadmins.  But that's not at the level of protocol at all.  If
the SMTP protocol dealt with the ages of the users of its endpoint
applications as a machine-processable semantic, we would be entering an age
of total madness and police states.

Admittedly, there are totally mad people and police-state advocates around,
but hopefully we are not among them.  Particularly when it's purely *security
theater* and doesn't actually achieve anything.


Morgaine.





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

On Sun, Oct 4, 2009 at 1:36 AM, Dickson, Mike (ISS Software) <
mike.dickson@hp.com> wrote:

>  The algorithm or mechanism to enforce an age related connection policy is
> outside the scope of the protocol, yes.  But its not at all  inconceivable
> that the protocol could carry age information as an attribute that an AD/RD
> pair could use to make a decision as to whether a connection is to be
> allowed.
>
>
>
> Mike
>
>
>
> *From:* ogpx-bounces@ietf.org [mailto:ogpx-bounces@ietf.org] *On Behalf Of
> *Morgaine
> *Sent:* Saturday, October 03, 2009 6:34 PM
> *To:* Carlo Wood
> *Cc:* ogpx@ietf.org
> *Subject:* Re: [ogpx] VWRAP Draft Charter - 2009 09 01
>
>
>
> On Sat, Oct 3, 2009 at 11:21 PM, Carlo Wood <carlo@alinoe.com> wrote:
>
> On Sat, Oct 03, 2009 at 10:52:18PM +0100, Morgaine wrote:
> > It's important to highlight (as you did) that issues such as age
> verification
> > have no place in a worldwide IETF protocol standard, so while you provide
> a
> > good example of policy variations among worlds, any such agreements are
> outside
> > of the context of our protocol.
>
> Not entirely... age verification is necessary in many countries with
> what's going on in an SL-like world.
>
> A RD cannot do the age-verification; that is a job for an AD.
>
> However, I think it's the RD that needs to make the decision whether
> or not a user is allowed in (based on its age), which in turn means
> that the AD has to tell the RD if it knows the age, and if so, what
> it is; hence, it should be part of the protocol.
>
>
> It's no business of an IETF protocol to deal with the age of participants.
> That's like SMTP rejecting connections or mail delivery based on the ages of
> the MTA operator and owner of the mail client.  The whole idea is completely
> ludicrous, not to mention unimplementable.
>
> Please let's try not to engage in what Schneier calls "security theater", a
> politically correct feelgood factor that actually achieves nothing while
> adding layers of red tape and complexity.
>
> Morgaine.
>
>
>