RE: spin bit in QUIC: troubleshooting

Salvatore Loreto <salvatore.loreto@ericsson.com> Tue, 14 November 2017 16:54 UTC

Return-Path: <salvatore.loreto@ericsson.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 EDB9D127843 for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 08:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 MucAkrAHBEWX for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 08:54:13 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 25EF2128CF0 for <quic@ietf.org>; Tue, 14 Nov 2017 08:54:12 -0800 (PST)
X-AuditID: c1b4fb3a-c5bff70000004c48-e1-5a0b1fb33f0c
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6D.69.19528.3BF1B0A5; Tue, 14 Nov 2017 17:54:11 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.21) with Microsoft SMTP Server (TLS) id 14.3.352.0; Tue, 14 Nov 2017 17:54:11 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YcfFMPyOYwbrvoxoLnVFDL34oa8YQCNu7pES/TiXOEY=; b=W3p6/BF/t3EtXVR6A1s+24hmscK4mZ0vlML7LMRwZ9Ng5B1m5Xx/BoJUTJIsHB1fHB1W4ovYnE1MeD0zViP0T806b+F03Opm5omVrVSmO6Es/n5iKP9VRIAWF/THeeS1GjU7tISN6nPPfd+a0/j5A0iiqhmd2fYRdBLPX3XMkQ4=
Received: from AM2PR07MB0563.eurprd07.prod.outlook.com (10.160.32.21) by VI1PR07MB3247.eurprd07.prod.outlook.com (10.175.243.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4; Tue, 14 Nov 2017 16:54:09 +0000
Received: from AM2PR07MB0563.eurprd07.prod.outlook.com ([fe80::51b:b1d2:5312:ddb6]) by AM2PR07MB0563.eurprd07.prod.outlook.com ([fe80::51b:b1d2:5312:ddb6%15]) with mapi id 15.20.0239.004; Tue, 14 Nov 2017 16:54:07 +0000
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>, Roni Even <roni.even@huawei.com>
CC: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, "emile.stephan@orange.com" <emile.stephan@orange.com>
Subject: RE: spin bit in QUIC: troubleshooting
Thread-Topic: spin bit in QUIC: troubleshooting
Thread-Index: AdNdMS3xiXFl+idYSdWDiJw89tZdFwAJsv0AAAE+vIAAAeM/AAABBYeg
Date: Tue, 14 Nov 2017 16:54:07 +0000
Message-ID: <AM2PR07MB0563ABF6900AD100DF15BE0FED280@AM2PR07MB0563.eurprd07.prod.outlook.com>
References: <11937_1510654451_5A0AC1F3_11937_138_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB924E7E4C5@OPEXCLILM44.corporate.adroot.infra.ftgroup> <CAKcm_gPRtyzL+jAd6kBSHvDaCYQtbFwXMVVph1SWezVzmNuU_A@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD836D79@DGGEMM506-MBX.china.huawei.com> <37B26B29-2193-443B-8B27-0CF68A8619CA@ericsson.com>
In-Reply-To: <37B26B29-2193-443B-8B27-0CF68A8619CA@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [31.133.152.63]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB3247; 6:lfAoAPd8vqcIStujYQjfMVNjwxkLD8pMRucXdvtvpomwGu6VpchmnBS+Kmnq8uOkyifMYP4nlYxC0gVZN3jBRFLUBCCiEtVkEp8e57OIrQYyETCwOe5b9K0WBet7QrVJjn5JBVMoxyx4exBpYZuoN8KFZl3Bf+WG//CKa6q+fIe9ZditJA41uaE48cE3JmQHPDWlYy54DGlz0UtpGdGrtmIwT6P0L9jeTZE5EOfKa4lE8fQS0u8yQCvbU5M7e0+PoKEBomknAeGn30mWaUOqt+Jdq8+nNB0B3hSEHSzJhhGuPPVC30e+VzldbW9ladq664D0O43sEw7PXcb2r9uGIdV/4VXh7hQqf7opasfK3EQ=; 5:ApHd/PBhb/rBz4uYsHgnFbC3JYvizUaPdHVNjRDDX9uzpoZpzmNhrHqDJ89FWyMOwFflFb/WQISCkyQ/gRJxfyFvYufvpPjRMaGkntJ+MmlQt4bntxnhnvG9lsI/NajfTHzjVDkK3FEpffoHoHUtf7hCziLVhoCf45BlzWqfNo8=; 24:YR4e1R05N0GcqnZFcYBaea2p9G7k70NIUc6iArO8caXc2/LvEtYFMvI8i7i+NYnBrOXGEqczQ3Wthi0MsEAmcZNYSAFrvEAfgwXy/Oh0JY0=; 7:PqW4r3eKHPTzk8dTTO2/stdf2+lNFBaSOUfQq+XudB6CmPLnbBL6vZK1PCMsJejT2ti6y3wv/oz3IAtS5h5vMv9YtfUu7Tk9l3qFEBxOJFc6DLceeNZsRR7Olgri9HjfvDUxRNDFQ2rltyCBgdiNe7/lmK0YGIEDZaU6l4yb9SeSS/w849kX1m1lPAi27Az49BTdwiLtGLGpY1UubYDKoFYZ9JU9kUDMNt2BCUNrncL19bXHDILm4gc+qqOHrEN3
x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(24454002)(51444003)(199003)(189002)(76176999)(54356999)(33656002)(53546010)(50986999)(189998001)(53936002)(99936001)(101416001)(68736007)(229853002)(4326008)(478600001)(6116002)(3846002)(790700001)(102836003)(14454004)(55016002)(316002)(66066001)(54906003)(110136005)(6246003)(97736004)(81156014)(93886005)(6436002)(106356001)(6506006)(105586002)(81166006)(7736002)(2950100002)(74316002)(7696004)(5660300001)(99286004)(6306002)(236005)(8936002)(5250100002)(2906002)(86362001)(2900100001)(34040400001)(3660700001)(54896002)(3280700002)(9686003)(8676002)(5890100001)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB3247; H:AM2PR07MB0563.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: 8c970317-bb44-497d-9fc7-08d52b805245
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603258)(49563074); SRVR:VI1PR07MB3247;
x-ms-traffictypediagnostic: VI1PR07MB3247:
x-microsoft-antispam-prvs: <VI1PR07MB32479328DF05B2620CA1C0EDED280@VI1PR07MB3247.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(50582790962513)(211936372134217)(227612066756510)(153496737603132)(18271650672692)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(2401047)(5005006)(8121501046)(3002001)(3231022)(920507027)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6041248)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123558100)(20161123555025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:VI1PR07MB3247; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:VI1PR07MB3247;
x-forefront-prvs: 04916EA04C
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=salvatore.loreto@ericsson.com;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_000D_01D35D71.8F62C9A0"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8c970317-bb44-497d-9fc7-08d52b805245
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Nov 2017 16:54:07.7333 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3247
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA1WSa0hTYRjHec9tc2txnK4ezCinfZnkvRgaohAyocJvlQk56qSiTjlnShco PyjIzFx5KWempY0ywUuWl4TcUlPLtDBFLcPSJO2CJmiWrm3vhPr2e27///O8vGJSvkZ7iVN0 eo7XadOUjIQqP9aq2PtwlzQ+6M6Yt9rydJVS/5pqp9WXq6Xqpd4hKorSVDdnaXK7v9Ga2tpf hCb3cz8TR8VLDpzm0lKyOT4wMlGS3G/rpDNLnqGz85M9ZA4abUIG5CYGNgy61lfsLBHL2WcI xgrqXUEfgqI1C+0IKLaQhAHDAI0rZQQsr46QOJhGYHvcxjjEGHY/zE23kA72ZI/AbJ/BaUKy WTBXe8/JHmwAfKjsQrgnEEzFEy6OgT/1G4QBie12e6D9uo8jLWMTwJzzWYS9XhFga2yiHAU3 NgqMDV1OX8Rug5WBegJ7bYeJmSoCH+cJ069fMJgV8OXTBu3QB9YHRs2xOL0T3lQVOE8G1iqC t42PXLOhYDB20rhwl4HWwW8EHj4MGz8v4XwNgvWvV1yiKng+cgbPpsLS+0KX6C0EZT0VIhzM 02B70kbhLm/oupnHGNFe0z+Lm+x9JFuIoONqO2NyPoE79JfPULjpBFg/GUWY/WF2fJbaZPPt BdJkX4S0L1Jjiv0/7eAIuLFmYTD7QEnBtEtmHyz0LKJqJK1DCoEThPSkkJAAjk85JQgZugAd p29G9l9oafkd3oYsc9FWxIqRcotsi7c0Xk5rs4Vz6VbkZ9f52PhgGHlRugwdp/SUtZsk8XLZ ae258xyfcZLPSuMEK9ohppTbZRpP+ySbpNVzqRyXyfGbVULs5pWDIvWLk/nzp1SqhF71wHDK TJvtd6lC+iMyLu6QmaywLSz5NhwPiXG/X/muv3q91KPjWrHane8Y8o/u5qdawgsk43nE5aMT P5Z7siJ8Ms/uTgwNKr7wfXVx7WJC2KKoaGhrX5PRb0Qfpwg2K9xmdL5JSfkjBxMH6/KDhiNe 5tc2flRSQrI2WEXygvYvDJAQ4I0DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JL51jAVHm8SmeuLZNRtJ_HD39H8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Nov 2017 16:54:16 -0000

+1

Latency is the most crucial component needed in Quic version 1

 

Also considering the fact that QUIC will be either most likely adopted in 3GPP for 5G SBA

and the majority of the traffic in 5G networks QUIC (per Georg Mayer mail on those points)

Operators will have to make sure to keep the latency really low in 5G networks and they

will be measured on latency.

 

/Sal

 

From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Marcus Ihlar
Sent: den 14 november 2017 17:21
To: Roni Even <roni.even@huawei.com>
Cc: Ian Swett <ianswett@google.com>; QUIC WG <quic@ietf.org>; emile.stephan@orange.com
Subject: Re: spin bit in QUIC: troubleshooting

 

+1 on Ronis statement below. 

Let us begin with latency, which is the most crucial component to have in place. 

As V1 gets deployed we will get a better understanding of what else might be needed. 


On 14 Nov 2017, at 23:27, Roni Even <roni.even@huawei.com <mailto:roni.even@huawei.com> > wrote:

I think that latency is what we need right now.

Once we understand more about quic and packet loss (will ECN be used reducing packet loss) and other functionality we can see what else is needed. This may be done in next version using variants.

Roni

 

From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Ian Swett
Sent: יום ג 14 נובמבר 2017 16:51
To: emile.stephan@orange.com <mailto:emile.stephan@orange.com> 
Cc: QUIC WG
Subject: Re: spin bit in QUIC: troubleshooting

 

What would the other bit or two be used for?  If there is no standardized use of those bits in v1, then I believe we should wait to reserve them when their usage is defined, given we'd need a version bump to specify how they were being used.  At the moment, the management use case is not competing with anyone else for bits in the short header.

 

On Tue, Nov 14, 2017 at 5:14 AM, <emile.stephan@orange.com <mailto:emile.stephan@orange.com> > wrote:

Hi

 

Last week Orange experienced a fallback of QUIC to TCP on one of its networks. The issues were not visible in QUIC traffic. The troubleshooting was made using TCP packets information. This is not sustainable on the long term when numerous applications using different versions of QUIC will stop to fallback to TCP.

 

Based on the exchange we had in the RTT design team and in today meeting , it sounds reasonable to reserve at least 2 bits (ideally 3 bits as discussed in the design team) for manageability in the QUIC invariants and to start experimenting the spin bit in QUIC V1.

 

Regards

Emile

 

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.