Re: [rtcweb] API options for supporting fork with ROAP (Re: SDP Offer/Answer draft-jennings-rtcweb-signaling)

Iñaki Baz Castillo <ibc@aliax.net> Tue, 18 October 2011 13:30 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 86BCA21F8B6C for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 06:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level:
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_24=0.6, 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 21LdmxJB5o-H for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 06:30:07 -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 0A56221F8B63 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 06:30:06 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so594062vcb.31 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 06:30:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.120.12 with SMTP id b12mr179038vcr.111.1318944606455; Tue, 18 Oct 2011 06:30:06 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Tue, 18 Oct 2011 06:30:06 -0700 (PDT)
In-Reply-To: <4E9D7019.2020303@ericsson.com>
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <CAD5OKxvE77Fia1hVRhdmqnfsOExpdJq=J2VMwtsfB_7ztEYtLA@mail.gmail.com> <4E9D43D2.9010804@alvestrand.no> <CALiegfnaE4OX6QHkkr1k5+Ux2WUOixB+4=e52_+gpphM4HKi6w@mail.gmail.com> <4E9D5E9A.7090308@alvestrand.no> <CALiegfkPk=o0YvmUCocmUOeL_hp37UogeYkv9vE=KQqQESRcKg@mail.gmail.com> <4E9D7019.2020303@ericsson.com>
Date: Tue, 18 Oct 2011 15:30:06 +0200
Message-ID: <CALiegf=3dHhC1gt=YEH-=7mdi33cjKx74OMa65CxVDvsgRwUdQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: =?UTF-8?Q?Stefan_H=C3=A5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] API options for supporting fork with ROAP (Re: SDP Offer/Answer draft-jennings-rtcweb-signaling)
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, 18 Oct 2011 13:30:07 -0000

2011/10/18 Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>;:
> Our idea is basically that whenever you create a new PeerConnection in
> the same context as you have already created one or more
> PeerConnection's, the same local candidates should be re-used. Of course the
> 5-tuple must remain unique so that different connections don't collapse into
> one, but this is quite simple to resolve.
>
> For clarity, the above would be requirements on the implementation (in
> browsers).
>
> This means that support of forking would be simple as the IP+port's to
> send media to (for the remote end) remains also for the new PeerConnection.
>
> Another advantage is that creating new PeerConnections will be faster as new
> candidates does not need to be gathered.
>
> I think this is quite a clean solution since there is no need for API
> changes, or any additional factory layer.


Hi Stefan, that looks nice, but could you explain what does it mean
"in the same context as you have already created one or more
PeerConnection's"?

Could you please translate it into a theorical JS API?

Regards.


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