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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 17 October 2011 17:25 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 0CFAC21F8CCA for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 10:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level:
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.083, 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 LRTZTakWDnKH for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 10:25:08 -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 6F91121F8CC7 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 10:25:08 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3334465vcb.31 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 10:25:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.25.75 with SMTP id a11mr21159752vdg.1.1318872307956; Mon, 17 Oct 2011 10:25:07 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Mon, 17 Oct 2011 10:25:07 -0700 (PDT)
In-Reply-To: <CAAJUQMgJ1wif-gNWvaM6XBzg_JK2Y6w0B7Mn_9qZdnz7B7scgQ@mail.gmail.com>
References: <AAE428925197FE46A5F94ED6643478FEA925614C6A@HE111644.EMEA1.CDS.T-INTERNAL.COM> <92A553E5-107A-4987-A5F5-1F56FB5A7800@acmepacket.com> <CALiegfn6nv1D2HjeMo-jPDh9Acph7JdH1DT1xZXUtHqzqxya3Q@mail.gmail.com> <CA+9kkMB3p1u7hRX_vO1bQbQ2z-V+0rLiJmi+ZqkEA0mqc66keQ@mail.gmail.com> <CALiegf=26_6r_YjBCmO+6_GnrAzi=KcLoPFqUi-y1E8m_gWreQ@mail.gmail.com> <CA+9kkMDsWyKdvXSRMV0OGEeEYbSENFHSOovNJDUGK30N_pGrnQ@mail.gmail.com> <CABRok6nsVH5tYfwFqQpmjF=Kj-wZQDB9XUX8oOee8r3wr51fKA@mail.gmail.com> <CAAJUQMg79h1=V4m9agq9CcEmFknTaaXrgUz9qtq9EL-0_nChiQ@mail.gmail.com> <4E996E80.6070500@alvestrand.no> <CABRok6k=8wa_K7X+MHwaii+6ANfTquLqauMKgm7KP82wf6pKyA@mail.gmail.com> <8486C8728176924BAF5BDB2F7D7EEDDF3E0906A2@ucolhp4d.easf.csd.disa.mil> <CAAJUQMjsRu=eQic002-T-V0rK=1ByRUD8vV2_+C3Q-cHf-ZL4g@mail.gmail.com> <CAAJUQMiV0-w7QBpWk1dc+BprM0T1MiKt-yuH7V9YyZ=vwD=z7Q@mail.gmail.com> <4E9BA235.3010808@jesup.org> <CAAJUQMjx3KnAqqFbEzzKBw_QMa48+yokQ8U4wemMGGVQhOepCg@mail.gmail.com> <4E9C430A.1070600@jesup.org> <CAAJUQMgJ1wif-gNWvaM6XBzg_JK2Y6w0B7Mn_9qZdnz7B7scgQ@mail.gmail.com>
Date: Mon, 17 Oct 2011 19:25:07 +0200
Message-ID: <CALiegfk=5eKh72wLOWoBwX9dSGHLSZjgMyypEzkm-DCKgtGa9A@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Wolfgang Beck <wolfgang.beck01@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] Signalling, SDP, and the way we think about interconnecting RTCWEB applications
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: Mon, 17 Oct 2011 17:25:09 -0000

2011/10/17 Wolfgang Beck <wolfgang.beck01@googlemail.com>;:
> Now you want to make a comment on some blog at blogspot.com. You point
> your browser at the blog's URL and log in using your Yahoo OpenID.
> The browser loads blogspot's JS client. The GUI looks quite different
> but you can post your comment as well.

Exactly. Some people has argued that getting a different GUI is bad,
but this is not about telephony world in which each person has a
phone. This is about communicating with different services each one
providing different features and capabilities so it does not make
sense at all to share the same GUI for RTCweb communication with a
second website.


> With the current RTCWEB thinking, we would have to specify an intra
> server protocol that covered stackexchange's discussion and chat
> systems as well as blogspot comments. Such a protocol would soon get
> very complex.

Agreed.

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