Re: [rtcweb] JSEP-03: O/A state machine and trickle ICE with forking

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 01 March 2013 11:24 UTC

Return-Path: <christer.holmberg@ericsson.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 7E46421F89B2 for <rtcweb@ietfa.amsl.com>; Fri, 1 Mar 2013 03:24:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.247
X-Spam-Level:
X-Spam-Status: No, score=-6.247 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBASpug0PI14 for <rtcweb@ietfa.amsl.com>; Fri, 1 Mar 2013 03:24:25 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id C092121F89E2 for <rtcweb@ietf.org>; Fri, 1 Mar 2013 03:24:24 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-f3-51308fe76347
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 74.0A.10459.7EF80315; Fri, 1 Mar 2013 12:24:23 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.82]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 12:24:23 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] JSEP-03: O/A state machine and trickle ICE with forking
Thread-Index: Ac4VKEWZ4cYZzPT+TXSns1oyaegaDgAGp8mAAA6+H/AAH3olAAAZtDSAAALeZcA=
Date: Fri, 01 Mar 2013 11:24:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B10DF97@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B10B6DE@ESESSMB209.ericsson.se> <CAOJ7v-0UTceYRjiTL2tPWhnJ914dsk54MYd1vvXAGLmp8ByztQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B10B98F@ESESSMB209.ericsson.se> <CAOJ7v-1VMjQ01J2vxJdwt0M7O7LiBeLLxDeUxCiKp4JRDH+ofA@mail.gmail.com> <51308899.9050802@alvestrand.no>
In-Reply-To: <51308899.9050802@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvje7zfoNAg9tzrC2O9XWxWaz9187u wORxZcIVVo8lS34yBTBFcdmkpOZklqUW6dslcGXsPfWXteCvQMXGjcdYGhjPcncxcnJICJhI tB7YzAxhi0lcuLeerYuRi0NI4BCjxKZ7PSwQziJGielP/gA5HBxsAhYS3f+0QRpEBIIlep+/ ZwSxhQV8JW4eXssEEQ+QONHynxXC9pOY9fYX2AIWARWJVX/ng8V5Bbwlrr6byggxfx+TxJaV j1hAEpwCuhLXX85nB7EZgS76fmoN2FBmAXGJW0/mM0FcKiCxZM95qKtFJV4+/scKYStKXJ2+ HKpeT+LG1ClsELa2xLKFr5khFgtKnJz5hGUCo+gsJGNnIWmZhaRlFpKWBYwsqxjZcxMzc9LL DTcxAqPh4JbfujsYT50TOcQozcGiJM4b5nohQEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAMj 853PQkrz6wzWHF6aHbs7bNKWszL7Z+zjO3pY44KTZJyQoUW6ZJOtkO7ZOdI62trRfNn+qs4r LIO3hnXfm1p85m+s7gzec1Plr1yOnMB7jj/xkJW0/wY9//xZ/Ey2j5JWPGtSf1jM/Fxa5OmJ b2nmk7b93uflbhCy6azTncIeHh6nr2Xzw08rsRRnJBpqMRcVJwIAhm9tV1QCAAA=
Subject: Re: [rtcweb] JSEP-03: O/A state machine and trickle ICE with forking
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: Fri, 01 Mar 2013 11:24:26 -0000

Hi Harald,

>My understanding is that the mismatch is that the JS APP isn't giving a consistent story to the browser on whether the answer was final or not.
>This sequence would work:
>
>BROWSER                         JS APP                                    REMOTE ENITTY
>
>    ------ create offer ----------
>                                             -------- SDP Offer 1----------------->
>                                            <------- SDP Answer 1 ----------------
>    ------ set remote pranswer(1) ---------
>                                            <------- SDP Offer 2 -------------------
>    ------ set remote answer(1) -----
>    ------ set remote offer(2) -----
>
>that is, when the JS app gets the information that there's a new offer incoming, it realizes that Answer 1 needs to be treated as a final answer, and finalizes it before passing in the new offer.

The problem with such approach is that it will terminate forking, i.e. it will not be possible to pass an SDP Answer from ANOTHER remote entity to the browser.

BROWSER                         JS APP                                    REMOTE ENTITY A         REMOTE ENTITY B

    ------ create offer ----------
                                             -------- SDP Offer 1----------------->
                                            ------- SDP Offer 1 ---------------------------------------------------->
                                            <------- SDP Answer 1 (A) -----------
    ------ set remote pranswer(1) ---------
                                            <------- SDP Offer 2 (A) --------------
    ------ set remote answer(1) -----
    ------ set remote offer(2) --------
                                            <------ SDP Answer 1 (B) ---------------------------------------------
    ------ ???? ----------------------------



Regards,

Christer