IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 07 May 2013 18:36 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 6528921F8B38 for <mmusic@ietfa.amsl.com>; Tue, 7 May 2013 11:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.142
X-Spam-Level:
X-Spam-Status: No, score=-0.142 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 RmIqWlusWz0P for <mmusic@ietfa.amsl.com>; Tue, 7 May 2013 11:36:37 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 82C9921F8B2B for <mmusic@ietf.org>; Tue, 7 May 2013 11:36:37 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta05.westchester.pa.mail.comcast.net with comcast id Yz4l1l0011ei1Bg556ccuF; Tue, 07 May 2013 18:36:36 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id Z6cc1l00b3ZTu2S3k6ccrK; Tue, 07 May 2013 18:36:36 +0000
Message-ID: <518949B4.9060601@alum.mit.edu>
Date: Tue, 07 May 2013 14:36:36 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mmusic@ietf.org
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>, <201305030115.r431Fis33999826@shell01.TheWorld.com> <BLU169-W1311854975457C1CFC4B01093BE0@phx.gbl> <201305061800.r46I0jM84247693@shell01.TheWorld.com>
In-Reply-To: <201305061800.r46I0jM84247693@shell01.TheWorld.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367951796; bh=MkQsyFq7M8ksSf3IzNfZJcbjK6YnCfuw2HOxQaYATTU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=a7y1ZktiMxvvKY5c1IWc+JC2ziJeV7FKFkz6HBPgLicVjlOOrFon2rpOOgbrCOMrQ bLjBd/BjWdwy+BpsH2HeqJ5FW/iyegAVBgK4FHRdhGY7gzXmoUt9BrquKDWC/kadJ4 5nCooINoLYamZygcSSjydAtPiTvZJQ8kLGxKINKxAYijAteff5lucwN5X9SL08NPTX qc+ppO0HvgGSB+85sj/BsrEo6PcUXNtFL+QZOxcpeOwNXg+HSMoHjDFoOKYZUJQwyP xWGOFhrLccLn/bpW+qeNA1/+skvLLMYXO2obWrONz72JiQXKqUj13v7F91c67f9anF 3+OibufQrnoWg==
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: Tue, 07 May 2013 18:36:42 -0000

I'd just like to point out that AFAIK bundling doesn't *require* ICE.
So lets not make any assumptions that assume ICE is used.

	Thanks,
	Paul

On 5/6/13 2:00 PM, Dale R. Worley wrote:
>> From: Bernard Aboba <bernard_aboba@hotmail.com>
>>
>>> 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.
>
> Dale
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

v2.23.0 | Report a Bug | By Email