Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP Mux rejected
"Stach, Thomas" <thomas.stach@unify.com> Wed, 08 October 2014 13:21 UTC
Return-Path: <thomas.stach@unify.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20BE51A1A39 for <mmusic@ietfa.amsl.com>; Wed, 8 Oct 2014 06:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level:
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yt09tEzJ0Eby for <mmusic@ietfa.amsl.com>; Wed, 8 Oct 2014 06:20:59 -0700 (PDT)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2771A1A42 for <mmusic@ietf.org>; Wed, 8 Oct 2014 06:20:57 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id ED2DF1EB8494; Wed, 8 Oct 2014 15:20:55 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.241]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0195.001; Wed, 8 Oct 2014 15:20:55 +0200
From: "Stach, Thomas" <thomas.stach@unify.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: bundle-11: BUNDLE accpeted, but RTCP Mux rejected
Thread-Index: Ac/iRGIfWukm+VgKTsyCbXLuDZy5KwAGEVHgABwyUoAABzpZoAADjPnA
Date: Wed, 08 Oct 2014 13:20:55 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE121E227D6D@MCHP04MSX.global-ad.net>
References: <F81CEE99482EFE438DAE2A652361EE121E224ECF@MCHP04MSX.global-ad.net> <7594FB04B1934943A5C02806D1A2204B1D46CF08@ESESSMB209.ericsson.se> <F81CEE99482EFE438DAE2A652361EE121E227C60@MCHP04MSX.global-ad.net> <7594FB04B1934943A5C02806D1A2204B1D46E6EF@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D46E6EF@ESESSMB209.ericsson.se>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_F81CEE99482EFE438DAE2A652361EE121E227D6DMCHP04MSXglobal_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/B6Qu2F_UjIz6u8XxPdnV5EzwQdU
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP Mux rejected
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 08 Oct 2014 13:21:03 -0000
inline From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] Sent: Mittwoch, 8. Oktober 2014 13:37 To: Stach, Thomas; Harald Alvestrand; Cullen Jennings (fluffy) Cc: mmusic Subject: RE: bundle-11: BUNDLE accpeted, but RTCP Mux rejected Hi Thomas, I suggest something like this: In section 10.3.2.3: OLD TEXT: "If the answerer rejects usage of RTP/RTCP multiplexing within the BUNDLE group, it MUST NOT assign an SDP 'rtcp-mux' or SDP 'rtcp' attribute to any bundled "m=" line in the answer." NEW TEXT: "If the answerer rejects usage of RTP/RTCP multiplexing within the BUNDLE group, it MUST NOT assign an SDP 'rtcp-mux' or SDP 'rtcp' attribute to any bundled "m=" line in the answer. The answerer will, based on the port number of the selected offerer BUNDLE address, use the next higher (odd) destination port number [RFC3550] for sending RTCP packets associated with a bundled "m=" line towards the offerer," [TS] I'd like to add something for receiving RCTP. With a slight re-wording the new text would be If the answerer rejects usage of RTP/RTCP multiplexing within the BUNDLE group, it MUST NOT assign an SDP 'rtcp-mux' or SDP 'rtcp' attribute to any bundled "m=" line in the answer. Based on the port number of the selected offerer BUNDLE address, the answerer will send RTCP packets associated with any bundled "m=" line to the next higher (odd) destination port [RFC3550]. Based on the port number of the selected answerer BUNDLE address, the answerer will receive RTCP packets associated with any bundled "m=" line at the next higher (odd) destination port [RFC3550]. This means that the associated RTCP streams for bundled "m=" lines are bundled at the next higher (odd) destination port In section 10.3.2.4: OLD TEXT: "If the answerer does not accept the usage of RTP/RTCP multiplexing [Section 10.3.2.3], the offerer MUST use separate 5-tuples for RTP and RTCP." NEW TEXT: "If the answerer does not accept the usage of RTP/RTCP multiplexing [Section 10.3.2.3], the offerer MUST use separate 5-tuples for RTP and RTCP. The answerer will, based on the port number of the answerer BUNDLE address, use the next higher (odd) destination port number [RFC3550] for sending RTCP packets associated with a bundled "m=" line towards the answerer." [TS] Similar here If the answerer does not accept the usage of RTP/RTCP multiplexing [Section 10.3.2.3], the offerer MUST use separate 5-tuples for RTP and RTCP. Based on the port number of the selected offerer BUNDLE address, the offerer will receive RTCP packets associated with any bundled "m=" line at the next higher (odd) destination port [RFC3550]. Based on the port number of the selected answerer BUNDLE address, the offerer will send RTCP packets associated with any bundled "m=" line to the next higher (odd) destination port [RFC3550]. Regards, Christer From: Stach, Thomas [mailto:thomas.stach@unify.com] Sent: 8. lokakuuta 2014 13:06 To: Christer Holmberg; Harald Alvestrand; Cullen Jennings (fluffy) Cc: mmusic Subject: RE: bundle-11: BUNDLE accpeted, but RTCP Mux rejected Christer, From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] Sent: Dienstag, 7. Oktober 2014 20:35 To: Stach, Thomas; Harald Alvestrand; Cullen Jennings (fluffy) Cc: mmusic Subject: RE: bundle-11: BUNDLE accpeted, but RTCP Mux rejected Hi Thomas, >BUNDLE can be used separate from RFC5761 RTCP-Multiplexing. >I can't find text in bundle-11 where the answerer would send its RTCP packets if it accepted BUNDLE, but rejected RTCP-muxing. >I see two options: >1. The answerer sends all RTCP packets to the shared RTP-port+1 of the negotiated shared address. >2. The answerer sends the RTCP packets to separate ports based on the unique addresses in the m-lines of the offer? Alternative 1) is correct. I guess we could add some text to clarify that. [TS] Yes, please. The current text is not sufficiently clear. >The offerer on the other hand will only receive a shared address. I assume it then has to send all its RTCP packets >to the shared RTP-port+1 of the answerer. Yes. >Is my understanding correct or am I completely off-track? Assuming my understanding is correct, your understanding is correct :) >Supposed I'm correct, then independent from the response, I'm asking if there really is a use case for that. >In case 1, one would have to demux the RTP streams and RTCP streams from two separate ports instead of a single port. How much implementation effort >is saved in that case? I am not sure what you mean. Are you asking how much implementation effort is saved if you don't have to de-mux RTP and RTCP? [TS] Yes. I was questioning myself what benefit there is in not mandating RTCP-mux. In the meantime I looked up again the discussion on "Q14" that led to having rtcp-mux optional. I agree with the outcome. Thanks! >In case 2 the RTCP handling at offerer and answerer is completely different. In addition, you still need "a lot" of RTCP ports and take advantage of only half >of the BUNDLE benefits. Correct. But, case 2 is not applicable (unless the endpoints choose not to use BUNDLE to begin with, that is...). Regards, Christer
- [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP Mux… Stach, Thomas
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Christer Holmberg
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Stach, Thomas
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Christer Holmberg
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Stach, Thomas
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Christer Holmberg
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Stach, Thomas
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Christer Holmberg
- Re: [MMUSIC] bundle-11: BUNDLE accpeted, but RTCP… Stach, Thomas