IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE and RTCP

Christer Holmberg <christer.holmberg@ericsson.com> Sun, 18 October 2015 17:53 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 D9C8E1AC3E6 for <mmusic@ietfa.amsl.com>; Sun, 18 Oct 2015 10:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 9Y_onZuzREL6 for <mmusic@ietfa.amsl.com>; Sun, 18 Oct 2015 10:53:19 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEE601AC39E for <mmusic@ietf.org>; Sun, 18 Oct 2015 10:53:18 -0700 (PDT)
X-AuditID: c1b4fb3a-f79136d0000071e2-07-5623dc8cd635
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 20.D7.29154.C8CD3265; Sun, 18 Oct 2015 19:53:16 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0248.002; Sun, 18 Oct 2015 19:53:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE and RTCP
Thread-Index: AdEJzH14LMfHNeeTQ5m0MrbuciOcLQAASvag
Date: Sun, 18 Oct 2015 17:53:15 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37B66EEC@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37B66DC9@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37B66DC9@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.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B66EECESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+JvjW7PHeUwg56ZBhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRs/VPawF53wq9p9tZW1gXO7cxcjJISFgIrHvxlZWCFtM4sK9 9WxdjFwcQgJHGSWWL3kM5SxmlOj51wFUxcHBJmAh0f1PG6RBREBd4uveHmYQW1hARqLh+m8W iLisxK2OFWwQtpFEy4+bYDaLgKrE9ulbwWxeAV+JU/8gaoSA7A1d59hBbE4BP4nXP06AzWEE Ouj7qTVMIDazgLjErSfzmSAOFZBYsuc8M4QtKvHy8T+oB5QkVmy/xAhRny+xdNkEVohdghIn Zz5hmcAoMgvJqFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGEWLU4uLc9ON jPRSizKTi4vz8/TyUks2MQJj6OCW31Y7GA8+dzzEKMDBqMTD++CIUpgQa2JZcWXuIUZpDhYl cd5mpgehQgLpiSWp2ampBalF8UWlOanFhxiZODilGhgjjH2j3om4Mzr8/3xl5eXV2vGX7syP iC9h11A490GkoDUyra9vovb1yp3r53fos9y/fWbzc7svvH7SATN/G22qEDPOiD5VeOvTMnH2 9e/3qoZN2Bl9qmB328P5OnOdrJVOCfnmWeib11/P6nOx2aFufuT2qslFUTvetH0N8V7btyFm +4o3t+8psRRnJBpqMRcVJwIAuuo8q4ICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/6Bol6R0eZQjKWdJHSeBtXyRtF-8>
Subject: Re: [MMUSIC] BUNDLE and RTCP
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: Sun, 18 Oct 2015 17:53:22 -0000

Hi,

Note that the issue exists even without bundle-only m- lines:

m=data channel 10000
m=rtp 11111
a=rtcp: 15000
m=rtp 11222
a=rtcp: 20000

Again, if the data channel m-  line is selected as the offerer BUNDLE address, which port will be used for RTCP?

Regards,

Christer

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 18 October 2015 20:47
To: mmusic@ietf.org
Subject: [MMUSIC] BUNDLE and RTCP

Hi,

During the proto write-up process of BUNDLE, an issue came up.

Assume the following BUNDLE offer, with one non-bundle-only data channel m- line and one bundle-only RTP m- line:

m=data channel 10000
m=rtp 0
a=bundle-only


Now, if bundle is accepted, the RTP m- line will get port 10000, as defined in BUNDLE. So far so good.

Now, if bundle is accepted, the data channel m- line will be selected as the offerer BUNDLE address, and RTP will use port 1000.

So far so good.


Next, assume we want to negotiate an explicit RTCP port for RTP. As the non-bundle-only m- line is not RTP (and therefore cannot contain an rtcp attribute), we have to add the actual RTCP port value to the bundle-only m- line:

m=data channel 10000
m=rtp 0
a=bundle-only
a=rtcp: 20000

So far so good.

Now, assume we also have one non-bundle-only RTP m- line:

m=data channel 10000
m=rtp 11111
a=rtcp: 15000
m=rtp 0
a=bundle-only
a=rtcp: 20000

Now, assume the data channel m- line is selected as the offerer BUNDLE address. It means that port 10000 will also be used for RTP. But, which port will be used for RTCP? 15000 or 20000?

Regards,

Christer

v2.23.0 | Report a Bug | By Email