Re: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?

Christer Holmberg <> Mon, 30 May 2016 08:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D34EB12D180; Mon, 30 May 2016 01:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id twus6elaeC60; Mon, 30 May 2016 01:08:16 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C78CD12D16B; Mon, 30 May 2016 01:08:14 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-72-574bf4ec26ac
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 65.8C.12926.CE4FB475; Mon, 30 May 2016 10:08:12 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0294.000; Mon, 30 May 2016 10:08:11 +0200
From: Christer Holmberg <>
To: Suhas Nandakumar <>
Thread-Topic: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AdG3iWsAcXNHXXrjTfakEZTp6P/ejwAHIEqAAKtQNIA=
Date: Mon, 30 May 2016 08:08:12 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D371CFE99672christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyM2K7h+6bL97hBtdn6Vi87FnJbrH85QlG i6nLH7NY7JzbwezA4jHt/n02j52z7rJ7LFnykymAOYrLJiU1J7MstUjfLoEro3c+Z8G82oo9 v4QaGBvzuhg5OCQETCRWvFbuYuQEMsUkLtxbz9bFyMUhJHCEUWL1nlnMEM4SRokJU+8ygjSw CVhIdP/TBmkQEdCSWL14LhNIDbPATkaJhm1/2UFqhAVCJDYsyAIxRQRCJW4/k4Yot5J4NWEz G4jNIqAqsWv7TCYQmxcovm9CH9TeKYwSex9OYQVJcAoESjw9uA3MZgQ67vupNWANzALiEree zGeCOFpAYsme88wQtqjEy8f/wOpFBfQkvtybxwgRV5T4+GofI0RvvETvmtlsEIsFJU7OfMIy gVFsFpKxs5CUzUJSBhE3kHh/bj4zhK0tsWzhayhbX2Ljl7OMs4BeZhawlpix0hJZyQJGjlWM osWpxUm56UbGeqlFmcnFxfl5enmpJZsYgVF7cMtv1R2Ml984HmIU4GBU4uFV0PMOF2JNLCuu zD3EKMHBrCTC+/YxUIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgs EwenVAOj4BUJLe0Y7wmrnfyynukXNPiyLtfRO5Iaf6v+6/Oe7FVG7PohM7Wee0XZPkjT67il ++BlgQS7s8CMC1yhly9M+7F913fGqBcT0v7/t+dUnFi67QXrgwPMOZutS54oJuxRt54o+vDK a76w6hSxvuN921kfF/7VU1x/5opsLP/BBatrrna+9QlQYinOSDTUYi4qTgQAPFSijdYCAAA=
Archived-At: <>
Cc: Magnus Westerlund <>, "Colin Perkins \(\)" <>, "" <>, "" <>
Subject: Re: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 May 2016 08:08:20 -0000

Hi Suhas,

I have the same understanding as you: the offerer indicates support of RTP/RTCP-mux, and the answerer decides whether to use it or not. And, if used, it will be used in BOTH directions – i.e. the usage of RTP/RTCP is not per direction.

Colin? Magnus?



From: Suhas Nandakumar <<>>
Date: Friday 27 May 2016 at 04:25
To: Christer Holmberg <<>>
Cc: "<>" <<>>, "<>" <<>>, Magnus Westerlund <<>>, Colin Perkins <<>>
Subject: Re: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?

Going along O/A negotiation procedures, i would lean towards your former conclusion that the offer needs to include the rtcp-mux ability.
If the offer doesn't include a=rtcp-mux and the answerer wants to mux , then it needs a new O/A from the answerer's perspectives.

If we make a=rtcp-mux a declarative SDP it might solve the other use-case ..


On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg <<>> wrote:
(Sorry for the cross-posting)


There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=rtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       o=csp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       c=IN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=1153134164 1153137764
       m=audio 49170 RTP/AVP 97
       a=rtpmap:97 iLBC/8000

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=rtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=rtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=rtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=rtcp-mux"

Q: The question is whether it is allowed to include a=rtcp-mux in an answer if the associated offer did NOT contain a=rtcp-mux.

The second last paragraph in the text above does say that, if the answer wishes to do RTP/RTCP-mux, it includes a=rtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=rtcp-mux in the answer, even if it’s not included in the offer? If so, how will the offerer then indicate whether mux is used or not.



Audio/Video Transport Core Maintenance<>