Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?

Christer Holmberg <> Tue, 07 May 2013 09:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6109021F8D2C for <>; Tue, 7 May 2013 02:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ATKupqwBVYBK for <>; Tue, 7 May 2013 02:53:54 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AA40121F8C23 for <>; Tue, 7 May 2013 02:53:53 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f536d000006e05-e0-5188cf23d451
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 7B.68.28165.32FC8815; Tue, 7 May 2013 11:53:39 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Tue, 7 May 2013 11:53:38 +0200
From: Christer Holmberg <>
To: "Dale R. Worley" <>, Bernard Aboba <>
Thread-Topic: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?
Thread-Index: Ac5FpkrHryzI/aQNT0iUvXy00zH5hwADtcYAAAPFvoAAAQhZgAA4imSAABwqMXAABklLyAAANmRgABmo8HEABBaqAAC15MErACEgllA=
Date: Tue, 07 May 2013 09:53:38 +0000
Message-ID: <>
References: <>, <>, <>, <>, <>, , <>, <>, <>, <> <BLU169-W1311854975457C1CFC4B01093BE0@phx.gbl> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM+Jvra7y+Y5Ag7OLhS32L7nMbDF1+WMW i5cnyhyYPSbv/8rs8bjnDJvHkiU/mQKYo7hsUlJzMstSi/TtErgy3k2ezVZwla/ixOmrzA2M u7m7GDk4JARMJI5/K+ti5AQyxSQu3FvP1sXIxSEkcJhRorXrKpSzmFFi3fpHzCANbAIWEt3/ tEEaRATCJPr/PmAHCTMLqEtcXRwEEhYWsJFo2rGTGaLEVmLKvRvsEHaZxMpZr1hBbBYBFYn+ l+sYQWxeAV+Jm0fOsUKsesEi0bFxDlgzp4CDxI8NLWA2I9Bx30+tYQKxmQXEJW49mc8EcbSA xJI955khbFGJl4//sULYihJXpy+HqteRWLD7ExuErS2xbOFrZojFghInZz5hmcAoNgvJ2FlI WmYhaZmFpGUBI8sqRvbcxMyc9HLDTYzAmDm45bfuDsZT50QOMUpzsCiJ8yZxNQYKCaQnlqRm p6YWpBbFF5XmpBYfYmTi4JRqYPReePQMl8nbdYXyGsy3g8K27+NclR348LrrzU89+wSN7h7/ e22C81Ym21Ce9ex+VqsmZtTHNTx9eSS7u7ky3WHTVmue7u26Abnc97UU0yuOyz2+soO5P+7u TbeunIVVW10WO/Flm8uHW/eqpydPqhN5PmWlbbgcT+RWsxqJ1/Nben7vee/8QImlOCPRUIu5 qDgRAJ6F7SFnAgAA
Cc: "" <>
Subject: Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?
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, 07 May 2013 09:54:00 -0000


>>> But it doesn't seem that there is much to gain by mandating rtcp-mux 
>>> in the first offer/answer, the one where actual bundling is not 
>>> being done.  All of the RTP/RTCP routing code that is active at that 
>>> point has to support non-rtcp-mux operation already.
>> [BA]  Support for rtcp-mux in the first offer/answer is mandated by 
>> RFC 5761 Section 5.1.3:
>>    The initial SDP offer MUST include this
>>    attribute at the media level to request multiplexing of RTP and RTCP
>>    on a single port. 
> I don't see how 5761 mandates that a=rtcp-mux MUST be used in the first offer of a bundle negotiation.  The context of your quote is:
>   5.1.3.  Interactions with ICE
>   [...]
>   If it is desired to use both ICE and multiplexed RTP and RTCP, the
>   initial offer MUST contain an "a=rtcp-mux" attribute to indicate that
>   RTP and RTCP multiplexing is desired and MUST contain "a=candidate:"
>   lines for both RTP and RTCP along with an "a=rtcp:" line indicating a
>   fallback port for RTCP in the case that the answerer does not support
>   RTP and RTCP multiplexing.  This MUST be done for each media where
>   RTP and RTCP multiplexing is desired.<
> That is, if the device desires to use both ICE and multiplex, it has to use a=rtcp-mux in the first offer of ICE's set of offers.  But we're talking about bundling, which (in the current design) contains
> *two* ICE cycles, since the second offer (in the bundle spec) is going to restart ICE.  And the device need not "desire" to use "both ICE and multiplexed RTP and RTCP" during the first of the ICE cycles.

As indicated, BUNDLE actually already DOES mandate a=rtcp-mux in the first offer, but it is optional for the answer, to the suggestion is to mandate it in the first answer.