[MMUSIC] MMUSIC plan for progressing simulcast and related work

Flemming Andreasen <fandreas@cisco.com> Fri, 16 October 2015 14:29 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id D9BAC1B2C3D for <mmusic@ietfa.amsl.com>; Fri, 16 Oct 2015 07:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id a2zvIEnKCp73 for <mmusic@ietfa.amsl.com>; Fri, 16 Oct 2015 07:29:43 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3763D1B2C1B for <mmusic@ietf.org>; Fri, 16 Oct 2015 07:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26160; q=dns/txt; s=iport; t=1445005783; x=1446215383; h=from:to:subject:message-id:date:mime-version; bh=bZpj7yYQNeuzOiOJcC9bqCjIdUU4F5DnxZXsTpO7jnw=; b=FHFB/tkLwq1zRsx0+JCM+QceTO/Kf/mq3XmwQoZWectUBpx8Avx8UnMC sutJXTakZIZwFPyA97jLs5GzHJaEgOUtU/HSYhnzj2NMqrq6jsEzfk+7c 51zm5UaWNBJJaCS6S1HLpA1OHbCvUQwDi1rW5A3kZ9h4GTdcuVUZNA5/h U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.17,689,1437436800"; d="scan'208,217"; a="38297688"
Received: from rcdn-core-5.cisco.com ([]) by rcdn-iport-6.cisco.com with ESMTP; 16 Oct 2015 14:29:42 +0000
Received: from [] (bxb-fandreas-8815.cisco.com []) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t9GETfqm013358 for <mmusic@ietf.org>; Fri, 16 Oct 2015 14:29:41 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>
Message-ID: <562109E9.6090508@cisco.com>
Date: Fri, 16 Oct 2015 10:30:01 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------050301050909030903010409"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Uq0M3BWrMaF6N01i5bwFXzhJevQ>
Subject: [MMUSIC] MMUSIC plan for progressing simulcast and related work
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 14:29:45 -0000

Greetings MMUSIC

Earlier this week, we had a virtual interim meeting on simulcast. One of 
the reasons for this meeting was that we have been informed, that W3C 
has a dependency on the simulcast work for the upcoming WebRTC 1.0, and 
MMUSIC itself has a milestone for the simulcast work in January (2016), 
both of which are approaching quite rapidly. The simulcast draft 
(draft-ietf-mmusic-sdp-simulcast) has been around for some time and is 
now complemented by the rid draft ( draft-pthatcher-mmusic-rid) to 
address concerns around payload type exhaustion. We haven't seen any 
major comments on the simulcast draft in a while however we understand 
the draft authors will be submitting an update for Yokohama. Based on 
the virtual interim meeting, while there were some questions raised on 
the rid draft, there seemed to be good support for the rid-draft 
overall. The rid-draft authors have subsequently submitted an updated 
document to try and address those questions.

Based on all of this, we plan to proceed the simulcast work as follows:

1. Wait for updated simulcast draft to be submitted (before IETF 
94/Yokohama deadline).

2. If the simulcast draft authors believe it is ready for WGLC, then 
issue WGLC (prior to IETF 94).

3. Issue a call for WG adoption of draft-pthatcher-mmusic-rid
4. Discuss any open issues raised on either draft in Yokohama
5. Update the drafts post-Yokohoma to address any open issues discussed
6. Issue WGLC on the rid-draft if it and related mechanisms in simulcast 
are ready (may include a second WGLC on simulcast draft).


     Flemming & Ari (as MMUSIC co-chairs)