Re: [mmox] OGP scalability concerns
Jon Watte <jwatte@gmail.com> Fri, 03 April 2009 04:39 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 614663A6A17 for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 21:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 J3fzrp5bTsSA for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 21:39:44 -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 7C94E3A68F8 for <mmox@ietf.org>; Thu, 2 Apr 2009 21:39:44 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id k40so856343rvb.49 for <mmox@ietf.org>; Thu, 02 Apr 2009 21:40:46 -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=1A0LjZWOY+doLKfFMhbMV46u+DRSCJW+R6EWalIjVkg=; b=nM3jVUxNCADGE9+AMoDbDd6vsK+2G3Ve17L2PUvVMd//onCmVC35MzWUbeOAcJj5di g8udyaq6lU1nSMmf1tIPnOWClAD/kBxdwxZQwBAoPRkk16w7ek1E6a7Qy4sNTyDOTpgI J1v7Y/zfLDtH/cf0xMRaZ37VgccVHrD77MKT4=
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=G0KYJ668h+Z6iluxh1oNiVJGLd+6HNlF2dIEDKzYoMUkT3WMcZ9ZuSl04GNlKFxL0J HH7WSW1Im+tpeHvUp/PzVbv6Ifmxrafugz2bkv5vNs9dqwekH6QByY7gvXaPVkfcJgqA 9y5hIa7i7whFw5nzWsOQQt8tHZIR90tdxcBoY=
Received: by 10.114.177.1 with SMTP id z1mr385723wae.68.1238733646678; Thu, 02 Apr 2009 21:40:46 -0700 (PDT)
Received: from ?192.168.1.101? (svn.mindcontrol.org [69.17.45.136]) by mx.google.com with ESMTPS id j34sm1811754waf.27.2009.04.02.21.40.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Apr 2009 21:40:46 -0700 (PDT)
Message-ID: <49D5934D.6020406@gmail.com>
Date: Thu, 02 Apr 2009 21:40:45 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <49D4628B.9050207@gmail.com> <3C59C4AA-CD4F-456D-83B5-35DC9DEAE4A7@lindenlab.com>
In-Reply-To: <3C59C4AA-CD4F-456D-83B5-35DC9DEAE4A7@lindenlab.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: Fri, 03 Apr 2009 04:39:45 -0000
Meadhbh Hamrick (Infinity) wrote: > to date, the proposed use of X.509 has been to identify agent domains > to region domains and region domains to each other. i don't think > we're proposing the use of client certs for client applications to > authenticate themselves to agent domains. or rather... no one's > talking about REQUIRING it. as an option, it's perfectly fine, though > a touch difficult to manage. I think that authentication comes in two flavors: Authenticating users, and authenticating entities that authenticate users. If you will, OAuth authenticates users, but how do you know who the OAuth provider is? That may be a separately established trust, that may be negotiated, or may be untrusted-but-traceable. i would argue that there _are_ in fact OpenSim operators who would want to connect to linden servers and consume linden services. I agree. However, there may also be operators who want to consume some Linden services, and some other services. Thus, it makes sense in that context, like John claims, to un-bundle each service. If the protocol allows you to discover multiple services in one go, and even authenticate for multiple services in one go, that's probably fine (and maybe even desired), but there shouldn't be anything in the protocol that requires all the services to come in one bundle. Even if some providers can provide them all in a bundle, the user probably will want to un-bundle them in certain cases. Sincerely, jw
- 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