[rtcweb] Plan xyz discussions; MMUSIC <> RTCweb Re: No Plan - but what's the proposal

Flemming Andreasen <fandreas@cisco.com> Thu, 06 June 2013 15:36 UTC

Return-Path: <fandreas@cisco.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 069A321F99C6 for <rtcweb@ietfa.amsl.com>; Thu, 6 Jun 2013 08:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 W2LTuFcV7WOu for <rtcweb@ietfa.amsl.com>; Thu, 6 Jun 2013 08:36:25 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 040F521F99C4 for <rtcweb@ietf.org>; Thu, 6 Jun 2013 08:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=963; q=dns/txt; s=iport; t=1370532985; x=1371742585; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=2vXW+SDbQdHecaQNYOEuLIdoTLw25vTt7xi1VkeCC4I=; b=bJcmB45wjxf4a61RhZZt47RG4Vy1HIagh2K0OkjJ38m3PNh7i1i+2dNv byrYQxSCVoZnCBJwohYYIKEYr2DZKpK5gBymQ+9Q+d2XhMH1nRVpWLUrX 0lUCo3HWGCpZVV1n6gvATOYhzx6Cv6qhin4l9W+9TJq89mhnBMcoCy3TG I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAH+rsFGrRDoH/2dsb2JhbABZgwm/d3gWdIIjAQEBBDhAARAZCgkWDwkDAgECAUUGDQEHAQGICLtPjzIHg1sDlz+RQIFYgVMg
X-IronPort-AV: E=Sophos;i="4.87,815,1363132800"; d="scan'208";a="82893560"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 06 Jun 2013 15:36:23 +0000
Received: from Flemmings-MacBook-Pro.local ([10.156.8.34]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r56FaMLv005955; Thu, 6 Jun 2013 15:36:22 GMT
Message-ID: <51B0AC76.2050401@cisco.com>
Date: Thu, 06 Jun 2013 11:36:22 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>
References: <51A65017.4090502@jitsi.org> <C3639EB3-0F44-4893-88DA-BB9F9C96A116@iii.ca> <51A8EB7F.6000506@jitsi.org> <72B58042-78E3-4759-B3CD-204B82A38447@iii.ca> <51ACF998.5030202@jitsi.org> <CALiegf=pJtdL2A6V7bprZ_F=V39Fadb+kRw3yfO+6+MFVZ9x2A@mail.gmail.com> <5ED2CC48-1514-4C00-AEE8-A334EB67A6F4@iii.ca> <51AF5784.3060307@jitsi.org> <13444A29-86C6-4D69-964D-AE9A5BA7BB4A@iii.ca> <51B0538A.5040800@jitsi.org>
In-Reply-To: <51B0538A.5040800@jitsi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] Plan xyz discussions; MMUSIC <> RTCweb Re: No Plan - but what's the proposal
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, 06 Jun 2013 15:36:30 -0000

On 6/6/13 5:16 AM, Emil Ivov wrote:
>
>
> P.S. I am confused as to where this discussion should be happening. 
> There have been contradictory comments from chairs that seem to say 
> how this should be in MMUSIC and how it actually doesn't belong to 
> MMUSIC and should happen on RTCWEB. I'd be grateful if chairs of both 
> WGs could sort this out and provide guidance.
>

Very fair request. This (MMUSIC) chair is confused too at this point as 
you can see on the MMUSIC list. The challenge I have is teasing apart 
the RTCWeb specifics (APIs, browser, RTCWeb specific scenarios, etc.) 
from the more general MMUSIC (SDP and O/A) considerations. The former 
should (IMO) be handled in RTCWeb and the latter should be done in 
MMUSIC, but the "Plan xyz" discussions don't always have a clean 
separation. I'll see if the chairs can come up with some guidelines here 
(but would welcome input from others of course)

Thanks

-- Flemming