Re: [tsvwg] Packet Loss Signaling for Encrypted Protocols: draft-ferrieuxhamchaoui-tsvwg-lossbits

"Lubashev, Igor" <ilubashe@akamai.com> Wed, 10 July 2019 16:54 UTC

Return-Path: <ilubashe@akamai.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF6E4120168 for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 09:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 lLOGDfN9XVeO for <tsvwg@ietfa.amsl.com>; Wed, 10 Jul 2019 09:54:33 -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 76218120150 for <tsvwg@ietf.org>; Wed, 10 Jul 2019 09:53:51 -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 x6AGqKUk023535; Wed, 10 Jul 2019 17:53:44 +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 : content-transfer-encoding : mime-version; s=jan2016.eng; bh=H44BWo2vq56M1iETIM/zEirYQ3dUDgCaTSKvAHtuT5I=; b=naRVGrzzk1fKGCPg7Q8whQT/GgA2gj4Zzqa1YXlggT+fCq+uYqRzViVyqLNviV7UcRQ9 ymBCesrTI5pUMPLBhkBhzkJJS5hXa3JAMQnRhY/u0UDAA96MoMkuMoBsJr8wvl0kDizi mR5nc2HDH34KTQQMDJnEkw5HJr+TbLffjLC98i+WwhpPDkCFptwH59m/maEwQ4DqxeyR K67uN6kVc7eH9l/orAfSjwlcE8fjBa7jFdnWq3Ei5RexenNuUBey0KDkAhZAwPm2UawY 2vy6pgnSmnTNZgRw2VtuHlwfODNgoxs355d3+Yam6LOOWF/vilUcGwMUnoL1z/Tb6Tp5 Rw==
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2tnd5v1e44-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Jul 2019 17:53:43 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x6AGlBBa009732; Wed, 10 Jul 2019 12:53:42 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.33]) by prod-mail-ppoint3.akamai.com with ESMTP id 2tjq01saj7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Jul 2019 12:53:42 -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; Wed, 10 Jul 2019 11:53:41 -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; Wed, 10 Jul 2019 11:53:41 -0500
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
CC: Isabelle Hamchaoui <isabelle.hamchaoui@orange.com>, Alexandre Ferrieux <alexandre.ferrieux@orange.com>, Cociglio Mauro <mauro.cociglio@telecomitalia.it>
Thread-Topic: Packet Loss Signaling for Encrypted Protocols: draft-ferrieuxhamchaoui-tsvwg-lossbits
Thread-Index: AdU1z13vAPi6st6TRKOd3SUsz+4ZFQBT3zQQAAfc5OA=
Date: Wed, 10 Jul 2019 16:53:41 +0000
Message-ID: <7b0dc87ecbcc4d498f966bc55ccdb770@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <6d90788c0d1449699378ea75e2bd7a10@ustx2ex-dag1mb5.msg.corp.akamai.com> <E92F9C7E59A8854E8BED73140B879B4E0133400B@lhreml507-mbb>
In-Reply-To: <E92F9C7E59A8854E8BED73140B879B4E0133400B@lhreml507-mbb>
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.32.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-10_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-1907100189
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-10_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=1011 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-1907100190
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/1j0wFRHJXCzXODwtDiXWLZ6Hs20>
Subject: Re: [tsvwg] Packet Loss Signaling for Encrypted Protocols: draft-ferrieuxhamchaoui-tsvwg-lossbits
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 16:54:36 -0000

Giuseppe, thank you very much for this feedback and a pointer to RFC 8321.  We'll definitely mention it in the next rev of the draft.

I see that RFC 8321 did introduce what we are calling a "sQuare bit" for alternate marking of blocks of packets. That's a method to estimate upstream loss.

Our draft is also using what we call "Loss event" bit that allows a single observer to estimate the end-to-end loss as well.  The combination of Q bit (RFC 8321) and the new L bit lets an observer do significantly more than RFC 8321 allows. 

- Igor

-----Original Message-----
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; 
Sent: Wednesday, July 10, 2019 10:54 AM

Dear Igor, Alexandre, Isabelle,
I have had a look at the draft and I think it is an interesting proposal for packet loss signaling and it is good to have a protocol independent document.
In addition, I would suggest to add a reference to RFC 8321 that introduces the packet loss measurement methodology through the alternate marking schema, as reported in Section 3 of your draft. 

Best Regards,

Giuseppe


-----Original Message-----
From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Lubashev, Igor
Sent: Monday, July 8, 2019 11:17 PM
To: tsvwg@ietf.org
Cc: Isabelle Hamchaoui <isabelle.hamchaoui@orange.com>;; Alexandre Ferrieux <alexandre.ferrieux@orange.com>;
Subject: [tsvwg] Packet Loss Signaling for Encrypted Protocols: draft-ferrieuxhamchaoui-tsvwg-lossbits

Alexandre, Isabelle, and I have just posted a draft on a protocol-independent method for endpoints to signal packet loss to the path, while maintaining end user privacy and resisting ossification.  This method can work for any protocol, but the primary focus is, of course, on protocols that encrypt their headers.

We think this loss signaling scheme (just takes 2 bits somewhere that are set by the sender) is an appropriate solution for allowing networks to do their job at providing high QoS and ease of troubleshooting without compromising on encrypted protocol goals.

- Igor

P.S.
  We've implemented this proposal in some Akamai servers and have been using it to serve actual end-user traffic for a subset of Orange customers.  Orange has implemented passive observer that used this signal to detect and identify loss.  We will discuss and analyze the data we collected at maprg (while the signaling protocol details belong to tsvwg).

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

A new version of I-D, draft-ferrieuxhamchaoui-tsvwg-lossbits-00.txt
has been successfully submitted by Igor Lubashev and posted to the IETF repository.

Name:		draft-ferrieuxhamchaoui-tsvwg-lossbits
Revision:	00
Title:		Packet Loss Signaling for Encrypted Protocols
Document date:	2019-07-08
Group:		Individual Submission
Pages:		9
URL:            https://www.ietf.org/internet-drafts/draft-ferrieuxhamchaoui-tsvwg-lossbits-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ferrieuxhamchaoui-tsvwg-lossbits/
Htmlized:       https://tools.ietf.org/html/draft-ferrieuxhamchaoui-tsvwg-lossbits-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ferrieuxhamchaoui-tsvwg-lossbits


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.