[MMUSIC] BUNDLE and RTCP

Christer Holmberg <christer.holmberg@ericsson.com> Sun, 18 October 2015 17:46 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 9F5581AC400 for <mmusic@ietfa.amsl.com>; Sun, 18 Oct 2015 10:46:54 -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 JVDQP1MDsT4Q for <mmusic@ietfa.amsl.com>; Sun, 18 Oct 2015 10:46:53 -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 6B1AF1AC3FF for <mmusic@ietf.org>; Sun, 18 Oct 2015 10:46:52 -0700 (PDT)
X-AuditID: c1b4fb3a-f79136d0000071e2-3b-5623db0ae5e8
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 18.87.29154.A0BD3265; Sun, 18 Oct 2015 19:46:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0248.002; Sun, 18 Oct 2015 19:46:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE and RTCP
Thread-Index: AdEJzH14LMfHNeeTQ5m0MrbuciOcLQ==
Date: Sun, 18 Oct 2015 17:46:49 +0000
Message-ID: <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_7594FB04B1934943A5C02806D1A2204B37B66DC9ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+JvjS7XbeUwg8l7RSymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujG8vu5kLWs0rbl39xd7A2GfQxcjJISFgIrHw6hk2CFtM4sK9 9UA2F4eQwFFGia5tM5kgnMWMEts372HtYuTgYBOwkOj+pw3SICKgLvF1bw8ziC0sICFxevIV doi4rMStjhVsIOUiAnoSsxfHgoRZBFQlZv54AraLV8BXYsLn20wgNiPQ3u+n1oDZzALiEree zGeCuEdAYsme88wQtqjEy8f/WCFsJYkV2y8xQtTnS0xb+ZkZYqagxMmZT1gmMArNQjJqFpKy WUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypG0eLU4uLcdCMjvdSizOTi4vw8vbzU kk2MwIg4uOW31Q7Gg88dDzEKcDAq8fA+OKIUJsSaWFZcmXuIUZqDRUmct5npQaiQQHpiSWp2 ampBalF8UWlOavEhRiYOTqkGxlTm92G5Z97l86xO1xay/3V1vg9rmtPJ3Qfuq93UfswdUZm9 5076m3d/rzRm6t1dxGXbobpN2qtYT2rltyYXI2/v4+3rSx/6fzj8+GfjSp8WZs2GvONrFndd /P3ljJf6omMzli222ab5uPKR/+n8W5+a9Dc9jnTss2tZ461qLWM5NcuZXY2DVYmlOCPRUIu5 qDgRABGqoY1pAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/0nvykc3MojTg1qCJZl83Gz4q9_M>
Subject: [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:46:54 -0000

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