Re: [MMUSIC] BUNDLE and RTCP

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 19 October 2015 14:22 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783DF1A910E for <mmusic@ietfa.amsl.com>; Mon, 19 Oct 2015 07:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level:
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, 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 Aa5lGW9WOnbQ for <mmusic@ietfa.amsl.com>; Mon, 19 Oct 2015 07:22:23 -0700 (PDT)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 073171A7021 for <mmusic@ietf.org>; Mon, 19 Oct 2015 07:22:22 -0700 (PDT)
Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233]) by resqmta-po-06v.sys.comcast.net with comcast id X2NE1r00152QWKC012NN4r; Mon, 19 Oct 2015 14:22:22 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-09v.sys.comcast.net with comcast id X2NM1r00H3Ge9ey012NNHl; Mon, 19 Oct 2015 14:22:22 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37B66DC9@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37B66EEC@ESESSMB209.ericsson.se> <56248496.2050408@gmail.com> <7594FB04B1934943A5C02806D1A2204B37B6CAC0@ESESSMB209.ericsson.se> <562495FD.7020603@gmail.com> <7594FB04B1934943A5C02806D1A2204B37B6CCC5@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <5624FC9C.90904@alum.mit.edu>
Date: Mon, 19 Oct 2015 10:22:20 -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
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37B6CCC5@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1445264542; bh=F3M3oQ6KwGikl+0LwPE+3vghCcHafUxB68ZjaIZkVZc=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=lk578uiKYYXpnkcaLoSNCcVN07Us3f6zNynz38EtLJijgGT9bMkhYz7hz0w1hzmW5 RYFSXPo8lILN+tZFKS7nI/oR2iJ+WBK8YYCPx3agslVyzuSX2w1s4UT9afO+9tX6s1 aiZWiC0CogqoGAMKepF4ZulbSaJOW9l+TGC+UyV08r3K+ZpL3PTIWIfvjLsh3FCaDe 9Er+dG9VYKKRn3qeA0M9sVe72cNs2Mlxi0TW5gibX4MXG4jch0RUMY2YJ6oYCn36xZ CodzTfyhMArfSAAj5lvpImExMw8bwkckQno9cajHuhc+3IyYmcyjZ+0BaB5FM7SOPA Prpv6szxl9uFw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Eow6W27_hevNa1JqdA9vBljvN-o>
Subject: Re: [MMUSIC] BUNDLE and RTCP
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: Mon, 19 Oct 2015 14:22:24 -0000

Good discussion.

How about the following:

If there is an RTP m-line in the bundle, and rtcp-mux is *not* 
negotiated, then the rtcp port is determined according to the rules for 
the first m-line selected in the bundle group. If *that* line has, and 
allows, an a=rtcp, then that is used. If that line doesn't have a=rtcp, 
then port+1 is used, even if this isn't an rtp m-line.

(Right now there isn't any way to have a bundle group with more than one 
non-rtp m-line, but that might not always be so.)

	Thanks,
	Paul

On 10/19/15 3:35 AM, Christer Holmberg wrote:
> Hi,
>
> ...
>
> ...
>
> ...
>
>     HOWEVER, we could make it SIMPLE and either:
>
>     1)*Mandate usage of rtcp-mux with BUNDLE*. I.e. if BUNDLE is
>     negotiated, rtcp-mux MUST be used.
>
>     This was already suggested in the past, but Paul(?) said we should
>     not make such restriction without a good reason. I think the current
>     issue is a good reason :)
>
>     m=data channel 10000
>
>     m=rtp 11111
>
>     a=rtcp-mux
>
>     m=rtp 11222
>
>     a=rtcp-mux
>
>     2)*Mandate usage of either rtcp-mux OR the default “+1” port with
>     BUNDLE*. I.e. if BUNDLE is negotiated, rtcp-mux or “+1” MUST be
>     used. The selection is based on whether the rtcp-mux attribute was
>     included in the offer/answer or not.
>
>     m=data channel 10000             // rtcp-mux
>
>     m=rtp 11111
>
>     a=rtcp-mux
>
>     m=rtp 11222
>
>     a=rtcp-mux
>
>     m=data channel 10000             // “+1”
>
>     m=rtp 11111
>
>     m=rtp 11222
>
>     The solutions above would not allow explicit negotiation of an RTCP
>     port when BUNDLE is used, but maybe we could live with that?
>
>>Well, I could live with both of your suggestions, but I thought you
> wanted a solution that can also negotiate which a=rtcp attribute to use.
>
>>If nobody really needs something like that , I would prefer 1) as it
> removes the needs for several implementation option that would only be
> needed to cover full backwards compatibility but would hardly be used.
>
> Personally I don’t have a strong preference, but as far as I know there
> may be environments where separate ports for RTP and RTCP are desired –
> even if BUNDLE is used.
>
>>>Now, if we can agree on a way forward before Yokohama, you won’t have to
> sit listening to me talking about BUNDLE at the meeting :)
>>
>>Well, I wouldn't be sitting there anyhow but understand that your
> motivation to speak there about BUNDLE again is probably limited.
>
> I don’t mind talking about BUNDLE – but I’d like to talk about it in the
> context of the great RFC that we have published :)
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>