Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]
Carlo Wood <carlo@alinoe.com> Mon, 29 June 2009 11:44 UTC
Return-Path: <carlo@alinoe.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 BF27B3A6AC2 for <ogpx@core3.amsl.com>;
Mon, 29 Jun 2009 04:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level:
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[AWL=-0.175,
BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, 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 UvItKmfKoXK5 for
<ogpx@core3.amsl.com>; Mon, 29 Jun 2009 04:44:56 -0700 (PDT)
Received: from viefep20-int.chello.at (viefep20-int.chello.at [62.179.121.40])
by core3.amsl.com (Postfix) with ESMTP id 8C9EF3A6855 for <ogpx@ietf.org>;
Mon, 29 Jun 2009 04:44:55 -0700 (PDT)
Received: from edge04.upc.biz ([192.168.13.239]) by viefep20-int.chello.at
(InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id
<20090629114514.WZQK21978.viefep20-int.chello.at@edge04.upc.biz>;
Mon, 29 Jun 2009 13:45:14 +0200
Received: from mail9.alinoe.com ([77.250.43.12]) by edge04.upc.biz with edge
id 9nl11c0CY0FlQed04nl2o6; Mon, 29 Jun 2009 13:45:14 +0200
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from
<carlo@alinoe.com>) id 1MLFIO-00014L-CB; Mon, 29 Jun 2009 13:45:12 +0200
Date: Mon, 29 Jun 2009 13:45:12 +0200
From: Carlo Wood <carlo@alinoe.com>
To: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
Message-ID: <20090629114512.GC1053@alinoe.com>
References: <3a880e2c0906280906i2cdcdaa3m3c1b1ef54e4e5fcb@mail.gmail.com>
<20090629105140.GA1053@alinoe.com>
<b8ef0a220906290413u5a7358eao300c2ff8ee1ab709@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b8ef0a220906290413u5a7358eao300c2ff8ee1ab709@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Infinity Linden <infinity@lindenlab.com>, 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 11:44:56 -0000
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. -- Carlo Wood <carlo@alinoe.com>
- [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