Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]

Mike Dickson <mike.dickson@hp.com> Mon, 29 June 2009 13:44 UTC

Return-Path: <mike.dickson@hp.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 49ADB28C23E for <ogpx@core3.amsl.com>; Mon, 29 Jun 2009 06:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level:
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 5puwm-mUqtcJ for <ogpx@core3.amsl.com>; Mon, 29 Jun 2009 06:44:35 -0700 (PDT)
Received: from g5t0009.atlanta.hp.com (g5t0009.atlanta.hp.com [15.192.0.46]) by core3.amsl.com (Postfix) with ESMTP id 762CA3A6ADF for <ogpx@ietf.org>; Mon, 29 Jun 2009 06:44:35 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (unknown [15.192.0.16]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g5t0009.atlanta.hp.com (Postfix) with ESMTPS id 1358730226; Mon, 29 Jun 2009 13:44:54 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-71-194.consolidated.net [209.169.71.194]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 9AC3310004; Mon, 29 Jun 2009 13:44:53 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Carlo Wood <carlo@alinoe.com>
In-Reply-To: <20090629114512.GC1053@alinoe.com>
References: <3a880e2c0906280906i2cdcdaa3m3c1b1ef54e4e5fcb@mail.gmail.com> <20090629105140.GA1053@alinoe.com> <b8ef0a220906290413u5a7358eao300c2ff8ee1ab709@mail.gmail.com> <20090629114512.GC1053@alinoe.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Mon, 29 Jun 2009 08:44:51 -0500
Message-Id: <1246283091.4197.69.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
Cc: Infinity Linden <infinity@lindenlab.com>, Meadhbh Siobhan <meadhbh.siobhan@gmail.com>, "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mike.dickson@hp.com
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, 29 Jun 2009 13:44:36 -0000

I have to agree with Carlo on this.  This is a case where virtual life
needs to model real life.  Lots of people with the same name in the
world.  The protocol needs to support some other way to uniquely
identify a "user" other than FN/LN. 

When crossing into a new region it seems highly possible that a region
owner may want to require a re-authentication also. 

I'm not suggesting a solution becaus this isn't my personal area of
expertise.  Simply stating I see the problem and agree a good solution
needs to be found. 

Mike

On Mon, 2009-06-29 at 11:45 +0000, Carlo Wood wrote:
> On Mon, Jun 29, 2009 at 04:13:08AM -0700, Meadhbh Siobhan wrote:
> > On Mon, Jun 29, 2009 at 3:51 AM, Carlo Wood<carlo@alinoe.com> wrote:
> > as mentioned in the draft, deployers MAY choose to identify users via
> > account ids rather than first+last.
> 
> But that is local to the deployers.
> 
> What is used to ID an agent in the server-server protocol
> when a user walks from one region into another, or teleports
> to a different region?
> 
> Firstname Lastname should be merely payload, not interesting
> to the servers, not being used for anything except passing
> it on the the viewers so they can use it to put in the tags.
> 
> There must be some other string, that is globally unique,
> that is used to ID the agent. I was missing that string
> in the first post that started this.
>