Re: [rtcweb] Where Plan A, B, and "no plan" discussions should happen

Cullen Jennings <fluffy@iii.ca> Sat, 08 June 2013 05:31 UTC

Return-Path: <fluffy@iii.ca>
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 5BC3B21F9A23 for <rtcweb@ietfa.amsl.com>; Fri, 7 Jun 2013 22:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599]
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 EnV-JKKu87RK for <rtcweb@ietfa.amsl.com>; Fri, 7 Jun 2013 22:31:36 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 62CC021F9A21 for <rtcweb@ietf.org>; Fri, 7 Jun 2013 22:31:36 -0700 (PDT)
Received: from [10.70.232.148] (unknown [64.104.46.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C6C1522E200; Sat, 8 Jun 2013 01:31:29 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CA+9kkMA-sye-uss+xa1kHkcGu7Yaw9QdgioHq2kj2a76RfQgCQ@mail.gmail.com>
Date: Sat, 8 Jun 2013 12:31:26 +0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <02AA976E-1768-49E2-BF7F-57191955404E@iii.ca>
References: <CA+9kkMA-sye-uss+xa1kHkcGu7Yaw9QdgioHq2kj2a76RfQgCQ@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.1503)
Subject: Re: [rtcweb] Where Plan A, B, and "no plan" discussions should happen
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: Sat, 08 Jun 2013 05:31:42 -0000

On Jun 8, 2013, at 12:49 AM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Howdy,
> 
> Several folks have asked for clarification on where plan A, plan B, and "no plan" discussions should occur. Magnus and Cullen and I have not had much chance to discuss it, but here is my take:
> 
> RTCWEB has made a request of MMUSIC for a standardized way to handle multiple media flows (for large values of "multiple" in some cases).  Plan A and Plan B propose specific approaches and syntax to resolve the request.  Discussions of those approaches and syntax belong in MMUSIC, full stop.
> 
> Discussions of whether we actually need a standardized way to handle that belong in RTCWEB, because they are essentially an argument to the WG that we can withdraw the request to MMUSIC and go forward using other pieces of the WebRTC mechanics to resolve the problem.
> 
> Emil's draft has some elements which critique plan A and plan B, and a proposal that falls into the "no need for a standard here" camp.  For clarity's sake, it might be easiest if those were split.  The proposal that a standard isn't needed could be submitted as an RTCWEB relevant draft (draft-ivov-rtcweb-no-plan-needed, perhaps?).  The critique of Plan A and Plan B could be submitted as an MMUSIC draft (draft-ivov-mmusic-plan-a-b-considerations, perhaps?).
> 
> At this point, I do not see consensus to withdraw the request to MMUSIC from RTCWEB, but, as I said, Magnus, Cullen, and I have not had much chance to coordinate, so this is not a chair decision.
> 
> regards,
> 
> Ted Hardie

100% agree with Ted. Cullen <with my chair hat on>

PS - Ted, Magnus, and I are currently roughly equally separated  each1/3 of the way around the world from the other two people so it's been hard to get the time zones to work for our usual phone calls.