Re: [mmox] OGP scalability concerns
Jon Watte <jwatte@gmail.com> Thu, 02 April 2009 16:37 UTC
Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E82B23A69A8 for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 09:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level:
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599]
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 1AQKmVYTAhD1 for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 09:37:16 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by core3.amsl.com (Postfix) with ESMTP id 273A33A6917 for <mmox@ietf.org>; Thu, 2 Apr 2009 09:37:16 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id k40so624447rvb.49 for <mmox@ietf.org>; Thu, 02 Apr 2009 09:38:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=tRlv6yIIfevEBAJ6yaDB0iJH3Z2CMBkBpG2ln5szs8Q=; b=NIzcdaKWcltp2k4MuML4rZrfQlL8lFQGgv+u7Dg4cxpBXzYHqMajn/oxPvqEbxOkIF sFKAbzVOS+hHSj76CYF6QqF2+ap9vzuWmbDomeyghcDS0bkwecgaVwnsBlHLCWNRYShK /6yS+2omCt58Uwam4SXtkNJPUFEZaFhkcusMc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=DJaIr0iGUxybGvKGnKUp9Va/Ykp9bhtIMs7EgK+Sy6oY3ryOYCHsdGtU5F9zZey0C4 NNLLhYtpkb6tZZXj3gG18gzXbtyrQQXx6GI+9FVrIeWQap7AKBPH+rjemTJ5pxn+k6uk kXH4G9YKqc+Ea+NVpSQ+h7FOqPlK7yGRLes04=
Received: by 10.141.43.19 with SMTP id v19mr76289rvj.115.1238690297603; Thu, 02 Apr 2009 09:38:17 -0700 (PDT)
Received: from ?10.10.111.233? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id k37sm3678264rvb.48.2009.04.02.09.38.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Apr 2009 09:38:17 -0700 (PDT)
Message-ID: <49D4E9F8.6050505@gmail.com>
Date: Thu, 02 Apr 2009 09:38:16 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Jason Giglio <gigstaggart@gmail.com>
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <49D4628B.9050207@gmail.com>
In-Reply-To: <49D4628B.9050207@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] OGP scalability concerns
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2009 16:37:17 -0000
Jason Giglio wrote: > My suggestion is that it's not appropriate to talk about client > identity, trust, or authentication as a service to be provided in a > centralized manner. > > Let's look at the text-based, non-interactive web: OpenID is a service, and it is "centralized" in the sense that an OpenID provider is a central service provider. E-mail is a service, and it is "centralized" in the sense that an e-mail address is centralized to that provider. When I sign up for a web site, typically I enter an e-mail address and a password, and I then have to click on a link sent to that e-mail address. This verifies that I am at least marginally reachable through that e-mail address. This establishes identity, albeit tenuous. However, if I want to show at amazon.com, I have to provide another identity: my credit card number. This is an identity with significantly higher bar to accreditation. Some sites, like those where there is legal ramifications to providing service to under-age visitors, actually use the credit card identity even for site access, because they have higher requirements on the identity they interact with. What, if anything, in this model do you think would be different for virtual worlds, when it is real-time 3D based? Sincerely, jw > The rest of the Internet gets along just fine without it. Sure I can > get a CA to sign something that says I am who I am, but no one much > cares; the rest of the net has routed around the problem of client > identification. I'm not sure why we would need to tackle something so > fundamentally difficult here, when it's not really necessary. > > -Jason > > ------------------------------------------------------------------------ > > _______________________________________________ > mmox mailing list > mmox@ietf.org > https://www.ietf.org/mailman/listinfo/mmox >
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Lawson English
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Jason Giglio
- Re: [mmox] OGP scalability concerns Rob Lanphier
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Meadhbh Hamrick (Infinity)
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Morgaine
- Re: [mmox] OGP scalability concerns Charles Krinke
- Re: [mmox] OGP scalability concerns Christian Scholz
- Re: [mmox] OGP scalability concerns Jon Watte
- Re: [mmox] OGP scalability concerns Hurliman, John
- Re: [mmox] OGP scalability concerns Christian Scholz