[MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux
Christer Holmberg <christer.holmberg@ericsson.com> Thu, 02 August 2012 23:32 UTC
Return-Path: <christer.holmberg@ericsson.com>
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 6EC8611E8129 for <mmusic@ietfa.amsl.com>; Thu, 2 Aug 2012 16:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.882
X-Spam-Level:
X-Spam-Status: No, score=-5.882 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
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 6lsbRh1RpVUA for <mmusic@ietfa.amsl.com>; Thu, 2 Aug 2012 16:32:02 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A511F11E80F0 for <mmusic@ietf.org>; Thu, 2 Aug 2012 16:32:01 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fd66d0000004ad-31-501b0df0a9c5
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 4C.99.01197.0FD0B105; Fri, 3 Aug 2012 01:32:00 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.21]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Fri, 3 Aug 2012 01:32:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Date: Fri, 03 Aug 2012 01:31:59 +0200
Thread-Topic: Simultanous usage of a=rtcp and a=rtcp-mux
Thread-Index: AQHNcQNY0hgh5d0YIEer0pxA+0dG7g==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058534086835E5@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBLMWRmVeSWpSXmKPExsUyM+Jvre4HXukAg61tphZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuHr8QWbOCpm7brK1sB4nq2LkZNDQsBEonPjSmYIW0ziwr31 YHEhgVOMEsevhXYxcgHZ8xkl5nRvZOli5OBgE7CQ6P6nDVIjIqAu8XVvD1gvi4CKxOKt98Bs YQFjiQM/37FA1FhIHGu7xgph60k8vPwDLM4rEC7x5nYrmM0ItPf7qTVMIDazgLjErSfzmSDu EZBYsuc81G2iEi8f/2OFqBeVuNO+nhGiXk/ixtQpbBC2tsSyha+ZIeYLSpyc+YRlAqPwLCRj ZyFpmYWkZRaSlgWMLKsYhXMTM3PSyw31Uosyk4uL8/P0ilM3MQJD++CW37o7GE+dEznEKM3B oiTOy5W0319IID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY8gqhw3PDlxIc2k6+njKjSdHDOzF z83mnmcgfba7327d1x5Vk02N+f2Lwg7UXFGPPdgb/f/a09SmtrNrctsLWyZPba56cnvxhqqJ u52exTcklXOtzjMqfZUq0v5CkXdeR63vjy9/nkZqzvWMOur9P49Xme95+TOu7lfWgc9djwnI eDg9P3frlxJLcUaioRZzUXEiAJ6b37o7AgAA
Subject: [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux
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: Thu, 02 Aug 2012 23:32:02 -0000
Hi, One of the issues which was raised during the MMUSIC BUNDLE presentation, but which is not BUNDLE specfic, was the case when an offer contains both a=rtcp and a=rtcp-mux. A case where this can happen is ICE, which requires the inclusion of the a=rtcp attribute. "If the agent is utilizing RTCP, it MUST encode the RTCP candidate using the a=rtcp attribute as defined in RFC 3605 [RFC3605]." (RFC 5245/Section 4.3) Example: m=audio 20000 a=rtcp: 25000 a=rtcp-mux Q: If the receiver supports both attributes, to which port would it send RTCP? As indicated during the meeting, in theory this could be solved by using a=rtcp: 20000 (ie same port as RTP), but people indicated that it is not allowed (eventhough not explicitly forbidden, afaik). As also indicated, another way to solve this could be by saying: "If the receiver supports a=rtcp-mux, use that, otherwise use a=rtcp". But, I have not found any text which would support such intepretion. Opinions? Regards, Christer
- [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-m… Christer Holmberg
- Re: [MMUSIC] Simultanous usage of a=rtcp and a=rt… Paul Kyzivat
- Re: [MMUSIC] Simultanous usage of a=rtcp and a=rt… Lishitao
- Re: [MMUSIC] Simultanous usage of a=rtcp and a=rt… Christer Holmberg