[rtcweb] Processing multiple remote offers
Taylor Brandstetter <deadbeef@google.com> Mon, 16 October 2017 23:13 UTC
Return-Path: <deadbeef@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 57152132403 for <rtcweb@ietfa.amsl.com>; Mon, 16 Oct 2017 16:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 43LnaUxZxAjV for <rtcweb@ietfa.amsl.com>; Mon, 16 Oct 2017 16:12:59 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 CA0601270AE for <rtcweb@ietf.org>; Mon, 16 Oct 2017 16:12:59 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id 126so8722236vkj.9 for <rtcweb@ietf.org>; Mon, 16 Oct 2017 16:12:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=aE6wDrJ95ftWm3mO0YusLpD6zNGvWmJ335Vibz+UcIs=; b=QfLU4DqZk3FOgc26VyPfWOFQm9ob6PwULwf0i0cvNcOj9t2UNzsSvedGln4YGI7I12 T95fZeo485D3k7K00yqVzTk54uPChh4e2Xi1lTvlDgkEM30xFbp3fMa4AhFtDiLh5AQ+ 084PYtR4bpS4irq8BbJvYlWMTvDH4E2fMwO+XsNtztchLhHhGupqOrOB+kMm/xpHpsXr X2rK/smcTLCYje0Ei/SdRHtE9ITM2utdkQ94mleGxQmjD0lD/pKYKVFYQW+BdPF+Xcgh BvnBWv4QXO34q47cLxLGSIDvauiqSBrBWIqHzJEI5PZd6WBQ1iIo3mKMSy8oR4TbmJ94 o2gA==
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=aE6wDrJ95ftWm3mO0YusLpD6zNGvWmJ335Vibz+UcIs=; b=dB6bdEQzYQOR3Qub6hdhQgg4HtzjtpjrUFdMlB7/7DDBqwb3HZf8nK8Umr+V2KoAph 5B/JRfZV5JY+B6x8Z97jcCqwSAPCZDH4d9YH7/ca6eK/EOD0zG5PI3bqroo4cGw7FVXR Ub2EZwSqqDZxIw+VYWVkMA3Zsyamjh7TfWdAniuIfsvRUrxLd966CSx7VScqnko+gHN2 vRZWY0T/KWANxdNtuR6EQux3VJpUR+4isOifeyUdCe19IBBF85qxuOtzxn4Q8j2Tnf07 /4i110M9EgihaRHrtTpyTIRvkm5hRQfsgvZ7fgCjShSOcNQ2cknfil9hQA9lR1OLGvt2 aOlQ==
X-Gm-Message-State: AMCzsaVLAGHbN2yHmDAmkkW6u/n8SYjLuUfuPeQthjcGMYAqKwCR8TPV CrOL+zAJ6y6J7Exb5OPpDqXlOYiuTzGupA+VbKpQnh+m
X-Google-Smtp-Source: ABhQp+T3UXO1nQ5Kz0GIZyFjXKogP0HamaVgX7nVfyQr/U/llAJQqqxIWDREz+OOL/eZcXBhcQW5mUOWZAQpQ3z91Z8=
X-Received: by 10.31.74.134 with SMTP id x128mr1692001vka.14.1508195578411; Mon, 16 Oct 2017 16:12:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.169.130 with HTTP; Mon, 16 Oct 2017 16:12:57 -0700 (PDT)
From: Taylor Brandstetter <deadbeef@google.com>
Date: Mon, 16 Oct 2017 16:12:57 -0700
Message-ID: <CAK35n0ZDYBmSpf7BPS+kABj9x8ZbwtMHPr794E8G5fVKqqndUg@mail.gmail.com>
To: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a114dacdcb4b94d055bb22576"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/iqPTla7Uz_GyxOlvnd-anpIJPIM>
Subject: [rtcweb] Processing multiple remote offers
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: Mon, 16 Oct 2017 23:13:01 -0000
JSEP allows a remote offer to be applied while in the "have-remote-offer" state. Meaning that, in addition to supporting multiple answers (via pr-answers), JSEP also supports multiple offers. However, I don't see any text that calls out what (if anything) must be the same between these offers. Should we assume that they can be *completely* different? Or do they at least need to contain the same m= sections (same type, MID and order)? For example: is it legal to apply an audio-only remote offer, then apply a video-only remote offer? Is it legal to apply an audio-only offer, then an audio+video offer? This affects WebRTC 1.0, because depending on which direction this goes, we may need to address a situation where an RTCRtpTransceiver is created by applying a remote offer, then invalidated by the next remote offer. Does it go away or exist in limbo state? Of course, another solution would be to say "this isn't supported, do a rollback if you need this."
- [rtcweb] Processing multiple remote offers Taylor Brandstetter
- Re: [rtcweb] Processing multiple remote offers Harald Alvestrand
- Re: [rtcweb] Processing multiple remote offers Taylor Brandstetter
- Re: [rtcweb] Processing multiple remote offers Cullen Jennings (fluffy)