Re: [MMUSIC] Not fixing a=rtcp and rtcp-mux exclusive

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 23 January 2016 14:06 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 374181A1B88 for <mmusic@ietfa.amsl.com>; Sat, 23 Jan 2016 06:06:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 fAjPXKbLjIQt for <mmusic@ietfa.amsl.com>; Sat, 23 Jan 2016 06:06:06 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD221A1B83 for <mmusic@ietf.org>; Sat, 23 Jan 2016 06:06:06 -0800 (PST)
X-AuditID: c1b4fb3a-f79df6d0000013b1-6b-56a388cc336e
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id AB.A1.05041.CC883A65; Sat, 23 Jan 2016 15:06:04 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.166]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Sat, 23 Jan 2016 15:06:04 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: Not fixing a=rtcp and rtcp-mux exclusive
Thread-Index: AQHRVH5u5HwUiLpiFk2f5BpmhdG86J8GeIug///94ICAAL0LkIAAOGowgABaTACAAV0qoA==
Date: Sat, 23 Jan 2016 14:06:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37D57EFC@ESESSMB209.ericsson.se>
References: <CAD5OKxvMdsdkYaJWB5UdvCTNj3a+pheXV+_1viyLrH_UOWBTpA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37D5509D@ESESSMB209.ericsson.se> <CAD5OKxum=E84NVTtWtSwYowDmyJ=sQifx6Na9wt0pUhYH1j_PA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37D557C6@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37D55EAA@ESESSMB209.ericsson.se> <CAD5OKxvaUi25TbOa48mKwkEJMnJqde_TQNfe1Cagdgj+jTbJ3g@mail.gmail.com>
In-Reply-To: <CAD5OKxvaUi25TbOa48mKwkEJMnJqde_TQNfe1Cagdgj+jTbJ3g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsUyM2K7ve6ZjsVhBusmKVpMXf6YxWLFhgOs FjMuTGV2YPb4+/4Dk8eSJT+ZPG5NKQhgjuKySUnNySxLLdK3S+DKmDzzPmPBPLGKM1MvsDQw XhHtYuTkkBAwkZjz/zoThC0mceHeerYuRi4OIYHDjBInjnxkh3CWMEp09j0Ecjg42AQsJLr/ aYM0iAioSvz9PhmsmVnAV+L9z+nsILawgKnE23P7mSBqzCRe939ig7DDJJ42QdgsQL2bZnSB 1fMC9V5t3g+1axWzxNQXy1lBEpwCgRI/7q8AK2IEuu77qTVQy8Qlbj2ZD3W1gMSSPeeZIWxR iZeP/7FC2EoSjUuesILczCygKbF+lz5Eq6LElO6HUHsFJU7OfMIygVFsFpKpsxA6ZiHpmIWk YwEjyypG0eLU4uLcdCMjvdSizOTi4vw8vbzUkk2MwHg6uOW31Q7Gg88dDzEKcDAq8fAWbFkU JsSaWFZcmXuIUYKDWUmEV7hxcZgQb0piZVVqUX58UWlOavEhRmkOFiVx3oP8QNUC6Yklqdmp qQWpRTBZJg5OqQZGIx8Zq+fXgh8EBk1VLU1LOynw6sLCaY1VqwXqBDYV5zr4T/pStrSH5fTO r1d4/Xq4maOr9xzQXbYpOvXf3sLZDplch45J90/Nl9LN/tvr/1Ypoth2xsMT07TWCnol/FJk vnau4+yrnVVLH+e2W5f3uH7a0C+tXvRrwckzgoaf+1dXyluGJWYqsRRnJBpqMRcVJwIArkXb 4qMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/q-kpJ4RN1QrjBXtsQYUyiMEECC8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Not fixing a=rtcp and rtcp-mux exclusive
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: Sat, 23 Jan 2016 14:06:08 -0000

Hi,

>>> We can for sure define a new attribute, if people prefer that.
>>>
>>> But, it still wouldn't solve Paul's issue, that a non-ICE endpoint that doesn't support the attribute may
>>> start sending RTCP on RTP+1. But, at least the offerer would see from the answer that the answerer does 
>>> not support mux-exclusive, and can take proper actions.
>>>
>>> We can define new attribute that specifies address and port for both RTP and RTCP similar to ICE candidate 
>>> or a=rtcp attribute and set address in c= line to IN IP4 0.0.0.0. This way any end point that does not understand 
>>> this attribute will send no media.
>>
>> Another option would be to set the m- line port to zero, like we do for bundle-only. Then, if the answerer 
>> doesn't support the attribute, it won't use the m- line.
>>
>> Example:
>>
>> c=IN IP4 11.22.33.44
>> m=0 RTP/AVP 0 99
>> a=mux-exclusive: 12345  <------- 12345 is the port to be used for RTP and RTCP
>>
>> One problem with this solution is that an intermediary that doesn't support the attribute won't know where to 
>> forward the media, it the m- line port value is 0. It very likely will assume there will be no media to begin with.
>
> I always wondered what intermediary we are talking about which is supposed to know where to forward media. If 
> we are talking about firewalls which dynamically open ports, then, most of the time it has no access to signaling information 
> due to use of secure channels. If we are talking about something that does something to the media and forwards it (rtp proxy 
> in combination with sip proxy), then we actually want such proxy to support rtcp mux exclusive or fail the connection for 
> the same reason we want regular end points to fail during connection setup -- to prevent RTCP from being sent to 
> unexpected destination.

If such proxy only forwards what it receives, it doesn't need to support mux-exclusive. It only forwards what it gets. However, if it sees an m- line with port 0, it may not forward anything.

Regards,

Christer