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

worley@ariadne.com (Dale R. Worley) Fri, 03 May 2013 01:16 UTC

Return-Path: <worley@shell01.TheWorld.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 DB67A21F8554 for <mmusic@ietfa.amsl.com>; Thu, 2 May 2013 18:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.894
X-Spam-Level:
X-Spam-Status: No, score=-2.894 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 T5wa2i5lZZOW for <mmusic@ietfa.amsl.com>; Thu, 2 May 2013 18:16:02 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 0109621F8540 for <mmusic@ietf.org>; Thu, 2 May 2013 18:16:01 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r431Fjd8003549; Thu, 2 May 2013 21:15:47 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r431FjmF4004282; Thu, 2 May 2013 21:15:45 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r431Fis33999826; Thu, 2 May 2013 21:15:44 -0400 (EDT)
Date: Thu, 2 May 2013 21:15:44 -0400 (EDT)
Message-Id: <201305030115.r431Fis33999826@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-reply-to: <7594FB04B1934943A5C02806D1A2204B1C3699A8@ESESSMB209.ericsson.se> (christer.holmberg@ericsson.com)
References: <7594FB04B1934943A5C02806D1A2204B1C368E12@ESESSMB209.ericsson.se> <517FFB7E.8050801@alum.mit.edu> <CABkgnnVf6f3RrP2h66_8hFPZScWU3Xp4f1x0dmW0xhmvZRQ70Q@mail.gmail.com> <51801BBD.1010505@alum.mit.edu> <CAOJ7v-12j0k1W7GRfOzvPmfN-BZ0ve=fHVcWy+avronfc8wFYw@mail.gmail.com>, <7594FB04B1934943A5C02806D1A2204B1C369709@ESESSMB209.ericsson.se> <CE0F590A-D948-4702-9082-FDE0DCBFB698@cisco.com> <7594FB04B1934943A5C02806D1A2204B1C3699A8@ESESSMB209.ericsson.se>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?
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: Fri, 03 May 2013 01:16:08 -0000

> From: Christer Holmberg <christer.holmberg@ericsson.com>
> 
> In fact, I noticed that, in the second offer, BUNDLE already
> mandates it in both the offer and answer :)
> 
> So, the only addition would be to mandate it also in the first answer.

I can see why it would be useful to mandate rtcp-mux in the bundled
offer/answer, because it is more port-efficient, and the code that
handles the multiplexing and demultiplexing the constituent streams
only has to handle the case where the RTCP is multiplexed with the
RTP.

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.

Dale