Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]
Meadhbh Siobhan <meadhbh.siobhan@gmail.com> Mon, 29 June 2009 14:51 UTC
Return-Path: <meadhbh.siobhan@gmail.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 8F38E28C0FD for <ogpx@core3.amsl.com>;
Mon, 29 Jun 2009 07:51:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[AWL=-0.002,
BAYES_00=-2.599, 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 Ba+YmkKb2gU2 for
<ogpx@core3.amsl.com>; Mon, 29 Jun 2009 07:51:19 -0700 (PDT)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com
[209.85.210.182]) by core3.amsl.com (Postfix) with ESMTP id 7D04F28C0F3 for
<ogpx@ietf.org>; Mon, 29 Jun 2009 07:51:19 -0700 (PDT)
Received: by yxe12 with SMTP id 12so1197316yxe.29 for <ogpx@ietf.org>;
Mon, 29 Jun 2009 07:51:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding;
bh=ZFQHAviupfvurXX+4pjeqPt0/1Wrl0je917yOC8ive4=;
b=G/qixnlr+peiVYigpxgA3XtnwrvDF+nacv8E5fcvUxOoS2oIPDmyCZZEqZcLNKDJLi
/uIAcR/7zYW2ySmX458YEGxJL8/xSWdHI3yLTKimPzRPslZw40XlPYyU9lAbiZZdxKFv
3/ID14aO0fh9rLK6khrtNfthd3l2yzo19Lrko=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
b=lIEaqyTBKdh7NpVMd3QPenXIv5QqYjyv6k2Lq0wst0ubQPwGLWO0P/345xtnatv1hH
1ovjyyp3P292OO+uuZyF0siFOzNQtsDiW5vXub8K1Q07/CwbXuYA5zU2xI6/A1t39cEZ
b7u3F8yMxo8JGs1crDppN/llKZpbVNyKC9KVQ=
MIME-Version: 1.0
Received: by 10.100.164.20 with SMTP id m20mr9386182ane.31.1246287069214;
Mon, 29 Jun 2009 07:51:09 -0700 (PDT)
In-Reply-To: <20090629114512.GC1053@alinoe.com>
References: <3a880e2c0906280906i2cdcdaa3m3c1b1ef54e4e5fcb@mail.gmail.com>
<20090629105140.GA1053@alinoe.com>
<b8ef0a220906290413u5a7358eao300c2ff8ee1ab709@mail.gmail.com>
<20090629114512.GC1053@alinoe.com>
Date: Mon, 29 Jun 2009 07:51:09 -0700
Message-ID: <b8ef0a220906290751s5131c401h1d55ace39348c89e@mail.gmail.com>
From: Meadhbh Siobhan <meadhbh.siobhan@gmail.com>
To: Carlo Wood <carlo@alinoe.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 14:51:20 -0000
okay. i get you. the question is, "how do you ID distinct users with the same name from two different agent domains?" an example use case might be... "You have two distinct users who both have avatars named 'John Smith' registered with two distinct agent domains (we'll call them 'avatarsrus.com' and 'businessworlds.com'.) how do you make the 'John Smith' from avatarsrus.com identifiable as a distinct entity from 'John Smith' from businessworlds.com so that both could be rezzed into the same region and both own assets that are rezzed in world simultaneously." so you have two issues: first, how do you identify the two as being distinct to the simulator and second, how do you identify the two as being distinct to other users since they'll both have the "John Smith" avatar name displayed. the first (how are the two identified to the simulator) is that agents will have a publicly addressable protocol endpoint in the form of a URL at their agent domains. The first agent might have the URL http://avatarsrus.com/a/Smith/John while the second has the URL http://bsinessworlds.com/BDFB8691-9FD5-444A-B601-4075E7226242. The format of the URL doesn't matter as long as the agent domain guarantee's they're unique and under the control of the agent domain. the second one is left as an exercise to client application developers and is analogous to the difficulty end users may have in differentiating two entities with the same name but distinct email addresses. On Mon, Jun 29, 2009 at 4:45 AM, Carlo Wood<carlo@alinoe.com> 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. > > -- > 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