R: About to measure Explicit Performances on user devices (mobile phones, PCs)

Cociglio Mauro <mauro.cociglio@telecomitalia.it> Wed, 15 July 2020 09:12 UTC

Return-Path: <mauro.cociglio@telecomitalia.it>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C153A0365 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telecomitalia.it
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 co7M_RFmXW5y for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 02:12:20 -0700 (PDT)
Received: from mx05.telecomitalia.it (mx05.telecomitalia.it [156.54.232.21]) (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 020AB3A0121 for <quic@ietf.org>; Wed, 15 Jul 2020 02:12:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=telecomitalia.it; s=selector1; c=relaxed/relaxed; q=dns/txt; i=@telecomitalia.it; t=1594804335; x=2458717935; h=MIME-Version:From:Date:Message-ID:Subject:To; bh=GzhfOuvISrwJaupQkF+xnhkYKR5KmkUBSAxxF6sJLWU=; b=c7kE1HgimDQ1ECjiM0JC4ZJZMrPlHZO7DU2ZY/lfBWcuNbdej+jLtcGkCvHGWPlo 7Ea4dMKrwjOdjZ4xx+mdHH04WMIt/ZZxMQk5A+NE8SOcnGowisZY+EYOFYo5DVBE PdMVOZQ7OaAzErxyhiR9PDd3WRxu47JhnbRi6YtJqzGUK27TUCO59aJoVtqSSWSW FecSzOlJ2vBBb+plXfAyK6gxifQKMtvgn5Bbx06LNWfeIexWuUpnZRI/vRp0xis6 RYyEbkGYRqDjI3uuvyDcrRgiX3JOq/mynUy2pfIj2hTfTCbnn/VdBmyXNRbXQObj 1URwCQ6KtrXvKvwuEa0Yvw==;
X-AuditID: 0a5a2d15-e41ff70000008cc1-96-5f0ec86febb9
Received: from TELMBXD11BA020.telecomitalia.local ( [10.90.43.45]) by mx05.telecomitalia.it () with SMTP id FF.92.36033.F68CE0F5; Wed, 15 Jul 2020 11:12:15 +0200 (CEST)
From: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
CC: "ippm@ietf.org" <ippm@ietf.org>, "quic@ietf.org" <quic@ietf.org>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, Nilo Massimo <massimo.nilo@telecomitalia.it>, "Bulgarella Fabio (Guest)" <fabio.bulgarella@guest.telecomitalia.it>, "riccardo.sisto@polito.it" <riccardo.sisto@polito.it>
Subject: R: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Topic: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Index: AdZQhy9WxJZw9I9ETrSFmbU5QsD6MAEZxd9wAWYsnkA=
Date: Wed, 15 Jul 2020 09:12:14 +0000
Message-ID: <da0613120a1443d4bec6927a6b49d11c@TELMBXD14BA020.telecomitalia.local>
References: <8c2df3da5f8c4450b272e3224dd23e46@TELMBXD14BA020.telecomitalia.local> <LEXPR01MB1040583A254B9FCEE49FF50D9C670@LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEXPR01MB1040583A254B9FCEE49FF50D9C670@LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [62.77.47.76]
x-ti-disclaimer: ADBanner
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsXCFaWtq5t/gi/e4Pd3Xos1c1YwWfQ8eMds 0bOA2+Ln7Z3sFh+mcTiwerQcecvqsWTJTyaP0yuLPdpeKgSwRHHZpKTmZJalFunbJXBlTDq7 gqWgUbti67K5rA2MD5W7GDk5JARMJI5sn8XWxcjFISSwilGi6cAdFpAEm4CZxJktz9hAbBEB S4k9s5aygxQxC6xkkmjq/cQIkhAWiJQ41LSEEaIoWuLJ8hnsELaVRMuKKUwgNouAqkT/qg+s IDavQKDEwh9TWSC2LWaUeNV3Cmwbp0CMRMvpSWBFjAKyEhN2LwIbyiwgLvFi+gl2iFMFJJbs Oc8MYYtKvHz8jxXCNpDYunQfC4QtL/Fhw3eoGkmJw4c3sUHM0ZO4MXUKlK0tsWzha2aIgwQl Ts58AtYrJKAjcfn+IbYJjOKzkKyehaR9FpL2WUjaFzCyrGIUza0wMNUrSc1JTc7PzSxJzMlM 1Mss2cQIjkJd0R2M21a80TvEyMTBeIhRgoNZSYSXh4s3Xog3JbGyKrUoP76oNCe1+BCjNAeL kjivLTC+hQTSE0tSs1NTC1KLYLJMHJxSDUxzvl13DnkWUWx7mTXv0dvY+AuqHf7ORftmCxdv PPbpwX2jrx2Zt8sebEyck7O6bcO2p/9O/DpTvkvcS/ha0MuyT8EJ5z+W7W/TKNiZneCU4S0i 7fj07M41HM8rSnScAmUvtDJu45mo+IE5c47IRI8n2YZLtgb0znkfsNZO0ljzY1kT87SD6S/X tCZZ6Gu/t7Y9IHl2sb9CyaJDk7+szi63NMybOYVB5dfX5pNcWaFZn77du7v13tlN2YfD889N d7+/deuC7GBrxn2fdypwNkn+dd2Ukh9y/slq8dtv66TeTJMKKmsxlPTfm/86SdV86Y+4XVrN CRvXnzNxX1u6+29tdcDn7e8crd+1zp7Me1VFiaU4I9FQi7moOBEAnrevRjEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/B2cGSfmzTKapBqRy8iSQ765X04o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2020 09:12:24 -0000

Thanks Ruediger for your interesting comments.
Your suggested option to increase connections with randomly generated performance bits could be applied on connections that originate from users' devices that have not activated (or have actually deactivated) the explicit measurements.
As you wrote, in this case, connections with "variable" performance bits (either "random" or "correctly" set) could be the majority and it would be quite difficult to prioritize this traffic.
Best regards.
Mauro

-----Messaggio originale-----
Da: Ruediger.Geib@telekom.de <Ruediger.Geib@telekom.de> 
Inviato: mercoledì 8 luglio 2020 08:35
A: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
Cc: riccardo.sisto@polito.it; ippm@ietf.org; quic@ietf.org
Oggetto: [EXT] AW: About to measure Explicit Performances on user devices (mobile phones, PCs)

Hi Mauro,

You suggest to base activation of the spin bit marking on a terminal configuration or on a user decision. That is reasonable, I think. An additional option is to activate the spin bit randomly on a number of connections. That might help to avoid situations where a set spin bit indicates that the performance of this flow is "rather likely" reported. A bit indicating that a flow's performance is likely to be reported to one or more interested parties should be taken as an incentive for preferential treatment.

The number of flows with randomly activated spin bit should be higher than those reporting performance, if this option is pursued.

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: ippm <ippm-bounces@ietf.org> Im Auftrag von Cociglio Mauro
Gesendet: Freitag, 3. Juli 2020 14:33
An: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>; quic@ietf.org
Cc: 'Riccardo Sisto' <riccardo.sisto@polito.it>
Betreff: [ippm] About to measure Explicit Performances on user devices (mobile phones, PCs)

Dear QUIC and IPPM WG members.
 
After Spin bit introduction, and now with packet loss measurement proposals*, the Explicit Performance Monitoring on client-server protocols (e.g. QUIC) becomes an interesting topic for Telco.
Explicit Performance Monitoring enables a passive Observer to measure delay and packet loss only watching the marking (a few bits) of production traffic packets.
 
We propose that the first place where to put the Explicit Performance Observer is on the user device (e.g. mobile phones, PCs).
Main reasons of this choice.
1. Scalability. On the user device there are few connections to monitor.
2. The Observer can monitor both directions: upload and download (inside the network is not always possible).
3. Some measurements, natively not end2end, became E2E (e.g. packet loss Q-bit) 4. It's possible to set alarm thresholds on the user device (and to signal to network probes to monitor only the sessions with impairments, in order to segment the performance measurements and to locate the faults). In this case observers, also embedded into network nodes, need to monitor only a limited number of connections (the ones that have problems).
 
Of course, to do this, the decision whether to activate the marking (e.g. Spin Bit) or not must be made by the device owner configuring the applications (e.g. browsers) based on protocols that supports Explicit Performance Monitoring (e.g. QUIC).
 
All applications should therefore provide for the activation or deactivation of the marking for the Explicit Performance Monitoring.
 
So, from this point of view, in the Client-Server handshake it should be the Client who decides whether the marking is active or not within a session and the Server should adapt.
 
The performance information thus obtained could then be kept on the user device or sent to "external bodies" according to the will of the device owner..
The main recipient would be the Internet Service Provider (see point 4 of the previous list), but these data could also be of interest to the national regulatory authorities and perhaps others.
 
Feedbacks are welcomed.
Best regards.
 
Mauro

* Explicit packet loss measurements proposals:
1) https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02
2) https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-03

 
_____________________
Mauro Cociglio
Telecom Italia-TIM
Via G. Reiss Romoli, 274
10148 - Torino (Italy)
Tel.: +390112285028
Mobile: +393357669751
_____________________
 


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. 

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 

Rispetta l'ambiente. Non stampare questa mail se non è necessario.

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm