Re: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP

Martin Thomson <martin.thomson@gmail.com> Thu, 10 May 2012 17:03 UTC

Return-Path: <martin.thomson@gmail.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 3AD5721F86F4 for <rtcweb@ietfa.amsl.com>; Thu, 10 May 2012 10:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.739
X-Spam-Level:
X-Spam-Status: No, score=-3.739 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, 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 oSM+GaA13H1m for <rtcweb@ietfa.amsl.com>; Thu, 10 May 2012 10:03:45 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id C7C9721F86BD for <rtcweb@ietf.org>; Thu, 10 May 2012 10:03:40 -0700 (PDT)
Received: by bkty8 with SMTP id y8so1751855bkt.31 for <rtcweb@ietf.org>; Thu, 10 May 2012 10:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WNoIM+0is5Cgm54vDxXJnwnfsuSc0MYhh7LoEyxGcMY=; b=aZ9ePad5/wvbCb8izsqvbN2YEe1rRguBn2IsbIy7f8znBZGJZBG3UK58oA7y50A7kE jrCywAgE94MJIIm4mGIEG4u1HEOMJE6A5kw3pUOJfKfkZhlj5PeUTmCtPZdYFDKxfB/Z F3JMi9VM8gQGNch+DsZxqCXbYY5t/jPdRefuvwbYtG9LPgExKVZj2B+oaIQgNX6baT2H Vqk3QHTUilSC5I6U150JHZtzX8l+3PDqUtWYhHEuiVhbCP79o3bRUA+iwc8BuJUeC9gu bb4U22Vrou4mh3boMsQUR0L68imMsarGv5+dgCNvt572ae5l70ZgbMZyCUe8qv7AplBs DipA==
MIME-Version: 1.0
Received: by 10.204.149.216 with SMTP id u24mr3041223bkv.36.1336669419862; Thu, 10 May 2012 10:03:39 -0700 (PDT)
Received: by 10.204.185.205 with HTTP; Thu, 10 May 2012 10:03:39 -0700 (PDT)
In-Reply-To: <BEC86C2A-B983-4230-A997-A39CF4205CCD@iii.ca>
References: <387F9047F55E8C42850AD6B3A7A03C6C0E23B102@inba-mail01.sonusnet.com> <6F428EFD2B8C2F49A2FB1317291A76C1136029362A@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <4FA13816.6050003@alvestrand.no> <CAD5OKxsOAeTRdCgj2g4BY8maeG1n9nzCv29g8kaFPVZ4tf8C5w@mail.gmail.com> <4FA15898.1040204@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A05852C44001329@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxsbTSpMPg30P4DSN6UasCx6na43tpZ5yT2ct6SLMpd9xQ@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400132C@ESESSCMS0356.eemea.ericsson.se> <6F428EFD2B8C2F49A2FB1317291A76C1136047B753@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400132F@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuy8_Ras3X-8tcY1qaLRTVJ-z-JuXQaf0NKaRwN_dU18Q@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C442AC0DA@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuv7T6YrEXEeVECKbGtRg4feoRYTgvC57yqWXTBK43ypg@mail.gmail.com> <4FA2B447.7010504@jesup.org> <4FA2E264.4040207@jesup.org> <CAD5OKxs3AqvbookWYPDgOuAkjPZGVUdSEhqz6P_p9E4h_ZHJGQ@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C44001338@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuq14_DfSJuFEHq_ZEubbOYt7NFTcXWpLND8ggAr37QhA@mail.gmail.com> <BEC86C2A-B983-4230-A997-A39CF4205CCD@iii.ca>
Date: Thu, 10 May 2012 10:03:39 -0700
Message-ID: <CABkgnnX3KNoiQbjDrUAh0WOv8Ozbhemr95P_fMe-qmFEAeZbPw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Randell Jesup <randell-ietf@jesup.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP
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: Thu, 10 May 2012 17:03:46 -0000

On 10 May 2012 07:13, Cullen Jennings <fluffy@iii.ca> wrote:
> The initial media flow could be forced to provide only relay ICE candidates to help mitigate this. (I think we decided awhile back that was one of the things we would provide support for in the API). Later with the user answers or consents in same way, the ICE can move the media to a non relay flow.

That's right.  But you pretty much have to leave this in the hands of
the application.

Unless you want to provide an authenticated indication of user answer
on the media path so that when the user picks up the phone you can
provide other local candidates...