[MMUSIC] BUNDLE: RTCP port issue solution alternatives
Christer Holmberg <christer.holmberg@ericsson.com> Wed, 21 October 2015 11:18 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 44A831A8AB4 for <mmusic@ietfa.amsl.com>; Wed, 21 Oct 2015 04:18:52 -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 vqdBYddCZ_Oy for <mmusic@ietfa.amsl.com>; Wed, 21 Oct 2015 04:18:50 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E6EB1A8AB3 for <mmusic@ietf.org>; Wed, 21 Oct 2015 04:18:50 -0700 (PDT)
X-AuditID: c1b4fb2d-f79626d000004282-4a-5627749805e1
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 04.BE.17026.89477265; Wed, 21 Oct 2015 13:18:48 +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; Wed, 21 Oct 2015 13:18:47 +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: AdEL8RXdh8BNoI07RoSt0gj6HwR1Ag==
Date: Wed, 21 Oct 2015 11:18:46 +0000
Message-ID: <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.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B805A7ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+Jvje6MEvUwgz87xS2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujHk/9jAXHDOrOHqtnbGB8ad+FyMnh4SAicSh25NZIGwxiQv3 1rN1MXJxCAkcZZT43HGOCcJZzCixed4j1i5GDg42AQuJ7n/aIA0iAuoSX/f2MIPYwgJmEie2 z2SFiFtL3Pu4nx3C1pOYv3AJWA2LgKpE69StTCA2r4CvxMlH28BsRqDF30+tAbOZBcQlbj2Z zwRxkIDEkj3nmSFsUYmXj/+xQthKEiu2X2IEOYdZIF9i5hEviJGCEidnPmGZwCg0C8mkWQhV s5BUQZToSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsYRYtTi4tz042M9VKLMpOLi/Pz9PJS SzYxAuPh4JbfujsYV792PMQowMGoxMObsFMtTIg1say4MvcQozQHi5I4bwvTg1AhgfTEktTs 1NSC1KL4otKc1OJDjEwcnFINjFN1rdnE/JWjNYvmhf+aFRx1NM4pYE/w20CdnDkcVrJeC32d 5/93a9pWczK5/+Rp95Ce19t9K9+lSM+ukDT+uffZQsvrJpM2+Kcq/tP3D46fc8nZZ45N0vvk f3/0M5a//fN3i42cZMMGq33ZTZX7z4mvuvZO7pmSl6B5YJpm9sLQV5OMC9rvKbEUZyQaajEX FScCAPNXqLZoAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PBHVkxiF_4Z82jCoQEtC0MhleQ4>
Subject: [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: Wed, 21 Oct 2015 11:18:52 -0000
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
- [MMUSIC] BUNDLE: RTCP port issue solution alterna… Christer Holmberg
- Re: [MMUSIC] BUNDLE: RTCP port issue solution alt… Christer Holmberg
- Re: [MMUSIC] BUNDLE: RTCP port issue solution alt… Christer Holmberg
- Re: [MMUSIC] BUNDLE: RTCP port issue solution alt… Paul Kyzivat