Re: [MMUSIC] SDP work needed for WebRTC stuff

"Cullen Jennings (fluffy)" <> Sun, 09 December 2012 00:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 09BF321F8AEA; Sat, 8 Dec 2012 16:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vNrqKDp+gij5; Sat, 8 Dec 2012 16:19:48 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2CCC921F8ADF; Sat, 8 Dec 2012 16:19:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2402; q=dns/txt; s=iport; t=1355012388; x=1356221988; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Nc0Laq5KqESAbVg4cXK4ac8TweDr2vrfHs8pN5/NDdM=; b=ehCulsR7xXhp5FqUFV/2CiC71VFsDpCvMqLADjqg3MG+lhC8UBRVBZvJ 48XQX5XToA/TxjS2y9JQEFBP+R1iGEPFAApUGu6X/lVUFx/wBpXrVcW7H 3Dws0RKGsPxsnJZ1EAo2OTQP63ugQytFB0xb/Pl+jO9Sp+a1rLR2l8CjK 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAN7Yw1CtJV2c/2dsb2JhbABEvmIWc4IeAQEBAwF5EAIBCA4KCiQyJQIEDgUIiAMGvyyMP4NiYQOIKp4kgnOCIg
X-IronPort-AV: E=McAfee;i="5400,1158,6920"; a="150877202"
Received: from ([]) by with ESMTP; 09 Dec 2012 00:19:46 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id qB90JkUA014590 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 9 Dec 2012 00:19:46 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Sat, 8 Dec 2012 18:19:46 -0600
From: "Cullen Jennings (fluffy)" <>
To: Eric Rescorla <>
Thread-Topic: [MMUSIC] SDP work needed for WebRTC stuff
Thread-Index: AQHN1ZrLc7vRdGyb+kCXOHgISQGSp5gP/yeA
Date: Sun, 09 Dec 2012 00:19:46 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<>" <>, mmusic WG <>, "<>" <>
Subject: Re: [MMUSIC] SDP work needed for WebRTC stuff
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 09 Dec 2012 00:19:49 -0000

On Dec 8, 2012, at 4:21 PM, Eric Rescorla <> wrote:

> +rtcweb
> On Sat, Dec 8, 2012 at 2:41 PM, Cullen Jennings (fluffy) <> wrote:
> I was looking over everything that needs to be completed to finish a fist cut of the WebRTC related work. There are a handful of big SDP problems that are currently blocking some of the WebRTC work and I'd like to figure out how to make some progress on them.
> Let me loosely characterize them as
> 1) If we have several video streams, how do theses map up to 1 or more m lines.
> 2) if we are doing port multiplexing, what does the SDP look like (the bundle problem)
> 3) How do we map the RTCWeb track and stream label concepts to identifiers in SDP
> 3) SDP for application running over SCTP/DTLS
> I don't want to speak for all the various chairs but I am under the impression that most of chairs of related groups in W3C and IETF believe these are issues that need to be resolved primarily in the MMUSIC WG and that they impact both WebRTC and CLUE as well as the general long term use of SDP in SIP and other protocols.
> I'd like to get some discussion going on how we can make some progress on these. I don't think we are going to solve these in 20 minutes of discussion at an IETF meeting so I think we probably need some interim (virtual or face to face) to sort this out.
> Thoughts?
> Wow, I'm totally confused here.
> I had assumed that the SDP-related issues were going to be the main
> topics at the WebRTC/RTCWEB interim in January. Is that not the case?

So far the interim was only talking about being a WebRTC & RTCWeb so this SDP stuff would be out of scope. Perhaps it would be better to have some of the time for mmusic topics? 

> IMO the lack of clarity around how to encode various media
> configurations into SDP is the major thing blocking progress here. In
> particular, Firefox has opted not to implement multiplexing of media
> streams over the same transport flow (whether of the bundle or
> multiple m-line variety) until the SDP for it is well-defined. The
> same thing applies to the question of how to map multiple m-lines to
> incoming MediaStreams/Tracks.
> We really need to cover these issues in the interim.
> -Ekr