Re: [rtcweb] BUNDLE with implicit rtcp-mux

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 12 March 2014 23:14 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6372F1A07A9 for <rtcweb@ietfa.amsl.com>; Wed, 12 Mar 2014 16:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tjz0vFmKwYFo for <rtcweb@ietfa.amsl.com>; Wed, 12 Mar 2014 16:14:37 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 441131A0781 for <rtcweb@ietf.org>; Wed, 12 Mar 2014 16:14:37 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta03.westchester.pa.mail.comcast.net with comcast id cmyH1n0030Fqzac53nEWkE; Wed, 12 Mar 2014 23:14:30 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id cnEW1n00Q3ZTu2S3UnEWlf; Wed, 12 Mar 2014 23:14:30 +0000
Message-ID: <5320EA56.1050507@alum.mit.edu>
Date: Wed, 12 Mar 2014 19:14:30 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-063mGE_zndtAqAMN2fJw7kWvUHX2SgyDMryfw_-aS-9w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1F1892@ESESSMB209.ericsson.se> <531DC52B.6020500@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D1FA6BC@ESESSMB209.ericsson.se> <531DCBE9.70701@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D1FA7B2@ESESSMB209.ericsson.se> <531DD756.50900@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D200086@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D200086@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394666070; bh=SXrvzGS7wSEc4j7XnqvyoSqed6PPdXyQZaZC2PYf89g=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=j6VAvUWG48/HLvY/nm9jxV8QBdemVWFwlSdQJ3frbhn3quiGR61ywOAEIJQ3xaJ9s WgG7Ba463ZF6Z4TCiMa1lzssZVyFwOJoU58BnMaumQof9t31Ua1zI4VbBCXkfp6O40 ZcQvftQj6ayyTiAmDp6YSI0xYBQ0t7HpKs4qxTzTMsOEa0Hub07/3Bf/XTlXxBvKjR os/K4q2LxFgZKh4rrZ8E+xl8RzsAHHlixzjgbWY/yDS6E/dT0yQO/eGCcQQwL7nsIv AL77ZiqezytVIe/DLnQOmvtEjFR9Z3AI4KW8xhUlLwotPpanolj+GUMxe+RGMZ0465 QuehSOOtsy4qA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Er5wGVALEi989ZM_rX0ANVPxEoc
Subject: Re: [rtcweb] BUNDLE with implicit rtcp-mux
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 12 Mar 2014 23:14:38 -0000

On 3/10/14 4:09 PM, Christer Holmberg wrote:

>> I also thought the a=rtcp-mux is a MUST to implement, not a MUST use.
>
> Currently the draft says MUST use. But, that may be a mistake, or a leftover from previous procedures. I agree that one should be able to use BUNDLE also without rtcp-mux (i.e. using separate BUNDLE ports for the RTP traffic and the RTCP traffic).

Now that I look carefully, I think you have been a little over zealous 
about this.

Remember, at least in principle, there can be non-RTP m-lines in the 
bundle. You don't want to require using rtcp-mux with those. (And, at 
least in principle, bundle can be used even when there are *no* RTP 
m-lines.)

So I think the draft must at least limit these requirements to RTP 
m-lines. (But finding a clean way to do that may be tricky, since there 
is a potentially open ended set of <proto> values that relate to RTP.)

	Thanks,
	Paul