Re: [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux

Christer Holmberg <> Tue, 14 August 2012 19:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9780B21F863F for <>; Tue, 14 Aug 2012 12:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.552
X-Spam-Status: No, score=-5.552 tagged_above=-999 required=5 tests=[AWL=-0.503, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id y+Ow93LH47cB for <>; Tue, 14 Aug 2012 12:17:13 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D320021F8615 for <>; Tue, 14 Aug 2012 12:17:08 -0700 (PDT)
X-AuditID: c1b4fb25-b7f236d000005cde-62-502aa433a8cb
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id C1.72.23774.334AA205; Tue, 14 Aug 2012 21:17:08 +0200 (CEST)
Received: from ([]) by ([]) with mapi; Tue, 14 Aug 2012 21:17:08 +0200
From: Christer Holmberg <>
To: Lishitao <>, "" <>
Date: Tue, 14 Aug 2012 21:15:05 +0200
Thread-Topic: Simultanous usage of a=rtcp and a=rtcp-mux
Thread-Index: AQHNcQNY0hgh5d0YIEer0pxA+0dG7pdXaa+QgAJWg+4=
Message-ID: <>
References: <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvra7JEq0Ag6/uFgf33WK2mLr8MYsD k0fLkbesHkuW/GQKYIrisklJzcksSy3St0vgynh77D97wSbJij/HHrI2MK4U6WLk5JAQMJF4 s+k8K4QtJnHh3nq2LkYuDiGBU4wSmz53s4AkhAQWMEp8mu7TxcjBwSZgIdH9TxskLCLgLjF5 +042EJtFQFXiZVMX2BxhAXOJSa962CFqLCSOtV1jhbCtJC41NIDZvALhEu9vnmCFGL+QUaLn pTOIzSkQJrHj+CFGEJsR6J7vp9YwgdjMAuISt57MZ4K4U0BiyZ7zzBC2qMTLx/9YIepFJe60 r2eEqNeRWLD7ExuErS2xbOFrZoi9ghInZz5hmcAoOgvJ2FlIWmYhaZmFpGUBI8sqRuHcxMyc 9HIjvdSizOTi4vw8veLUTYzA+Di45bfqDsY750QOMUpzsCiJ81pv3eMvJJCeWJKanZpakFoU X1Sak1p8iJGJg1OqgbHSmm+O2JaF/y93x/3Mt3F4Uth3rS6j8vve4vhpy8+tvGt77Vi5rsmR iEURe7b9+9tRWyK4XnlnTu1/PneJX1dSO7+e93ba4pl66zfP1snPX7HVTHR9XbooeG7KTQHJ DqHlxw5PNGOc6Lb+Urzs0tu3C+043z/9cKNRtd0pOWrTlnnHxTKmLolWYinOSDTUYi4qTgQA +i11Ll0CAAA=
Subject: Re: [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Aug 2012 19:17:13 -0000

Hi Shitao,

I agree with your understanding.

Of course, the answerer might not support ICE, but a=ssrc and a=rtcp-mux, and in that case it will have to choose one. But, as the offerer has to be prepared for both alternatives, I guess that should not be a problem.



From: [] On Behalf Of Lishitao []
Sent: Monday, August 13, 2012 10:40 AM
To: Christer Holmberg;
Subject: Re: [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux

Hi Christer
I find some words in RFC 5245, section 5.7.1, this may answer your question.

   In the case of RTP, this would happen when one agent provides
   candidates for RTCP, and the other does not.  As another example, the
   offerer can multiplex RTP and RTCP on the same port and signals that
   it can do that in the SDP through an SDP attribute [RFC5761].

   However, since the offerer doesn't know if the answerer can perform
   such multiplexing, the offerer includes candidates for RTP and RTCP
   on separate ports, so that the offer has two components per media
   stream.  If the answerer can perform such multiplexing, it would
   include just a single component for each candidate - for the combined
   RTP/RTCP mux.  ICE would end up acting as if there was just a single
   component for this candidate.

To me, this indicates that if the receiver supports rtcp-mux, it should use the same port for RTP and RTCP.


> -----Original Message-----
> From: [] On Behalf
> Of Christer Holmberg
> Sent: Friday, August 03, 2012 7:32 AM
> To:
> Subject: [MMUSIC] Simultanous usage of a=rtcp and a=rtcp-mux
> 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 mailing list
mmusic mailing list