Re: [mmox] OGP scalability concerns

Jon Watte <jwatte@gmail.com> Thu, 02 April 2009 21:43 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 607223A6B39 for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 14:43:58 -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 ykUI1hgDWPOo for <mmox@core3.amsl.com>; Thu, 2 Apr 2009 14:43:57 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by core3.amsl.com (Postfix) with ESMTP id AC9C73A6896 for <mmox@ietf.org>; Thu, 2 Apr 2009 14:43:57 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id k40so732463rvb.49 for <mmox@ietf.org>; Thu, 02 Apr 2009 14:44:59 -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=FC524cDYiJ688IC1ad37JhdFDPcMY9gWIVz/+tWm5xk=; b=WaS+1UTQexDwCjBeCQRNjHDtAw/7Iga40ieGd5lh0ta6+UeA1socgDp4MZr42Ai6dm SH905FyX/uYr4McEZ7hAt0IrUBVcH3AwMoxabW9HGCQkv8xMQsBxsQ8QLTUwd7EWYi71 euh2Hg+Eqj9VwqEuXUAuyHNC1CaiExm0uDrkQ=
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=W4n4U42dvRDKLRd0AbO6ccOppATTiRPesPtXXXz0dk6VnNhK2np0u/9wnaMhM7t9g8 r1iD8ShT2I0QlOB7b2RNNJVAY1droBSAMXlAUTI5BgpYkYnnROzIzekjTt62isfqQ37l lf46k4oXjg0VehBcS+/Lut8RpUWoWvn3iz+LY=
Received: by 10.141.101.12 with SMTP id d12mr166934rvm.240.1238708699539; Thu, 02 Apr 2009 14:44:59 -0700 (PDT)
Received: from ?10.10.111.233? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id f21sm4469097rvb.25.2009.04.02.14.44.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Apr 2009 14:44:59 -0700 (PDT)
Message-ID: <49D531DA.4080006@gmail.com>
Date: Thu, 02 Apr 2009 14:44:58 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Christian Scholz <cs@comlounge.net>
References: <62BFE5680C037E4DA0B0A08946C0933D7B692E1B@rrsmsx506.amr.corp.intel.com> <CD02023C-3E7B-4E76-8429-11035C827E53@lindenlab.com> <f0b9e3410904011701i2ccb03d4r1b48d33cfe3988ea@mail.gmail.com> <49D40A06.7030708@gmail.com> <8D793BD8-6AA2-49C7-96EF-435A5B449AA6@lindenlab.com> <49D4295C.2020502@gmail.com> <52A129B8-3FC6-486A-99A5-C00BED8BDE08@lindenlab.com> <49D4E5AF.2030301@gmail.com> <49D51A7D.8000104@comlounge.net> <62BFE5680C037E4DA0B0A08946C0933D7B6934A3@rrsmsx506.amr.corp.intel.com> <49D52DCD.2000806@comlounge.net>
In-Reply-To: <49D52DCD.2000806@comlounge.net>
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 21:43:58 -0000

Christian Scholz wrote:
> Another option would be to join forces with the OAuth group at IETF 
> and check on how we could add identity to OAuth (there is discussion 
> about that already). Eventually this might be an easier choice and you 
> could do authorization in one step, at least for some centralized 
> services.

The first question is: does the OAuth "callback" URL work in a VW sense? 
At a minimum, this means that a VW needs to have a publicly available 
*incoming* URL for receiving authentication tokens. For a VW behind a 
firewall, that's not necessarily true. (Then again, OAuth doesn't work 
for an intranet web site behind a firewall, either)

Sincerely,

jw