Re: Off-topic: making WebRTC work in practice (Re: a brief pondering)

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 06 April 2020 21:28 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 028143A0BDC for <ietf@ietfa.amsl.com>; Mon, 6 Apr 2020 14:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level:
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 K7a_T58otG4X for <ietf@ietfa.amsl.com>; Mon, 6 Apr 2020 14:28:11 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10084.outbound.protection.outlook.com [40.107.1.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B83A83A0BD2 for <ietf@ietf.org>; Mon, 6 Apr 2020 14:28:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IROJeM3tEGHx4b/NVzy676HVHUDslG/v8XcVlR2HIIiwxwHTq3At3V+UZd3nhCGZdnNeQfQoPfDGIYB0uOPuOB5OpihsR7Ex7Rxrq9uodGNHLLIEVGkMGn54Xx7dsmndx64MjsQm234+bKVK5a0e7W8sX0aqTMwkIVcw8ltQGTNYoNm3CHYl/uwjlDznHESZI4w6gLWfI2YhOFXtzaenrzSQvxgm1G5HObBmKjEGYIqWGyRDGMw3fopysBELKmDJXkmJbn0UvXWn1uRxeNUXW54I0BM94hAVt7cYlhG1M09PgocuPjX4WOUlyHlwlFJHRCvADq0S0Oqzd+NX3yRY0Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pv/a/7JOo7v7spkPg1LsHeuw0a+lZWqVbXAtfyYWJw0=; b=hALdi7afZVpOTW3RS9NL6h7WT8L+6zOfT7mcPvplBpEEPFQh25BsC64mqb26QoQS/vk2A9IjcBZzHV3r8dwSe2mz3SmQjf9f0/KyDvsLcCJ3cerK1aUCQ6TzlDJ1eGmBBO+FjM2fz9cDCnqFHIT4huYsf2RnxMJKfKuUvH4WN0W4eeOo/yFrLT7zoBdbagWNSu/ZGzWfmWBvGn3RESNMKPm0RMQW/FgaGqvPorXfK5sX879oH80w+gjaxjOjq7cn55m8khfQrQaaBFA6TWGS6sYHbrkc+kEEhw9uXDS9RehJtTakd0Rh9qC44rOYOuCSCoknGxuLi7KePTWV0zbtpg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pv/a/7JOo7v7spkPg1LsHeuw0a+lZWqVbXAtfyYWJw0=; b=MjSYrBtScijpr7X/Qu3fpMBuw0+War2GHlp25JQBjOoNs2ZaroGKn6v3JIJceePKxVW3wM2+zQZ3zGBi69Ae8U//ev8bFwemfNEzT2oCPehZobg76rempQAHaC+34ZD30vdJ7zPoWEja8xzG4AT5kQNT8MsgzPz+9vwoe2CWT04=
Received: from AM0PR07MB3987.eurprd07.prod.outlook.com (52.134.82.159) by AM0PR07MB4626.eurprd07.prod.outlook.com (52.135.144.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.13; Mon, 6 Apr 2020 21:28:08 +0000
Received: from AM0PR07MB3987.eurprd07.prod.outlook.com ([fe80::57b:b81e:33ec:5512]) by AM0PR07MB3987.eurprd07.prod.outlook.com ([fe80::57b:b81e:33ec:5512%7]) with mapi id 15.20.2900.012; Mon, 6 Apr 2020 21:28:08 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Off-topic: making WebRTC work in practice (Re: a brief pondering)
Thread-Topic: Off-topic: making WebRTC work in practice (Re: a brief pondering)
Thread-Index: AQHWCS2ffEKTNH+pQUK7paEnTu2SSahqlTIAgAAqz4CAAAalAIAAZtWAgAABswCAAW47gIAAAuqL
Date: Mon, 06 Apr 2020 21:28:08 +0000
Message-ID: <AM0PR07MB398753D0DFB365BEDF620B0A93C20@AM0PR07MB3987.eurprd07.prod.outlook.com>
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <31A798F0-9DE0-4231-A768-76BA9A1A2180@tzi.org> <E1FD746D-0BCD-4ECC-BB9B-75DFA05AA9DC@tzi.org> <C9836670-02D6-4A01-8BD2-9F7FDBC990E5@iii.ca> <cce76641-a2d9-a3d6-4d59-55cf2ca31abe@alvestrand.no> <20200405164223.GS88064@kduck.mit.edu> <8EAE0555-F97E-4EFC-A99B-A8F0113C5FA9@gmail.com> <014901d60b9f$ebf75990$c3e60cb0$@acm.org> <37688278-b70e-e10d-1aea-cfa3dfa81334@network-heretics.com>, <f85b54ce-2f3f-6198-d8f4-184085c48b6d@alvestrand.no>
In-Reply-To: <f85b54ce-2f3f-6198-d8f4-184085c48b6d@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [188.127.223.154]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5a676da1-5759-4b9d-9a51-08d7da716689
x-ms-traffictypediagnostic: AM0PR07MB4626:
x-microsoft-antispam-prvs: <AM0PR07MB4626C758DDC59082D84235FE93C20@AM0PR07MB4626.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0365C0E14B
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR07MB3987.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(396003)(136003)(376002)(346002)(39860400002)(366004)(81166006)(19627405001)(2906002)(55016002)(8936002)(81156014)(66574012)(86362001)(44832011)(478600001)(316002)(8676002)(5660300002)(4744005)(52536014)(110136005)(26005)(33656002)(71200400001)(7696005)(76116006)(6506007)(66476007)(9686003)(186003)(64756008)(66446008)(66946007)(66556008); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: LX08Wmfus7RxWD+3mUiCqzinvb8LkifvT8TlklLNfmqwVYjgIkc1+Yu5bdHRXKwmvcC/mwEZcG4tN1MQlBAi5e/MDOJiR3lNYdbvdpnPJH3L0IOyiquEN8wAL3XLDbJS2cqfGSkM7EejWHCOV3MeViKBHg3mdlNKLGDIdYd+aaaaGzwUuqVuTqY4CKeGTx48bQf+RDt2s4f+1FkGN1rybdpM3qwoYIf/4Og1vAgzY5SXbH28rbAeKDrOWfK+M3yAS2lTbAACDZNRxnJi/B27gA6sUyi4KOJ72TqP5YLNLDqaWeZfZ8wf+bBJ3mF9CfXxEOzS2Hh3r31Ut004N6Jqkd2aS4lONh0wzq0vcmLfvj6TvDIPpofvlk8hPENSfRAoftF/T6HJbEqZXWWauZ8hVU3AYYKF/SmSw8cNPl5qGRf/ouJZyCTrpgmF5BRgERTY
x-ms-exchange-antispam-messagedata: ANRmCS8HIffVO9YEQYcw+BflcoRrvJtZuqTknXrBOOY57dSgZUe8rSKMfd5b0Jf50UobNOp+TRt0HoZKzfTmQWAEjnTfWQ+XeQdMoaZHkqmeG/56ku9JVVZC3KyQn6kQmL2qNwd7bSmtMBRIHlz+zg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR07MB398753D0DFB365BEDF620B0A93C20AM0PR07MB3987eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5a676da1-5759-4b9d-9a51-08d7da716689
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2020 21:28:08.2298 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pXQa9N8irc3/bJxruPPUqt8AWrYHNIchr4O2og7ZfCCH8kO6y5MMczNDnYl22OMwSRRnNLXaz8ncEe/Qqi4vhJIAbR8aWbS8ekYu9+nLYKQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4626
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nWVIcBPRWGzMSUN_Qx1Cp8dtH9Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 21:28:12 -0000

Hi,

>>> There should be no benefit to native app except for vendor lock-in.
>>
>> Well, don't discount vendor lock-in.   But of course if the app can
>> communicate directly between peers, whereas the browser cannot, that
>> consumes fewer resources than routing the traffic through the vendor's
>> servers, and likely provides better service to users also.   An app is
>> also better positioned to act as spyware.
>
> WebRTC was designed to allow communication directly between peers.
> Much of the complexity in the stack (which RIPT is trying to get rid of)
> comes precisely from the decision to make it peer to peer.

As far a peer to peer communication is concerned, what complexity does RIPT get rid of?

Regards,

Christer