IETF Logo Mail Archive

Re: [rtcweb] Facebook is not SIP

Harald Alvestrand <harald@alvestrand.no> Thu, 20 October 2011 09:52 UTC

Return-Path: <harald@alvestrand.no>
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 AF75121F8B7B for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.572
X-Spam-Level:
X-Spam-Status: No, score=-110.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 b9S1sQtIb4O8 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:52:39 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 025D121F8532 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 02:52:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 47EC939E0F3; Thu, 20 Oct 2011 11:52:38 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2LzOCm9F+CA5; Thu, 20 Oct 2011 11:52:35 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 7BB4C39E072; Thu, 20 Oct 2011 11:52:35 +0200 (CEST)
Message-ID: <4E9FEF63.4000606@alvestrand.no>
Date: Thu, 20 Oct 2011 11:52:35 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Tim Panton <tim@phonefromhere.com>
References: <CALiegfmWebR6pJCpCYhH3YWNTqnfENXU_uiu1Db5joM-RSrVAQ@mail.gmail.com> <4E9FEA28.10900@alvestrand.no> <094BC958-085C-4A8B-9ED0-F1C8B1735191@phonefromhere.com>
In-Reply-To: <094BC958-085C-4A8B-9ED0-F1C8B1735191@phonefromhere.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Facebook is not SIP
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: Thu, 20 Oct 2011 09:52:39 -0000

On 10/20/11 11:39, Tim Panton wrote:
> On 20 Oct 2011, at 10:30, Harald Alvestrand wrote:
>
>> On 10/20/11 11:23, Iñaki Baz Castillo wrote:
>>> Hi all,
>>>
>>> When two Facebook users chat via web, they are already using a
>>> signaling protocol in-the-wire, which one? The *custom* signaling
>>> protocol Facebook designed.
>> They're using XMPP: https://developers.facebook.com/docs/chat/
> Yes, they are using XMPP - but are they using it to the browser or only for interop? The
> document does not say, and I haven't wiresharked the traffic to see,
> at the very least I imagine they are running it over http / websockets.
I stand corrected; they are running their own protocol between the 
browser and their servers.
As does Google, for that matter, even though our backends are XMPP-based.

Sorry for going off half-baked.

           Harald

v2.23.0 | Report a Bug | By Email