Re: [ogpx] Global Agent Domain Registry [Was: Re: OpenID and OGP : beginning the discussion ...]
Kajikawa Jeremy <belxjander@gmail.com> Mon, 06 July 2009 10:54 UTC
Return-Path: <belxjander@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 8973A3A6BB9 for <ogpx@core3.amsl.com>;
Mon, 6 Jul 2009 03:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, SARE_RMML_Stock10=0.13]
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 g1PT+eVeVigi for
<ogpx@core3.amsl.com>; Mon, 6 Jul 2009 03:54:29 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com
[209.85.198.236]) by core3.amsl.com (Postfix) with ESMTP id A730528C2F4 for
<ogpx@ietf.org>; Mon, 6 Jul 2009 03:53:43 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id f9so1098722rvb.49 for
<ogpx@ietf.org>; Mon, 06 Jul 2009 03:54:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:subject:from:to:in-reply-to
:references:disposition-notification-to:content-type:date:message-id
:mime-version:x-mailer:content-transfer-encoding;
bh=qCDZW0iTkNz+8MRg+56grvtRQZbywr0y5V+lhGUg38g=;
b=Sfy71MWJrAMOFg9uCrKwwm/G1TjD1XiAmSwXBdct4wmxj7j4u1M4VSgcBUbqL4xYOR
9qxlcBCkEfWv8OXNfvs/Hev78OnvVGmnsZkyqD2e8GlXGgA219KnU98Wh1CeNqUvPCKu
kH6t9FDoMA1SKlFX8liYSNvPxormwOweFPA7g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=subject:from:to:in-reply-to:references:disposition-notification-to
:content-type:date:message-id:mime-version:x-mailer
:content-transfer-encoding;
b=j/HdpFik0f7WdQ03Pe6KbDRWxa1y5PUkXPkh55G8DgQAklUGmcwnooW8QmAwvh30N+
CshWXZpqSQalvs1UXP6X+Wt9G/AT3ZKz2eGyJgP6scXgdYejiyEwzbh/S6xWXaiynhSs
eP/i4ef6GLQF8sL79Dq5Ee49ewHlTEq4i6eME=
Received: by 10.140.203.3 with SMTP id a3mr2225738rvg.238.1246877640468;
Mon, 06 Jul 2009 03:54:00 -0700 (PDT)
Received: from ?10.2.1.3? (p3146-ipbfp203tottori.tottori.ocn.ne.jp
[123.226.140.146]) by mx.google.com with ESMTPS id
k37sm27749973rvb.48.2009.07.06.03.53.57 (version=SSLv3 cipher=RC4-MD5);
Mon, 06 Jul 2009 03:53:58 -0700 (PDT)
From: Kajikawa Jeremy <belxjander@gmail.com>
To: ogpx@ietf.org
In-Reply-To: <3a880e2c0906280906if8f9791h89a9bc13a7170b53@mail.gmail.com>
References: <3a880e2c0906280906if8f9791h89a9bc13a7170b53@mail.gmail.com>
Content-Type: text/plain
Date: Mon, 06 Jul 2009 17:56:53 +0900
Message-Id: <1246870613.11996.23.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.2
Content-Transfer-Encoding: 7bit
Subject: Re: [ogpx] Global Agent Domain Registry [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, 06 Jul 2009 10:54:30 -0000
Why not a simple option of including an "@domain" extra identifier? when interacting with multiple domains... Each domain keeps an own registry and cross-domain relations can use a pre-agreed Domain ID... That way anyone can use a given name but confusion is avoided since there are people already existing with the same name that I am already aware of (R.W. solution is middle initial or other seperator when together) Why not re-use an already usable social custom and define for any interop across "Agent Domain"s ... similar to "somename@hotmail.com" being different to "somename@gmail.com".com", and I would suggest use of the Originating AgentDomain as being the seperator for this use case of multiple-same-name Avatars On Sun, 2009-06-28 at 09:06 -0700, Infinity Linden wrote: > okay... so it seems like you're actually asking... "how do we maintain > global avatar name uniqueness if avatar first and last name are used > as primary keys for logging in?" > > there was some discussion about a global avatar name registry last > year in the SL Architecture Working Group, though i don't think there > were any definitive results. > > i think we're punting on the problem with respect to protocol > development. that is, i don't think the protocol specifications will > say anything about the expectation that an agent name be globally > unique across grids. > > deploying such a service would be quite an effort in terms of community buy-in. > > that being said, there's no reason it can't be done in the future or > as a project of a non-IETF group. > > for the time being, we can use account identifiers to guarantee > uniqueness; or at least that's my sense given the lack of radical > agreement in the topic. > > in other words, i think it's a topic that will lead to wailing and > gnashing of teeth and would only serve to delay production of > standards that people _do_ agree on. > > On Sun, Jun 28, 2009 at 5:34 AM, Carlo Wood<carlo@alinoe.com> wrote: > > I'm glad it doesn't imply that then :p > > > > Nevertheless, it worries me a bit. At some point we want to be able to > > teleport between grids right? Surely the people will want to have the > > same name (and shape) after they teleported in most cases. > > > > If the same first_name+last_name is only unique per grid, then > > people will (have to) start fights about names: one has to register > > the same first_name+last_name on every grid you want to use. > > > > The make a long story short: they same wars and trouble will immerse > > as are happening on IRC now: too many people in a too small namespace. > > > > At some point there will come the strong demand for a "nick serv", > > some central point where people can reserve their name for every > > large grid on the planet and claim for themselves (for example, to > > stop forms of impersonations). That would be 'hack'. > > > > I think we have to seriously think about this. Perhaps there is a > > better solution than 'first name / last name' to login ;). > > > > On Sat, Jun 27, 2009 at 03:54:08PM -0700, Infinity Linden wrote: > >> why would this imply global uniqueness? it describes a message sent > >> from a client to a particular protocol endpoint. > >> > >> On Sat, Jun 27, 2009 at 3:33 AM, Carlo Wood<carlo@alinoe.com> wrote: > >> >> & identifier = { > >> >> type: 'account', > >> >> account_name: string, > >> >> first_name: string, > >> >> last_name: string, > >> >> } > >> >> > >> >> & identifier = { > >> >> type: 'agent', > >> >> first_name: string, > >> >> last_name: string, > >> >> } > >> > > >> > This seems to implicate that first_name + last_name > >> > have to be unique not only per grid, but globally > >> > for every virtual world. > >> > > >> > Is that true? Or would it be possible to use a different > >> > name on different grids? Would it be possible that different > >> > unrelated people use the same name on different grids? > > > > -- > > Carlo Wood <carlo@alinoe.com> > > > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx
- [ogpx] Global Agent Domain Registry [Was: Re: Ope… Infinity Linden
- [ogpx] Globally unique authentication token versu… Carlo Wood
- Re: [ogpx] Global Agent Domain Registry [Was: Re:… Kajikawa Jeremy