Re: [rtcweb] media rollback and glare

Justin Uberti <juberti@google.com> Thu, 08 August 2013 20:35 UTC

Return-Path: <juberti@google.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 78B0B11E81F0 for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 13:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 m+SMu+3fmMsZ for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 13:35:02 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5B27311E8221 for <rtcweb@ietf.org>; Thu, 8 Aug 2013 13:35:00 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 17so2782403iea.17 for <rtcweb@ietf.org>; Thu, 08 Aug 2013 13:34:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=e2ZQpBmrMH6NUqRmYNKcIlgUkyHmelZNOLU5dVBEmHs=; b=l7ZE6FLj/32VP+vLep1+aj/pSASB6bUg8JeDGdMHRDhCh3FbKt62nHm1xe1scyEVkm H1y1rBBNgAHdNvWFMoQFzaJgc/Ob6exyZ0sMTJavv0tHdwNdvFP4vNuaJe7EXHmZK/V/ FPv2w0D2sFYlxCLkqWAUpEfktSLraol2YCmmjK7aQSFbmU1bUgFic9Au8uVSawYRWBfc fT+7MpaZ3dRbixDuSB0nwv9eXQVq6cH8Opzq2s7iVuPwUQp2oALMOLaPgXBZa3OjnuZj IthRBPY9nZ35YUzSVGzTWZYrya4Y/hbGwlUS9RtoABYmX7X8FuNaxZdUnz+OJS+H3c8I vMCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=e2ZQpBmrMH6NUqRmYNKcIlgUkyHmelZNOLU5dVBEmHs=; b=ZDcXXbuq0xHlhc1lGfooBxSHVg+qlwndcRh2hUTFTkbLa8FUAXaooNDisCf1PZgWGo 2Xfm/C2VVJiX/+BWJXKNjGMG7WoOKwZi6PVAkgHnUbD3R59ULYJ/N9uJNIKm1JaMYKhf IVEdiVbXJUskwdM47HnlsMEK/Bt5scdjcWjUkV3EzK3hq3Er3I/Q4QoEjZs0gEGKHPBt 24xXaVg9Q34FnVrSjuhtYkEGgZbzGIWACvaNPziGC5+Q/PAFE2pw5PYn7gdMk1XZTIWh bFYUlcDu1JOPBTEwIvrXF2WE/MU9iTmy2TPPD2tHmiFA+zKI8QyvswfxpFHcjd9U2kyu EZwg==
X-Gm-Message-State: ALoCoQl1hmofKgnxQEoOqTV2hqLbLpu6i2Yzylla3oHYhGlAiZ6n1XBpndQBEAYnisuNctuX3L0NevcvmW5Ec7RvPncFyiTS/SsHyxFqMRFnsIPmyidekP0IXhHXujyc6t0Iwwb8XdAXkOhtQgZ42MFRrV+ZkxFEWiLTfp8RfOgUD6wdH0D3yuDIptLWIwqhziPzLcG4VTqE
X-Received: by 10.50.129.38 with SMTP id nt6mr468690igb.16.1375994099741; Thu, 08 Aug 2013 13:34:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.97.132 with HTTP; Thu, 8 Aug 2013 13:34:39 -0700 (PDT)
In-Reply-To: <56C2F665D49E0341B9DF5938005ACDF80D33B9@DEMUMBX005.nsn-intra.net>
References: <dadb4585c9f0234ee8b370876873cd05@mail.gmail.com> <56C2F665D49E0341B9DF5938005ACDF80D33B9@DEMUMBX005.nsn-intra.net>
From: Justin Uberti <juberti@google.com>
Date: Thu, 8 Aug 2013 13:34:39 -0700
Message-ID: <CAOJ7v-3obGa5ZugJBW599z8UkcSF7iVa-Kw56sE8rzBmCMYOag@mail.gmail.com>
To: "Rauschenbach, Uwe (NSN - DE/Munich)" <uwe.rauschenbach@nsn.com>
Content-Type: multipart/alternative; boundary=047d7b41426c87585704e3759783
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] media rollback and glare
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, 08 Aug 2013 20:35:03 -0000

The thinking has been to pass in a SessionDescription of type "rollback" to
the API. See 4.2.3.2 in http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-03
.


On Thu, Aug 8, 2013 at 7:51 AM, Rauschenbach, Uwe (NSN - DE/Munich) <
uwe.rauschenbach@nsn.com> wrote:

> Hi,
>
> +1
>
> In the Open Mobile Alliance, a REST API is being defined, intended to be
> exposed by a gateway that offers WebRTC access to IMS (or even PSTN).
> For that work, it is also necessary to understand how rollback will work
> in the PeerConnection API.
>
> Kind regards,
> Uwe Rauschenbach
>
> --
> Dr. Uwe Rauschenbach
> Senior Specialist
> NSN, Technology & Innovation
> St.-Martin-Str. 76, D-81541 Munich, Germany
> Tel.: +49 89 5159 29751
> Mobile: +49 173 3083573
>
> Nokia Siemens Networks Management International GmbH
> Geschäftsleitung / Board of Directors: Andreas Sauer, Ralf Dietzel
> Sitz der Gesellschaft: München / Registered office: Munich
> Registergericht: München / Commercial registry: Munich, HRB 198081
>
> --------------------------------------------
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf
> Of ext Andrea Dixon
> Sent: Thursday, August 08, 2013 12:17 PM
> To: rtcweb@ietf.org
> Subject: [rtcweb] media rollback and glare
>
> The Webrtc spec states:
> "This API changes the local media state. In order to successfully handle
> scenarios where the application wants to offer to change from one media
> format to a different, incompatible format, the RTCPeerConnection must be
> able to simultaneously support use of both the old and new local
> descriptions (e.g. support codecs that exist in both descriptions) until a
> final answer is received, at which point the RTCPeerConnection can fully
> adopt the new local description, or roll back to the old description if the
> remote side denied the change.
> Issue 8
> ISSUE: how to indicate to roll back?"
> When will rollback be added to webrtc? Is it imminent? We need it to
> resolve glare scenarios where both peers renegotiate at the same time. Or
> is there another way of resolving glare in webrtc? This is becoming a
> pressing concern.
> Regards
>
>
> --------------------
> Note: The information contained in this message may be privileged and
> confidential
> and protected from disclosure. If the reader of this message is not the
> intended
> recipient, or an employee or agent responsible for delivering this message
> to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or
> copying of this communication is strictly prohibited. If you have received
> this
> communication in error, please notify us immediately by replying to the
> message and
> deleting it from your computer. Thank you. Thrupoint, Inc.
> nXaR2cC3
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>