Re: [rtcweb] Signalling, SDP, and the way we think about interconnecting RTCWEB applications

Randell Jesup <> Mon, 17 October 2011 20:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA48F11E8073 for <>; Mon, 17 Oct 2011 13:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 90rN2fRRvIcw for <>; Mon, 17 Oct 2011 13:50:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D49AB21F8B79 for <>; Mon, 17 Oct 2011 13:50:20 -0700 (PDT)
Received: from ([] helo=[]) by with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <>) id 1RFu8X-00088a-Fi for; Mon, 17 Oct 2011 15:50:17 -0500
Message-ID: <>
Date: Mon, 17 Oct 2011 16:45:41 -0400
From: Randell Jesup <>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
References: <AAE428925197FE46A5F94ED6643478FEA925614C6A@HE111644.EMEA1.CDS.T-INTERNAL.COM> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
Subject: Re: [rtcweb] Signalling, SDP, and the way we think about interconnecting RTCWEB applications
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 17 Oct 2011 20:50:21 -0000

On 10/17/2011 1:10 PM, Wolfgang Beck wrote:
> On Mon, Oct 17, 2011 at 5:00 PM, Randell Jesup<>  wrote:
>> Ok, I looked at draft-beck-rtcweb-alt-ic.
>> One huge problem with it: it's based on an assumption that for most cases of
>> federation and cross-service calls won't hold: that clients will use the
>> same client JS app, and the services are just providing different
>> realms/methods of authentication and user-lookup.
>> Also, your draft doesn't explain how A&  B came to be talking to the same
>> server in the first place.  The draft seems mostly focused on how a single
>> provider can use a shared authentication scheme (and I would suggest that we
>> try to find a provider-agnostic way to leverage id systems such as BrowserID
>> and/or OpenID to provide end-user identification).
> Ok, here's an example that works today. Let's assume you have a yahoo
> account and want to post a comment on
> You just point your browser to the url [i.e. user
> location]. Now you log in using your yahoo account as OpenID. The
> browser loads the stackexchanges's JS client that enables you to post
> your text.  There is no comment-posting-protocol required between
> yahoo and
> stackexchange. They only have to agree on an 3rd party authentication protocol.

Right; you're talking entirely about open/shared ID systems (ala 
BrowserID, OpenID, Facebook login (ugh), etc).

> If stackexchange extends its functionality, let's say with real-time
> chat (which they did), your browser will load the appropriate JS
> client
> the next time you load the page.  All parties in the chat will use the
> same JS client under stackexchange's control, regardless whether
> people have
> used google, yahoo, or facebook to log in. There is no need to
> standardize anything that crosses stackexchange's servers.

You're making the argument that no federation is needed, because to 
contact someone on stackexchange you'd browse to stackexchange first.

I don't think that handles the use-cases of, from within say gmail, you 
try to call someone on Stackexchange - or even more unavoidable, you try 
to invite someone from stackexchange to join your already-running call. 
  You can't exit out and load the stackexchange JS client.

Randell Jesup