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

Roman Shpount <roman@telurix.com> Tue, 18 October 2011 16:07 UTC

Return-Path: <roman@telurix.com>
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 75CD121F8C0F for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 09:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 kC4XNMSuEBwi for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 09:07:18 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id F1D4A21F8C0C for <rtcweb@ietf.org>; Tue, 18 Oct 2011 09:07:15 -0700 (PDT)
Received: by ywa8 with SMTP id 8so905076ywa.31 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 09:07:15 -0700 (PDT)
Received: by 10.68.1.230 with SMTP id 6mr6000998pbp.27.1318954035100; Tue, 18 Oct 2011 09:07:15 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by mx.google.com with ESMTPS id ji3sm8668608pbc.2.2011.10.18.09.07.12 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Oct 2011 09:07:13 -0700 (PDT)
Received: by pzk34 with SMTP id 34so1997772pzk.9 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 09:07:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.8.233 with SMTP id u9mr5917408pba.30.1318954032379; Tue, 18 Oct 2011 09:07:12 -0700 (PDT)
Received: by 10.68.47.40 with HTTP; Tue, 18 Oct 2011 09:07:12 -0700 (PDT)
In-Reply-To: <4E9D85CB.6030503@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> <CALiegf=3dHhC1gt=YEH-=7mdi33cjKx74OMa65CxVDvsgRwUdQ@mail.gmail.com> <4E9D85CB.6030503@ericsson.com>
Date: Tue, 18 Oct 2011 12:07:12 -0400
Message-ID: <CAD5OKxtRygfzAYviKPyDxeZGt2ajXFQHr9WGdqiR24MbC3j2Cw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Content-Type: multipart/alternative; boundary="bcaec5215a5993366604af94eaf9"
Cc: "rtcweb@ietf.org" <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 16:07:18 -0000

On Tue, Oct 18, 2011 at 9:57 AM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> What I mean is: if this web app has already created a PeerConncection, and
> is about to open another one (e.g. for a new fork), the new PeerConnection
> should use the same local candidates as the one already created collected.
>
>
What would happen if new PeerConnection has a different set of codecs/media
streams? Do we just add/remove local candidates based on how many different
streams are needed?

Overall I do like this idea since it not only addresses the forking issue,
but suggest a good resource usage policy.
_____________
Roman Shpount