[rtcweb] media rollback and glare

Andrea Dixon <adixon@thrupoint.com> Thu, 08 August 2013 10:16 UTC

Return-Path: <adixon@thrupoint.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 50BFE21E8055 for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 03:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level:
X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 3LpOp4wpUhay for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 03:16:40 -0700 (PDT)
Received: from eu1sys200aog124.obsmtp.com (eu1sys200aog124.obsmtp.com [207.126.144.157]) by ietfa.amsl.com (Postfix) with SMTP id 9BBDE21F9CA1 for <rtcweb@ietf.org>; Thu, 8 Aug 2013 03:16:39 -0700 (PDT)
Received: from mail-qc0-f172.google.com ([209.85.216.172]) (using TLSv1) by eu1sys200aob124.postini.com ([207.126.147.11]) with SMTP ID DSNKUgNwABYUqFlpUf2q98kfcw1EYcz/PX4g@postini.com; Thu, 08 Aug 2013 10:16:39 UTC
Received: by mail-qc0-f172.google.com with SMTP id a1so1461074qcx.31 for <rtcweb@ietf.org>; Thu, 08 Aug 2013 03:16:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=awgzcXRQhM5qtZ8queynXGJe5iMHnHjCtqugjpq/mCo=; b=Cxx1fqrqtU51NZj6dAFTUrBOjQ+KCiOj4f4Mc5H4ePWYy1V+iyrpocHCVojkHb5GKH QtK91hXJDEHAmTqb8L608KPDiKnJ6bY480fnz0fnnDn2QTG0Wfaoin89pAtBonnIk+n1 GKVaBA4YK7xKOTD/eJujPFX4KwqPAocp2Htvu0xaBksz3MIShMPkPHZGzRu/byzIG0Uk LwoMoDCHoq0YxAHVjTBLsoUDSht84xSSNWdbwOYAEpPSyZdusUVzmwUwyU61aOxdjF0+ /VooULLidbfethu4jcmS15voXpB4nEIvO53mf28cRb+VagaM7Ys+zKrpZp94p8iYoHFS PgnQ==
X-Gm-Message-State: ALoCoQmYEylOiPquCGxxHD5H9UGmSSAyB5xBoG3y+zKVyUxZq04m2A+6L/YrvPO7U1U6p/s+mKbIMebtThxq/fl8oIHtABYduZSJnt4n6srWFylyZjE1PhclTUzCti2rXnRY8VXWu2sF/9f1UUbNMUWfKme2NIfVMA==
X-Received: by 10.224.166.129 with SMTP id m1mr4618089qay.46.1375956991607; Thu, 08 Aug 2013 03:16:31 -0700 (PDT)
X-Received: by 10.224.166.129 with SMTP id m1mr4618079qay.46.1375956991422; Thu, 08 Aug 2013 03:16:31 -0700 (PDT)
From: Andrea Dixon <adixon@thrupoint.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac6UIFnhhNg3ys8nTdOldkCxEvKIQA==
Date: Thu, 8 Aug 2013 11:16:30 +0100
Message-ID: <dadb4585c9f0234ee8b370876873cd05@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary=047d7b60457cb351dc04e36cf342
Subject: [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 10:16:46 -0000

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<http://www.w3.org/TR/webrtc/#idl-def-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<http://www.w3.org/TR/webrtc/#idl-def-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