Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 30 April 2013 17:12 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36E5121F9C1C for <mmusic@ietfa.amsl.com>; Tue, 30 Apr 2013 10:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.175
X-Spam-Level:
X-Spam-Status: No, score=-0.175 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 WPuFA7aY1ZXe for <mmusic@ietfa.amsl.com>; Tue, 30 Apr 2013 10:12:32 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA2721F9763 for <mmusic@ietf.org>; Tue, 30 Apr 2013 10:12:31 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta14.westchester.pa.mail.comcast.net with comcast id WFPg1l0061HzFnQ5EHCXSi; Tue, 30 Apr 2013 17:12:31 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id WHCW1l01Y3ZTu2S3aHCXBR; Tue, 30 Apr 2013 17:12:31 +0000
Message-ID: <517FFB7E.8050801@alum.mit.edu>
Date: Tue, 30 Apr 2013 13:12:30 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C368E12@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C368E12@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=1367341951; bh=ZoKWJAkdWM1anW/EXuiexeGv4fuQQ9RwNW2MTt9pa2I=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Boqh0nD5sUIHYmE4d3niwSn9Jbtg6U2OMM5PNrYlpmSLS/cmCpcWD8xrOGvFFvfjf CYDBeubbhR9bolYGpbTV8Ty1AQ9yZs3wAaj455ZJe+l1G9okrK2PIGG7Fi+qTC4EkX 8vpkGRR7cLKuBaf8BPaDFbCkRoJ/EXbuIMcBef9sAuRrTL9TiKa7hfEE3vrReEWSoK N8Iytv99UVmpTSur3jB5ivrmj7ZR6aGmlIMXKzaJ6XvqHyhONvrfENLZJ9veFoaK+D 8UyL/c7ZiYTskisBz4iQaCK8t0OSZ8oPtuXzuGxveOyPwKX0neYwOgBiEmrfHS4uET SjSLgdi/AMrzg==
Subject: Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 30 Apr 2013 17:12:48 -0000

On 4/30/13 9:26 AM, Christer Holmberg wrote:
> Hi,
>
> As currently indicated in BUNDLE, and SDP offer for RTP must contain an
> rtcp-mux attribute, indicating support of RTP/RTCP multiplexing.
>
> However, it is currently optional to include it in the SDP answer.
>
> There has been some discussions on whether we should MANDATE the usage
> of rtcp-mux whenever BUNDLE is enabled.
>
> Would anyone OBJECT to that?

What are the implications of *not* mandating it?

Doing so requires two ports, so in some sense you end up with two bundles.

If a=rtcp:nn is used, then presumably it will need to be the same in all 
RTP m-lines. But we have many such requirements, so this one isn't special.

I guess I won't *object*, but it does offend my notion that independent 
things should be kept independent.

	Thanks,
	Paul