Re: [rtcweb] Facebook is not SIP

Iñaki Baz Castillo <ibc@aliax.net> Thu, 20 October 2011 09:46 UTC

Return-Path: <ibc@aliax.net>
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 DC1F021F8ADC for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.625
X-Spam-Level:
X-Spam-Status: No, score=-2.625 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 cWv26U6KWbRk for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 02:46:43 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4802D21F84F8 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 02:46:43 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so2739916vcb.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 02:46:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.117.81 with SMTP id p17mr724060vcq.41.1319104001649; Thu, 20 Oct 2011 02:46:41 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Thu, 20 Oct 2011 02:46:41 -0700 (PDT)
In-Reply-To: <4E9FEA28.10900@alvestrand.no>
References: <CALiegfmWebR6pJCpCYhH3YWNTqnfENXU_uiu1Db5joM-RSrVAQ@mail.gmail.com> <4E9FEA28.10900@alvestrand.no>
Date: Thu, 20 Oct 2011 11:46:41 +0200
Message-ID: <CALiegfkWu2q4JFQNKON_LTvng2vnpJ3pMGwQnbjrDBwsGcm37Q@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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:46:44 -0000

2011/10/20 Harald Alvestrand <harald@alvestrand.no>;:
> 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/

It changes nothing. If RTCweb decides a standard in-the-wire signaling
protocol different than XMPP we are also forcing facebook to use a
protocol different than XMPP for audio/video signaling (in-the-wire).

Anyhow, this is what I capture from the network when I send a IM
message ("hello") to other user visiting Facebook website:

---------------------
POST /ajax/chat/send.php?__a=1 HTTP/1.1'
Host: www.facebook.com'
User-Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:10.0a1)
Gecko/20111017 Firefox/10.0a1'
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8'
Accept-Language: en-us,en;q=0.5'
Accept-Encoding: gzip, deflate'
DNT: 1'
Connection: keep-alive'
X-SVN-Rev: 460802'
Content-Type: application/x-www-form-urlencoded; charset=UTF-8'
Referer: http://www.facebook.com/?sfrm=1'
Content-Length: 399'
Cookie: datr=ZuyfTjurvmsqvYVBDcXF8u; c_user=104442654509775; L=2;
lu=RgQytVtJJBQSvWUNOYzs0oQg; sct=1319153603;
xs=60%3A1c179a6dfb7f08277477b20e778bd391; p=112;
presence=EM319103631L212REp_5f1B04654409875F4EriF0CEstateFDutF1319103633096EvisF1H0EblcF0EsndF1ODiFA21B02602687525A2C_5dEfFA21B02602687525A2EuctF1319103618EsF0CEblFD55F1G319103604PEuoFD1B02602687525FDexpF1319103680370EflF_5b1_5dEolF0CCEalFD1B02602687525FDiF0EmF0CCCC;
wd=1366x675'
Pragma: no-cache'
Cache-Control: no-cache'
'
msg_id=1319103647568%3A3620978310&client_time=1319103646048&to=100002772687525&num_tabs=1&pvs_time&msg_text=hello&to_offline=false&to_idle=false&window_id=2877189837&sidebar_launched=true&sidebar_enabled=true&sidebar_capable=true&sidebar_should_show=false&sidebar_visible=false&post_form_id=449eb730c851e127f21d8a88b6a00667&fb_dtsg=AQC3StlW&lsd&post_form_id_source=AsyncRequest&__user=100002654409995
---------------------


Could you explain me where do you see "XMPP" there? Please note that
I'm speaking about the in-the-wire signaling between the webbrowser
and the server, and the above HTTP POST is the signaling message
Facebook is using for sending a IM.




> Unfortunately Facebook has chosen (so far) to not participate in federation.

Federation does not matter here. I'm just speaking about the
in-the-wire signaling protocol between web users visiting Facebook
website. Federation is another topic IMHO.


> Rest of message deleted, since it's based on a false premise.

Which premise?


Regards.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>;