Re: [rtcweb] URIs for rtcweb "calls"

"Timothy B. Terriberry" <tterriberry@mozilla.com> Sun, 14 August 2011 11:47 UTC

Return-Path: <prvs=200d3d72f=tterriberry@mozilla.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD78A21F8853 for <rtcweb@ietfa.amsl.com>; Sun, 14 Aug 2011 04:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ilqHzJV6nENF for <rtcweb@ietfa.amsl.com>; Sun, 14 Aug 2011 04:47:10 -0700 (PDT)
Received: from mxip3i.isis.unc.edu (mxip3i.isis.unc.edu [152.2.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA5221F855B for <rtcweb@ietf.org>; Sun, 14 Aug 2011 04:47:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAN60R06sGgRS/2dsb2JhbABBpxKBXYFAAQEEAThAAQULCyEWDwkDAgECAUUTAQcCh2yyG4ZHBIdfkDAPjAk
X-IronPort-AV: E=Sophos;i="4.67,368,1309752000"; d="scan'208";a="149795901"
Received: from mr1a.isis.unc.edu (HELO smtp.unc.edu) ([172.26.4.82]) by mxip3o.isis.unc.edu with ESMTP; 14 Aug 2011 07:47:51 -0400
X-UNC-Auth-As: tterribe
X-UNC-Auth-IP: 71.87.145.153
Received: from [192.168.1.139] (71-87-145-153.static.hlrg.nc.charter.com [71.87.145.153]) (authenticated bits=0) by smtp.unc.edu (8.14.4/8.14.3) with ESMTP id p7EBkYXJ023492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rtcweb@ietf.org>; Sun, 14 Aug 2011 07:47:49 -0400 (EDT)
Message-ID: <4E47B595.1020508@mozilla.com>
Date: Sun, 14 Aug 2011 04:46:29 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101120 Gentoo/2.0.10 SeaMonkey/2.0.10
MIME-Version: 1.0
CC: rtcweb@ietf.org
References: <CA+9kkMBFwX9KiPDGwOZaANJuMO6J_wh06CPt+9+=y6iJL-hzXA@mail.gmail.com> <4E457915.7010809@skype.net> <CA+9kkMCP==SO8whDpfJ_BdHqvS=pg-iVXycfAqEJp+nZd=u1Pw@mail.gmail.com>
In-Reply-To: <CA+9kkMCP==SO8whDpfJ_BdHqvS=pg-iVXycfAqEJp+nZd=u1Pw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] URIs for rtcweb "calls"
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 11:47:10 -0000

> rtc-web context.  That would still fire up the full game context,
> slotting the user into the game (rather than making a phone call).

By "full game context" do you mean it would somehow load an http webpage 
with HTML+CSS+JS to handle the signaling? If that's the case, what 
advantages does this offer over normal http[s] URLs (with a path to the 
necessary page and parameters, etc. needed to carry sufficient 
information to establish the session). That certainly seems to already 
cover the case of, "A URI that I could use to paste into a chat window." 
How does it handle all the things that an http[s] URL already provides 
(port, path, caching, proxies, all the associated services built around 
http (e.g. bit.ly), etc.)?

If that's not the case, what do you mean by "context"?