Re: [rtcweb] Translating Plan A into No Plan (Was: No Plan)

Eric Rescorla <ekr@rtfm.com> Mon, 03 June 2013 18:35 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 6D79511E80A4 for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 11:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 12oGF-A2FiYv for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 11:34:58 -0700 (PDT)
Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) by ietfa.amsl.com (Postfix) with ESMTP id 11A4021F92FC for <rtcweb@ietf.org>; Mon, 3 Jun 2013 11:34:24 -0700 (PDT)
Received: by mail-qe0-f54.google.com with SMTP id ne12so2034891qeb.27 for <rtcweb@ietf.org>; Mon, 03 Jun 2013 11:34:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=m19/R522ObJCRQ6dcAEOiGsJ6akQPxbA8aCa92t6aq4=; b=Em6oxK5nqvsHlzjDlBIPO2fqwzOKk9cTNX/IFxkUhJPjNLNKtZvRkjESC+KEoDbka2 rG9tk23NeME4EzsOjgcC0gPw5gKfBccUCkWAgK8zG3t9ztFxqZA5mOl6RT0mtaXZXmrM XVV+gBLefnG8qoCRYPMW+9LFk/+XwBE66bHzrBphgBu6MBEB4hlRSaYyfY+57yZRJfbR BN1NFVRBoYThAxMisT5VUn+W42OD4RLY8M+hRv636D6lTbGS4RnRV4tNw8YeDqd1aLya 4xDT/7iBEZ7LxNXj9Wkvij2CW2WjPv/dsagY+NTalKZOunc/5W0Tyyn7tuvA6055hNfI jb7g==
X-Received: by 10.49.81.147 with SMTP id a19mr18754133qey.47.1370284464413; Mon, 03 Jun 2013 11:34:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.0.163 with HTTP; Mon, 3 Jun 2013 11:33:44 -0700 (PDT)
X-Originating-IP: [63.245.220.224]
In-Reply-To: <51ACD224.8080100@jitsi.org>
References: <51A65017.4090502@jitsi.org> <51A65DB8.9060702@alum.mit.edu> <51A880A7.7010908@jitsi.org> <C5E08FE080ACFD4DAE31E4BDBF944EB113528171@xmb-aln-x02.cisco.com> <51A8EAB7.8080206@jitsi.org> <C5E08FE080ACFD4DAE31E4BDBF944EB11352940B@xmb-aln-x02.cisco.com> <51ACD224.8080100@jitsi.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 3 Jun 2013 11:33:44 -0700
Message-ID: <CABcZeBNp72QirKG1WPaX0HFjCFC+WRJ4Zh-H9L8zaVmmb4Yuog@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: multipart/alternative; boundary=047d7b6dd15ebe37ac04de4436a8
X-Gm-Message-State: ALoCoQnw5IAq6AH9WUUGtGVhhdYdLGP6QHNVhRtCb+A8uJUCR3WE4fgDhl0DN53VBK4x6f86luO5
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Translating Plan A into No Plan (Was: No Plan)
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: Mon, 03 Jun 2013 18:35:14 -0000

On Mon, Jun 3, 2013 at 10:28 AM, Emil Ivov <emcho@jitsi.org> wrote:
[...]

> III. Talking to other WebRTC applications
>
> This is the fun case and the one we should be most concerned with. Let's
> imagine that the answerer needs to add a fourth video stream. To make this
> work endpoints would need to do the following:
>
> a) with Plan A and draft-roach-rtcweb-glareless-**add:
>    - send application specific signalling to the offerer
>    - have a new O/A exchange
>
> b) with Plan A:
>    - have a new O/A exchange
>    - potentially risk glare with some impact on user experience
>
> c) with No Plan:
>    ... nothing
>
>
I'm really not following how this works in "No Plan". Ignoring Plan A and
Plan B, can you just
walk through a complete example of what happens in your plan? I.e., how
does browser
B learn learn that Browser A wants to send 3 streams instead of one?

-Ekr