Re: [rtcweb] Minimal SDP negotiation mechanism

Iñaki Baz Castillo <ibc@aliax.net> Tue, 20 September 2011 13:21 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 73FCA21F8CA7 for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 06:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=0.028, 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 BJ4BgK93N9DE for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 06:21:19 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E381121F8CA1 for <rtcweb@ietf.org>; Tue, 20 Sep 2011 06:21:18 -0700 (PDT)
Received: by vws5 with SMTP id 5so798444vws.31 for <rtcweb@ietf.org>; Tue, 20 Sep 2011 06:23:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.69.18 with SMTP id a18mr611841vdu.430.1316525023456; Tue, 20 Sep 2011 06:23:43 -0700 (PDT)
Received: by 10.220.94.200 with HTTP; Tue, 20 Sep 2011 06:23:43 -0700 (PDT)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852233F6F291@ESESSCMS0356.eemea.ericsson.se>
References: <4E777500.5030201@alvestrand.no> <69262135-CF5D-4E79-85CD-82DFDC4250C0@acmepacket.com> <7F2072F1E0DE894DA4B517B93C6A05852233F6F222@ESESSCMS0356.eemea.ericsson.se> <CALiegf=r7t4b+Ov=UqhEZc7x2a9+Prdm3yuar+n156CYnyyrRw@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852233F6F291@ESESSCMS0356.eemea.ericsson.se>
Date: Tue, 20 Sep 2011 15:23:43 +0200
Message-ID: <CALiegfmqXoOjMN00Nyq-DXNZJ-Zs87WV95B1gneqHeGQMyyV7g@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Minimal SDP negotiation mechanism
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: Tue, 20 Sep 2011 13:21:19 -0000

2011/9/20 Christer Holmberg <christer.holmberg@ericsson.com>om>:
> The JS SIP app can decide that, but my point was that the JS SIP app needs to be able to "replace" the SDP answer with anohter one (received on another early dialog) - *IF* it chooses to do so.

Sure. That must be designed by the signaling layer. What I hope is
that such signaling layer is up to the JS code (optionally in form of
custom code or a given WebRTC JS API).



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