Re: [rtcweb] What the gateway draft should say about mux/non-mux
"Asveren, Tolga" <tasveren@sonusnet.com> Fri, 31 July 2015 18:49 UTC
Return-Path: <tasveren@sonusnet.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1641B3482 for <rtcweb@ietfa.amsl.com>; Fri, 31 Jul 2015 11:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_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 OFnfZtztmkOX for <rtcweb@ietfa.amsl.com>; Fri, 31 Jul 2015 11:49:27 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0665.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:665]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679DD1B3499 for <rtcweb@ietf.org>; Fri, 31 Jul 2015 11:49:26 -0700 (PDT)
Received: from SN1PR0301MB1551.namprd03.prod.outlook.com (10.162.129.157) by SN1PR0301MB1551.namprd03.prod.outlook.com (10.162.129.157) with Microsoft SMTP Server (TLS) id 15.1.225.19; Fri, 31 Jul 2015 18:49:21 +0000
Received: from SN1PR0301MB1551.namprd03.prod.outlook.com ([10.162.129.157]) by SN1PR0301MB1551.namprd03.prod.outlook.com ([10.162.129.157]) with mapi id 15.01.0225.018; Fri, 31 Jul 2015 18:49:21 +0000
From: "Asveren, Tolga" <tasveren@sonusnet.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Bernard Aboba <bernard.aboba@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] What the gateway draft should say about mux/non-mux
Thread-Index: AQHQy8DcUgzWwtVCmk+8q67BCzjC45316kQQ
Date: Fri, 31 Jul 2015 18:49:21 +0000
Message-ID: <SN1PR0301MB155145AE63D5EF3CF2DF5B2AB28A0@SN1PR0301MB1551.namprd03.prod.outlook.com>
References: <CAJrXDUGs_+AKNHhaJjB5udr9TZv7oFpJ7h3cJ_ToXUfUC5TEpQ@mail.gmail.com> <CABcZeBOH6zCEfuH6xh8-sPSmW3y4Vt2cDudfAAtw5MXq90oyWQ@mail.gmail.com> <SN1PR0301MB1551E28A489A90A93FA2F8BDB28A0@SN1PR0301MB1551.namprd03.prod.outlook.com> <CY1PR0501MB1579BC38B75CBC58744A970FEB8A0@CY1PR0501MB1579.namprd05.prod.outlook.com> <SN1PR0301MB15518198D375F21B973C091DB28A0@SN1PR0301MB1551.namprd03.prod.outlook.com> <CAD5OKxvUUSEyCfJcrxTJj68qKZuw6Ddze1Aw1QxXvTnGXT-qfA@mail.gmail.com> <AF9C5DDA-451E-4ED4-A0AA-9853A3983D59@gmail.com> <7594FB04B1934943A5C02806D1A2204B348E29DA@ESESSMB209.ericsson.se> <CAOJ7v-2B0zO7aAjpf9-39o-Bjr7UB9=78Ry17JP8Fff8z_PMWA@mail.gmail.com> <CAD5OKxvtn66yNf10_eSy-1wkD7PopWrmUNpcF+0O_VAzFXw0sg@mail.gmail.com> <CAGTXFp_DwcE5ybS2yypcezo-42Y60FqabBPBBFTgCkPBhmDeNw@mail.gmail.com> <67196805-ED4E-49EA-83AA-3F4C37B5BC50@gmail.com> <CAD5OKxuSSdE2msiP2Saoaka_6UhZBQPoTk27f=6RRNi8-ARtKQ@mail.gmail.com> <D8E1148E-D03A-40A7-8438-4B5AABDF959B@gmail.com> <7594FB04B1934943A5C02806D1A2204B348E2D52@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B348E2D52@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [50.182.164.80]
x-microsoft-exchange-diagnostics: 1; SN1PR0301MB1551; 5:N30g3O34GzTGe8N/ht1+sm7Tv6NjldoOAZXBPa3qRI2OlfIj2J2mKoPCyE5/EkPWe0QP9iMjdkfLaJwUJwTataGuHyPxzCXyxxm1bQxHOJiCrGD1BdaDK+SElb0WSrhV2Z3NTYu6Zi1BJHASrObfaw==; 24:jEBre4kLJGEOl5T1b/ed6YnSqyo+TnQm+mGdeMcFir0lrOnwn+9EoEO7IUKJPrqJEnJ/2a6vyGj6O5zA6NR2rCH4Y4nQmIUMfVtvepHqxFs=; 20:QVr5Y+hEcd8WAapbFiMirIdk1l8Drpufr+IvRxcdNEOHog6z5MOeE0RUyW4skhimTJG2GwcAuC/T37Xh5Gp/Zg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0301MB1551;
sn1pr0301mb1551: X-MS-Exchange-Organization-RulesExecuted
x-microsoft-antispam-prvs: <SN1PR0301MB1551FC31B384F8B33E4BEFE2B28A0@SN1PR0301MB1551.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:SN1PR0301MB1551; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0301MB1551;
x-forefront-prvs: 0654257CF5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(24454002)(164054003)(377454003)(66066001)(76576001)(74316001)(2656002)(86362001)(2900100001)(87936001)(62966003)(106116001)(77096005)(40100003)(102836002)(92566002)(5002640100001)(93886004)(76176999)(15975445007)(50986999)(54356999)(99286002)(2950100001)(19580395003)(46102003)(33656002)(5001770100001)(5003600100002)(77156002)(122556002)(5001960100002)(19617315012)(19625215002)(5001920100001)(16236675004)(19580405001)(19300405004)(19609705001)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR0301MB1551; H:SN1PR0301MB1551.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_SN1PR0301MB155145AE63D5EF3CF2DF5B2AB28A0SN1PR0301MB1551_"
MIME-Version: 1.0
X-OriginatorOrg: sonusnet.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jul 2015 18:49:21.1038 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0301MB1551
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/1eWYcg9ArF_IsSZq58169k0vekU>
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] What the gateway draft should say about mux/non-mux
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 18:49:30 -0000
Yes, you *could* mandate the whole universe to support it, that shouldn’t be too difficult to describe on paper ;-) OTOH, why? If there are folks, for whom no-rtcp-mux is just fine (for whatever reason), let their implementations function that way (and let them suffer if this is really such a terrible thing from implementation difficulty perspective). And it will be their problem if that causes interoperability issues for them, e.g. they won’t be able to talk to browsers, which mandate use of rtcp-mux. Browsers (or any other implementation) always mandate use of rtcp-mux by always offering it and terminating a session if the answer indicates no rtcp-mux support. Similarly, they can reject offers with rtcp-mux. Thanks, Tolga From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Friday, July 31, 2015 2:44 PM To: Bernard Aboba <bernard.aboba@gmail.com>; Roman Shpount <roman@telurix.com> Cc: <rtcweb@ietf.org> <rtcweb@ietf.org> Subject: Re: [rtcweb] What the gateway draft should say about mux/non-mux Hi, If we choose to mandate usage of rtcp-mux, we could also mandate gateways to support it. Regards, Christer From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Bernard Aboba Sent: 31 July 2015 21:32 To: Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> Cc: <rtcweb@ietf.org<mailto:rtcweb@ietf.org>> <rtcweb@ietf.org<mailto:rtcweb@ietf.org>> Subject: Re: [rtcweb] What the gateway draft should say about mux/non-mux On Jul 31, 2015, at 10:57, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote: Why would the gateway need to negotiate non-mux if rtcp-mux is supported? [BA] IMHO, Gateways should be required to support mux like any other WEBRTC endpoint, but this is not what it says in Section 2 of https://tools.ietf.org/html/draft-ietf-rtcweb-gateways : "If a gateway serves as a media relay into another RTP domain, it MAY choose to support only features available in that network. This means that it MAY choose to not support Bundle and any of the RTP/ RTCP extensions related to it, RTCP-Mux, or Trickle Ice. However, the gateway MUST support DTLS-SRTP, since this is required for interworking with WebRTC endpoints." Assuming that browsers remove or do not implement non-mux, it seems prudent to require gateways to support mux so as to avoid negotiation failures. If we make that change then gateways would always negotiate RTCP-mux with browsers.
- [rtcweb] Proposal: require rtcp-mux (remove non-m… Peter Thatcher
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Peter Thatcher
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Simon Perreault
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Peter Thatcher
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Randell Jesup
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Eric Rescorla
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Peter Thatcher
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Asveren, Tolga
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Wyss, Felix
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Asveren, Tolga
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… richard.vandet
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Asveren, Tolga
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Justin Uberti
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Eric Rescorla
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Christer Holmberg
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Justin Uberti
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Victor Pascual Avila
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Eric Rescorla
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Justin Uberti
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Christer Holmberg
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Rauschenbach, Uwe (Nokia - DE/Munich)
- Re: [rtcweb] What the gateway draft should say ab… Rauschenbach, Uwe (Nokia - DE/Munich)
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Rauschenbach, Uwe (Nokia - DE/Munich)
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Rauschenbach, Uwe (Nokia - DE/Munich)
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Roman Shpount
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… richard.vandet
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Bernard Aboba
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Christer Holmberg
- Re: [rtcweb] Proposal: require rtcp-mux (remove n… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] What the gateway draft should say ab… Eric Rescorla
- Re: [rtcweb] What the gateway draft should say ab… Bernard Aboba
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Bernard Aboba
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Bernard Aboba
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Bernard Aboba
- [rtcweb] Number of DTLS sessions/DTLS connections… Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] Number of DTLS sessions/DTLS connect… Christer Holmberg
- Re: [rtcweb] Number of DTLS sessions/DTLS connect… Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] What the gateway draft should say ab… Rauschenbach, Uwe (Nokia - DE/Munich)
- Re: [rtcweb] What the gateway draft should say ab… Sergio Garcia Murillo
- Re: [rtcweb] Number of DTLS sessions/DTLS connect… Asveren, Tolga
- Re: [rtcweb] Number of DTLS sessions/DTLS connect… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Ranjit Avasarala
- Re: [rtcweb] What the gateway draft should say ab… Eric Rescorla
- Re: [rtcweb] [TLS] Number of DTLS sessions/DTLS c… Martin Thomson
- Re: [rtcweb] What the gateway draft should say ab… Roman Shpount
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Wyss, Felix
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… tim panton
- Re: [rtcweb] What the gateway draft should say ab… Hutton, Andrew
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Simon Perreault
- Re: [rtcweb] What the gateway draft should say ab… Hutton, Andrew
- Re: [rtcweb] What the gateway draft should say ab… tim panton
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… tim panton
- Re: [rtcweb] What the gateway draft should say ab… Jonathan Lennox
- Re: [rtcweb] What the gateway draft should say ab… Eric Rescorla
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Eric Rescorla
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Jonathan Lennox
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Peter Thatcher
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg
- Re: [rtcweb] What the gateway draft should say ab… Asveren, Tolga
- Re: [rtcweb] What the gateway draft should say ab… Christer Holmberg