IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Sat, 15 October 2011 08:37 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 9E23421F8B1A for <rtcweb@ietfa.amsl.com>; Sat, 15 Oct 2011 01:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.111, 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 c75AEA+5EXCj for <rtcweb@ietfa.amsl.com>; Sat, 15 Oct 2011 01:37:06 -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 2471021F8B1F for <rtcweb@ietf.org>; Sat, 15 Oct 2011 01:37:04 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so1888053vcb.31 for <rtcweb@ietf.org>; Sat, 15 Oct 2011 01:37:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.117.81 with SMTP id p17mr896999vcq.41.1318667824288; Sat, 15 Oct 2011 01:37:04 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Sat, 15 Oct 2011 01:37:04 -0700 (PDT)
In-Reply-To: <5748C5EE-48D1-4D30-B0D2-8703C45972EE@acmepacket.com>
References: <AAE428925197FE46A5F94ED6643478FEA925614C6A@HE111644.EMEA1.CDS.T-INTERNAL.COM> <CALiegfkw=aA-4NrAG3U03suUYHAzQHyAWnNEbpRHcjd5xr3_KQ@mail.gmail.com> <ABB0E87F-DEEF-4386-A718-D48E00F5961A@acmepacket.com> <CALiegfnHuYJnX3rnuDGbZPB4NvK=dCTJ=iLcu+zguP5wo_uPqQ@mail.gmail.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> <5748C5EE-48D1-4D30-B0D2-8703C45972EE@acmepacket.com>
Date: Sat, 15 Oct 2011 10:37:04 +0200
Message-ID: <CALiegfkyDw1JfQD+Z=Xg_dZCwbvrr2hMs190R7gVoRphhjtwRQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.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: Sat, 15 Oct 2011 08:37:06 -0000

2011/10/15 Hadriel Kaplan <HKaplan@acmepacket.com>:
>> Ok, let me try again:
>>
>> IMHO RTCweb (specially the JS API for managing media sessions) must be
>> designed in a way that it's possible for a developer to implement a
>> SIP client in JavaScript or another custom signaling protocol having a
>> gateway that maps it to/from SIP. This means that SIP features as
>> parallel forking, early media, conference... should be possible using
>> the RTCweb JavaScript API. I think we agree here :)
>
> Right I think we do agree - I was under the impression you were saying we don't need to work with SIP.

Humm, taking into account that I'm involved in SIP over WebSocket to
make pure SIP (no protocol conversion) available for RTCweb... it
would be annoying that I wouldn't like to interoperate with SIP :)


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

v2.23.0 | Report a Bug | By Email