IETF Logo Mail Archive

Re: [MMUSIC] mux-exclusive: a=mux-exclusive and a=rtcp-mux in the same m- line?

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 03 February 2016 17:38 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 DB34B1A8A8D for <mmusic@ietfa.amsl.com>; Wed, 3 Feb 2016 09:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 tcFrvNEPXTw2 for <mmusic@ietfa.amsl.com>; Wed, 3 Feb 2016 09:38:37 -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 514971A86EF for <mmusic@ietf.org>; Wed, 3 Feb 2016 09:38:37 -0800 (PST)
X-AuditID: c1b4fb3a-f79df6d0000013b1-40-56b23b1b8022
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 5D.E9.05041.B1B32B65; Wed, 3 Feb 2016 18:38:35 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.166]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Wed, 3 Feb 2016 18:38:35 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] mux-exclusive: a=mux-exclusive and a=rtcp-mux in the same m- line?
Thread-Index: AdFeYGbEUl5ZALTxRXaQ4UThrGlu1wAOTZiAAAPylxA=
Date: Wed, 03 Feb 2016 17:38:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37D6D954@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37D6C486@ESESSMB209.ericsson.se> <CAD5OKxvohj8naUTFMjG=UuNKpG+X44j3hdmevjnOZKasg5m7QQ@mail.gmail.com>
In-Reply-To: <CAD5OKxvohj8naUTFMjG=UuNKpG+X44j3hdmevjnOZKasg5m7QQ@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.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbHdT1faelOYwZyHihZTlz9msZhxYSqz A5PHkiU/mTxuTSkIYIrisklJzcksSy3St0vgyji84TVbQR9Xxcu15xgbGN9wdjFyckgImEj8 eLyOGcIWk7hwbz1bFyMXh5DAYUaJL4vns0I4ixklnq7Yz97FyMHBJmAh0f1PG6RBREBV4u/3 yUwgYWYBdYmri4NAwsICURInDjWxgYRFBKIl1j3ygDCtJJ7PLgKpYBFQkfi5ah87iM0r4Ctx adZaFohFUxglejvWMoEkOAUCJV63PgA7jRHotO+n1oDFmQXEJW49mc8EcbKAxJI956HOF5V4 +fgfK4StJLHo9meoyzQl1u/Sh2hVlJjS/RBqr6DEyZlPWCYwis1CMnUWQscsJB2zkHQsYGRZ xShanFpcnJtuZKSXWpSZXFycn6eXl1qyiREYNQe3/LbawXjwueMhRgEORiUe3g1/NoQJsSaW FVfmHmKU4GBWEuF9arQpTIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvGuf1YUIC6YklqdmpqQWp RTBZJg5OqQZGg73L729pbXgXJ5D4utP+crL+m9PfvLyPVlzdyiO0deW/8qyDj01WZ/7l3qC0 dNI0G4a4zqkK5uInxNWszde++2HVttpI7eVO7sL+iVffbI0umiP4cp6zrUnDXeHdx7RXTwp9 dNN2z9TWkzE+qTJsp5cssftsHfFyS3drt/aph8aP59WzhuzUV2Ipzkg01GIuKk4EANZ9toOW AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/zp2H1I2SM2Xi85eQQmQZnRG-prc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] mux-exclusive: a=mux-exclusive and a=rtcp-mux in the same m- line?
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: Wed, 03 Feb 2016 17:38:39 -0000

Hi,

>>One issue is whether it’s allowed to include both a=mux-exclusive (or whatever we will end up calling it) and a=rtcp-mux in the same m- line, as a=rtcp-mux means support of fallback to non-mux.
>>
>>OPTION #1:
>>
>>If one includes a=mux-exclusive, one must also include a=rtcp-mux
>> 
>>OPTION #2:
>> 
>>If one includes a=mux-exclusive, one must not include a=rtcp-mux.
>
>
> Do we allow to setup a media session if end point sends an offer with a=mux-exclusive and a=rtcp-mux and gets the answer back with a=rtcp-mux only?

I think we should - because that means that the answerer agrees to do mux.

And, that is perhaps a good justification for option #1, because it allows to negotiate mux even if the answerer does not support a=mux-exclusive. Because, no matter if we include a=rtcp-mux or not, if the answerer doesn't indicate mux in the answer the offerer will have to take actions.

Regards,

Christer

v2.23.0 | Report a Bug | By Email