[rtcweb] Revising rollback semantics
Eric Rescorla <ekr@rtfm.com> Fri, 11 August 2017 16:43 UTC
Return-Path: <ekr@rtfm.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 9049B1321DF for <rtcweb@ietfa.amsl.com>; Fri, 11 Aug 2017 09:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjdFWhwgcGWU for <rtcweb@ietfa.amsl.com>; Fri, 11 Aug 2017 09:43:28 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C28941321C9 for <rtcweb@ietf.org>; Fri, 11 Aug 2017 09:43:27 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id p68so25603392ywg.0 for <rtcweb@ietf.org>; Fri, 11 Aug 2017 09:43:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=8WLX4YZNNPtcZSrhP5u35O586h2Ht94zkLQ+B5C22B0=; b=E2WsGUWPF1vqga6UKLJJFXd4T+xIXSZ39/pRz9ylq5Ro681Y4tLIFR3ApMWANoijtH arkhqdQPrJtiETEyNnSe9Q+lljU3xdEP4us0uEcjw+QlDN6CCTsqQY7cQ2JUzYipbA6Q NBDc7nNx1bxzYGvMU9v5hBM4l3pxS5Sj3606y1oONJZLc1+aef3bUPQRq0i6prmAMzsm IM6mUFD0SrJI58/UynYmPzf5SB5O4kn9wo79DUvyYJHYUJcCUtJ2R+M0ZSSyoaskjyGx Nn8ZRq60LB5B/FB4OPhkpu6wyEPRUZoEEZm37mwEbZoDjaYLGe31Pcn3XRlAVFcVhwM+ 7tqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8WLX4YZNNPtcZSrhP5u35O586h2Ht94zkLQ+B5C22B0=; b=U43nVHeTQCch/oihtNV/UpKpVcwY+dRgTI+Bwk/42lOE7SmxJz/RXB5+PawdQvKI/m 4rvGM/ggvtBqUACjSClA+9iulZ/zCRkTOUEWPbZhDO2g2jQ5GXWhK8Tk8mJ/P+akZjSD BO/fj7STveLlFZhEXv8dxLaNg6juOX5EViFKJSvXGv3iog3Uj/sZDcGJCFLM8TXelHkt kHwbnmuAIHamH/Jb6vR6OSsyjlaDcLqEyfTttPTjn8aJBY4jUah/3LbBkq2GUJPueVq4 FaacIHqOl7vEwOCHSZnvzAgKJQQEUu/d48sOSr9V9HImgcO8M56JZa5dKpRm5Sy5DTm9 Sw3w==
X-Gm-Message-State: AHYfb5iJ2+txO+LHzafYcmFTjozTUkjigtYJHXXOR6wbrzUeZ587bjND F+ohybhGFTDa/ZOxpCSM3SnZLncxr1cqxvZ/KA==
X-Received: by 10.13.251.3 with SMTP id l3mr13610409ywf.71.1502469806719; Fri, 11 Aug 2017 09:43:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.218.130 with HTTP; Fri, 11 Aug 2017 09:42:46 -0700 (PDT)
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 11 Aug 2017 09:42:46 -0700
Message-ID: <CABcZeBOgbDJbAWtS9A-cNjTvMvrBXH0GzHc6NKLBBz0re8Zhhg@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c07f0361dc20405567d03ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/mruHLXbVRJSZWoQ1jzNi4ggoc3c>
Subject: [rtcweb] Revising rollback semantics
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 16:43:32 -0000
I wanted to make the group aware of the following change that we've made to
the semantics of rollback [0].
The basic idea is that rollback always returns you to the stable state
regardless
of what state you are in and it doesn't matter which of
set{Local,Remote}Description you call. This makes life a bit easier for
implementations, which may want to handle either remote or local rollbacks
in a uniform fashion. Please speak now if you object.
-Ekr
[0]
https://github.com/rtcweb-wg/jsep/commit/6f5dc414265cab8b76b25e5cd381a53bcb9cd5c5
- [rtcweb] Revising rollback semantics Eric Rescorla