Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]
Christian Scholz <cs@comlounge.net> Mon, 29 June 2009 14:05 UTC
Return-Path: <cs@comlounge.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 032C53A6A44 for <ogpx@core3.amsl.com>;
Mon, 29 Jun 2009 07:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, J_CHICKENPOX_36=0.6, J_CHICKENPOX_54=0.6]
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 o4xXn9-K7ZoB for
<ogpx@core3.amsl.com>; Mon, 29 Jun 2009 07:05:16 -0700 (PDT)
Received: from post.comlounge.net (post.comlounge.net [85.214.59.142]) by
core3.amsl.com (Postfix) with ESMTP id CFAF53A680C for <ogpx@ietf.org>;
Mon, 29 Jun 2009 07:05:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by post.comlounge.net
(Postfix) with ESMTP id A75BD1CE00DA; Mon, 29 Jun 2009 16:04:27 +0200 (CEST)
Received: from post.comlounge.net ([127.0.0.1]) by localhost
(h1346004.stratoserver.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 2oLTbcyRBnon; Mon, 29 Jun 2009 16:04:26 +0200 (CEST)
Received: from Labertasche.local (unknown [81.187.73.203]) by
post.comlounge.net (Postfix) with ESMTP id 83CCE1CE0047;
Mon, 29 Jun 2009 16:04:24 +0200 (CEST)
Message-ID: <4A48C9E6.6080705@comlounge.net>
Date: Mon, 29 Jun 2009 15:04:22 +0100
From: Christian Scholz <cs@comlounge.net>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: mike.dickson@hp.com
References: <3a880e2c0906280906i2cdcdaa3m3c1b1ef54e4e5fcb@mail.gmail.com> <20090629105140.GA1053@alinoe.com> <b8ef0a220906290413u5a7358eao300c2ff8ee1ab709@mail.gmail.com> <20090629114512.GC1053@alinoe.com>
<1246283091.4197.69.camel@mdickson-laptop>
In-Reply-To: <1246283091.4197.69.camel@mdickson-laptop>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-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
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 14:05:17 -0000
Mike Dickson wrote: > 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. I would also go further and say that it would be great to reuse identities on non-3D social networks. As we see with OpenID this usually is done via URLs (like myspace.com/mrtopf and now also facebook.com/mrtopf) and I don't see why this shouldn't be used here as well. firstname/lastname should be provided as well of course (e.g. via reading it over an OpenSocial REST API) but the real identity is then defined via the URL. I am not sure where to display it though, if directly over an avatar or inside the profile page but that needs some experimentation I guess. At least some means need to be given to find out which person it actually is. -- Christian > 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. >> > > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx -- Christian Scholz Homepage: http://comlounge.net COM.lounge GmbH blog: http://mrtopf.de/blog Hanbrucher Str. 33 Skype: HerrTopf 52064 Aachen Video Blog: http://comlounge.tv Tel: +49 241 400 730 0 E-Mail cs@comlounge.net Fax: +49 241 979 00 850 IRC: MrTopf, Tao_T neuer Podcast: Der OpenWeb-Podcast (http://openwebpodcast.de) new podcast: Data Without Borders (http://datawithoutborders.net)
- [ogpx] A Review of Multi-Domain Use Cases [Was: R… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Meadhbh Siobhan
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Mike Dickson
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Christian Scholz
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Meadhbh Siobhan
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Meadhbh Siobhan
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Charles Krinke
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Charles Krinke
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Joshua Bell
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Morgaine
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Nexii Malthus
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Carlo Wood
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Infinity Linden
- Re: [ogpx] A Review of Multi-Domain Use Cases [Wa… Kajikawa Jeremy