IETF Logo Mail Archive

[MMUSIC] ICE and RTCP host components

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 20 October 2015 12:28 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 B8F4B1A8ADF for <mmusic@ietfa.amsl.com>; Tue, 20 Oct 2015 05:28:19 -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 jht-vZHkzxjw for <mmusic@ietfa.amsl.com>; Tue, 20 Oct 2015 05:28:18 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE9071A8AF2 for <mmusic@ietf.org>; Tue, 20 Oct 2015 05:28:17 -0700 (PDT)
X-AuditID: c1b4fb25-f79a26d00000149a-98-5626335f06bc
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id A6.59.05274.F5336265; Tue, 20 Oct 2015 14:28:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0248.002; Tue, 20 Oct 2015 14:28:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: ICE and RTCP host components
Thread-Index: AdELMspQZuqUGadKR+G+TYSjfMsEiQ==
Date: Tue, 20 Oct 2015 12:28:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37B7AC27@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.18]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B7AC27ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+JvjW68sVqYwYaDkhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRs+pfraCDvmKFUe3sjQwzpfuYuTgkBAwkWj64NjFyAlkiklc uLeerYuRi0NI4CijxO4v65ggnMWMEu03JjKDNLAJWEh0/9MGaRARkJHYu2kzM4gtLKAqcfFo BwtEXEvixYl7TBC2nkTz751sIDYLUM3RUzfB6nkFfCU6GiBqGIEWfz+1BsxmFhCXuPVkPhPE QQISS/acZ4awRSVePv7HCmErSnx8tY8Roj5fYsa/F+wQMwUlTs58wjKBUWgWklGzkJTNQlIG EdeRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKFqcWJ+WmGxnrpRZlJhcX5+fp5aWWbGIE RsTBLb9VdzBefuN4iFGAg1GJh/dBumqYEGtiWXFl7iFGaQ4WJXHeZqYHoUIC6YklqdmpqQWp RfFFpTmpxYcYmTg4pRoYO907JxRr57+4FxvxKfnGXO7n7yMebks81j0hM86/1GFNzJyt6xfK X1wRwB8stnWmytz7/NtON93Zfsp8sradqdh/xuldQU3d1+ccqPXfd9Dw9kaZ8NzDly3bt/26 UsKyM7OT69RjOfkFgmqOD383ZwXInus9wfs1Pfd/7ZG/DHYHM+ReH3X3VmIpzkg01GIuKk4E AGHLQSNpAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RhUPGd8rqy7TcvahvE61FCGiKko>
Subject: [MMUSIC] ICE and RTCP host components
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: Tue, 20 Oct 2015 12:28:19 -0000

Hi,

ICEbis and ice-sip-sdp say that, when a separate port is used for RTCP, separate components are allocated for RTP and RTCP.

Assume the offerer uses a=rtcp to specify a port for RTCP, but the answerer doesn't support the attribute (and instead will use RTP port+1 for RTCP): Does that mean that the offerer needs to allocate RTCP host components both for the a=rtcp value and RTP port+1?

Section 5.1.3.1. of ICEbis talks about the rtcp-mux, when it is now known whether the answerer will support it, but this is about having two different ports for RTCP.

Regards,

Christer

v2.30.2 | Report a Bug | By Email | System Status