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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 22 January 2016 09:53 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 83DA01A004E for <mmusic@ietfa.amsl.com>; Fri, 22 Jan 2016 01:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level:
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9YzalCMaeE-Z for <mmusic@ietfa.amsl.com>; Fri, 22 Jan 2016 01:53:11 -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 A46A91A004D for <mmusic@ietf.org>; Fri, 22 Jan 2016 01:53:10 -0800 (PST)
X-AuditID: c1b4fb3a-f79df6d0000013b1-b8-56a1fc047385
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id BA.D9.05041.40CF1A65; Fri, 22 Jan 2016 10:53:08 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.166]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0248.002; Fri, 22 Jan 2016 10:53:08 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Not fixing a=rtcp and rtcp-mux exclusive
Thread-Index: AQHRVH5u5HwUiLpiFk2f5BpmhdG86J8GeIug///94ICAAL0LkIAAA1MAgAAVBVA=
Date: Fri, 22 Jan 2016 09:53:07 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37D55AE5@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> <CAMvTgcffWjB153y=9iJ3MU5EWwZoi4qVVg_J6MGjRe-jy30vLg@mail.gmail.com>
In-Reply-To: <CAMvTgcffWjB153y=9iJ3MU5EWwZoi4qVVg_J6MGjRe-jy30vLg@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.19]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsUyM2K7ii7Ln4VhBluvGVvcnP+WxWLq8scs Fis2HGC1mHFhKrMDi8ff9x+YPHbOusvusWTJTyaPW1MKAliiuGxSUnMyy1KL9O0SuDL6b+5i K+gTrFi8fR1bA+MVgS5GTg4JAROJe4t3skDYYhIX7q1n62Lk4hASOMwo8WbvNBYIZwmjxJm2 ZiCHg4NNwEKi+582SIOIgI7EwfuT2UFsZoEiiaYFm8EGCQvYSTSfXs8MUWMvcWrtB0YI209i zpftTCA2i4CqRH9bG1gNr4CvxMnehWwgtpDAMyaJV9vSQWxOgUCJzUfXg81kBDru+6k1TBC7 xCVuPZnPBHG0gMSSPeeZIWxRiZeP/7FC2IoS7U8bGEFOZhbQlFi/Sx+iVVFiSvdDdoi1ghIn Zz5hmcAoNgvJ1FkIHbOQdMxC0rGAkWUVo2hxanFxbrqRkV5qUWZycXF+nl5easkmRmCEHdzy 22oH48HnjocYBTgYlXh4PyQtDBNiTSwrrsw9xCjBwawkwstwFSjEm5JYWZValB9fVJqTWnyI UZqDRUmcN0mmMUxIID2xJDU7NbUgtQgmy8TBKdXAKMzDXul9bbeC5W6nqaIxrrefX3yz1nqr V+FO1/JyQbUVYsKOzbmJCXelLG4faXWo7Ta4LPB3182mGVurDzUF/FK5WbikPWdC0nOuvHRh Ptkd+astlzRpvvdzK5mSqf+rx//e5BP7p4Z6Hz0oZ3JOJbmEb/rJ71XzEnmuLn5jGTw7RElX NOGDEktxRqKhFnNRcSIAQQibpKwCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/CDR4Jx5j_xaB6UGMH3j0_hY23EQ>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
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: Fri, 22 Jan 2016 09:53:12 -0000

Hi,

>Would changing the protocol field of the m= line make sense in this case? For example:
>
>c=IN IP4 11.22.33.44
>m=12345 RTPMUX/AVP 0 99
>
>Endpoints that don't support mux-exclusive should reject that m= line.

I guess it could be done that way, but personally I don't think it would be semantically correct. Also, we use "RTP" when negotiating non-exclusive mux, and when muxing bundled RTP streams.

Regards,

Christer

On 22 January 2016 at 08:27, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
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

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic