IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE: RTCP port issue solution alternatives

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 22 October 2015 11:02 UTC

Return-Path: <christer.holmberg@ericsson.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 B25FA1A1ADD for <mmusic@ietfa.amsl.com>; Thu, 22 Oct 2015 04:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level:
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 JDgudEDrhxbQ for <mmusic@ietfa.amsl.com>; Thu, 22 Oct 2015 04:02:15 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5821A1ADC for <mmusic@ietf.org>; Thu, 22 Oct 2015 04:02:14 -0700 (PDT)
X-AuditID: c1b4fb30-f79626d000006adf-b2-5628c2345cfb
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 63.63.27359.432C8265; Thu, 22 Oct 2015 13:02:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0248.002; Thu, 22 Oct 2015 13:02:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: RTCP port issue solution alternatives
Thread-Index: AdEL8RXdh8BNoI07RoSt0gj6HwR1AgAx5HOA
Date: Thu, 22 Oct 2015 11:02:11 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37B85DD4@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37B805A7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37B805A7@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B85DD4ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGfG3RtfkkEaYwbmLmhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxo474gU3nCp+nWphamBstO5i5OSQEDCRmLTsPAuELSZx4d56 ti5GLg4hgaOMEpuX/2eFcBYzSkz/chQow8HBJmAh0f1PG6RBREBd4uveHmYQW1jASuLQ8teM EHFriXsf97ND2EYSEy4vYAKxWQRUJf6t/A1WzyvgKzHjwh8wWwjIftv+DqyeU8BP4uqBXWAH MQId9P3UGrBeZgFxiVtP5jNBHCogsWTPeWYIW1Ti5eN/rBC2okT70wZGiPp8iVXPrrFC7BKU ODnzCcsERpFZSEbNQlI2C0kZRFxHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8UoWpxanJSb bmSkl1qUmVxcnJ+nl5dasokRGEEHt/w22MH48rnjIUYBDkYlHt4HXBphQqyJZcWVuYcYJTiY lUR4L00FCvGmJFZWpRblxxeV5qQWH2KU5mBREudtZnoQKiSQnliSmp2aWpBaBJNl4uCUamAM 6trUGvE01GWKj1YLq93qrpRL5wsVfpw+FcdoeO/m2h2eIUv+fwq+/3JmUp+J3sQfDns0Qw2u 5VS+1RHZEtZgeH7VwbdCE5luZa46ue+YUfGd+T7+Ipe78nfteDuh7Y0CY8Siy/uStL/15c95 fZu5VFvYU777cJrntxvHaw4ZJFfm2Ejp3zuuxFKckWioxVxUnAgAnox6xpwCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/teYCkLptyHgRDT85bCfVbKbcokc>
Subject: Re: [MMUSIC] BUNDLE: RTCP port issue solution alternatives
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 22 Oct 2015 11:02:16 -0000

Hi,

A clarification to alternative 1).

The suggestion is that clients must still support non-rtcp-mux, and are free to include a=rtcp etc if they want, for cases where the remote endpoint does not support (or does not want to use) BUNDLE and there is a fallback to non-BUNDLE.

Regards,

Christer

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 21. lokakuuta 2015 14:19
To: mmusic@ietf.org
Subject: [MMUSIC] BUNDLE: RTCP port issue solution alternatives

Hi,

Based on the discussions so far, I have identified 3 alternative solutions for the RTCP port issue:


1)      Mandate RTCP-MUX whenever BUNDLE is used

Note: In order to maintain alignment with SDP, my suggestion would be to still mandate including of a=rtcp-mux in all RTP m- lines. I.e. the rtcp-mux usage would not be implicit.


2)      Select the RTCP port based on the RTCP properties (implicit or explicit) associated with the FIRST RTP m- line within the BUNDLE group, or the RTCP properties associated with the selected offerer BUNDLE address m- line if RTP.


3)      Allow usage of RTCP properties (a=rtcp, ICE RTCP components, etc) also in non-RTP m- lines.


Note: This MAY require updates of some RFCs.

Regards,

Christer

v2.23.0 | Report a Bug | By Email