RE: Packet Loss Signaling for Encrypted Protocols - draft-ferrieuxhamchaoui-tsvwg-lossbits

"Lubashev, Igor" <ilubashe@akamai.com> Tue, 09 July 2019 15:19 UTC

Return-Path: <ilubashe@akamai.com>
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 6D06B120637 for <quic@ietfa.amsl.com>; Tue, 9 Jul 2019 08:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=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=akamai.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 j7B5CPTyb7kS for <quic@ietfa.amsl.com>; Tue, 9 Jul 2019 08:18:57 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 96A4C1205FB for <quic@ietf.org>; Tue, 9 Jul 2019 08:18:53 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.27/8.16.0.27) with SMTP id x69FC6Nf011882; Tue, 9 Jul 2019 16:18:48 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=vBMHlfL6c2+uqG3zMTxQa4AYTERaVDJt8+AnbSr+63w=; b=IbteiiODldSJu7oHbgyRGCcyPnKvMmQJK8wjZWgqnq5/WZ42MsGyd8uAYPy/1Loa7l/M 7oZwRLqa6gu3VUft+w7aswaPrj89aABGavZZTQZI7Xes7EbinnUPUdKlMY05MA0Yl9lV xaDBG0yKX5CQuntCtXO37P8OEVEPtc2h2SKCtOwBPnyxwc6Xd99dZi2/w+XnllSiOAd+ ILNZQ+/NNbGK/rFoSAKZ3k/AFRD7qmAPXSI06zBH5ckS/+b4Bhakmk+5ahtDjime9qvW qEnT7zVFF3O5Pflob0ywKdcVjvHqcF/ruPQ68Ml4vow6w9pJI6ANc9r5r09Vjyznn8uU +w==
Received: from prod-mail-ppoint7 (prod-mail-ppoint7.akamai.com [96.6.114.121] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2tjk635ed7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 09 Jul 2019 16:18:48 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x69FHPem008538; Tue, 9 Jul 2019 11:18:46 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.30]) by prod-mail-ppoint7.akamai.com with ESMTP id 2tjpyxryk9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 09 Jul 2019 11:18:45 -0400
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.27.105) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.27.103) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Jul 2019 10:18:42 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.27.105]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.27.105]) with mapi id 15.00.1473.004; Tue, 9 Jul 2019 10:18:42 -0500
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>, "quic@ietf.org" <quic@ietf.org>
CC: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "isabelle.hamchaoui@orange.com" <isabelle.hamchaoui@orange.com>
Subject: RE: Packet Loss Signaling for Encrypted Protocols - draft-ferrieuxhamchaoui-tsvwg-lossbits
Thread-Topic: Packet Loss Signaling for Encrypted Protocols - draft-ferrieuxhamchaoui-tsvwg-lossbits
Thread-Index: AdU2CmyJiha8kWgiTzSY5F1e75TnXwAVrpiAAAHI7DA=
Date: Tue, 09 Jul 2019 15:18:42 +0000
Message-ID: <8dac9ac39a5d4e75ac9de2799ff423d1@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <f405ea70fc994867b3585b267106bc84@ustx2ex-dag1mb5.msg.corp.akamai.com> <CAN1APdfzzu91NVi7mDLDKUS8hkttKLBcOATg-a5DG_XLBc6GhA@mail.gmail.com>
In-Reply-To: <CAN1APdfzzu91NVi7mDLDKUS8hkttKLBcOATg-a5DG_XLBc6GhA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.122]
Content-Type: multipart/alternative; boundary="_000_8dac9ac39a5d4e75ac9de2799ff423d1ustx2exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-09_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907090180
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-09_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907090180
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5gzJ_hEK6Z0em5AcrRNITSxL-MU>
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: Tue, 09 Jul 2019 15:19:01 -0000

From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>


The Q Period needs to be chosen carefully, since the observation could become too unreliable in case of packet reordering and loss if Q Period is too small. However, when Q Period is too large, short connections may not yield a useful upstream loss measurement.

Wrt. short connections, do you mean low-latency, small RTT, or short-lived?

By “short” I mean too few packets sent (fewer than half Q Period).  I will clarify this in the text. Thank you.

While this looks interesting, can you explain how the objectives compete or differ from the spin bit, and quality and information provided?

Latency Spin Bit (aka “spin bit”) measures connection rtt.  The proposed mechanism measures packet loss.  So the two are complementary measurement signals.

  *   Igor



On 9 July 2019 at 06.45.42, Lubashev, Igor (ilubashe@akamai.com<mailto:ilubashe@akamai.com>) wrote:
Alexandre, Isabelle, and I have posted a draft on a method for endpoints to signal packet loss to the path, while maintaining end user privacy and resisting ossification. The method is protocol-independent, but of course you get the most benefit by applying the method to encrypted transports, and QUIC is what people usually think of first in such context.

The draft is not targeted at the QUIC WG specifically, since it is describing a general method of such loss reporting. But we do mention QUIC, so the WG may find it interesting. We would welcome feedback from the QUIC WG.

Lars, Mark, I am sure the meeting agenda for Montreal is pretty tight, but if the WG is interested, we are happy to have a quick QUIC-specific presentation on this.

Thank you!

- Igor

P.S. We've implemented this proposal in some Akamai servers and have been using it to serve actual end-user QUIC traffic for a subset of Orange customers. Orange implemented a passive observer that used this signal to detect and identify loss. We can share the high-level of the results and will share the detailed analysis of the data and measurement techniques in maprg.

---------------------

https://datatracker.ietf.org/doc/draft-ferrieuxhamchaoui-tsvwg-lossbits/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dferrieuxhamchaoui-2Dtsvwg-2Dlossbits_&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=Djn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&m=8tqj3OKmcGwAeTvifbhpZNwiGgQQrld_04cGqddUgas&s=GDUFlTwCpg_Ewg6sZuR0uKLJ5gLiW8qRPrb88Eoscr0&e=>

Abstract:
This document describes a protocol-independent method that employs
two bits to allow endpoints to signal packet loss in a way that can
be used by network devices to measure and locate the source of the
loss. The signaling method applies to all protocols with a protocol-
specific way to identify packet loss. The method is especially
valuable when applied to protocols that encrypt transport header and
do not allow an alternative method for loss detection.