RE: spin bit in QUIC: troubleshooting
<emile.stephan@orange.com> Thu, 16 November 2017 08:37 UTC
Return-Path: <emile.stephan@orange.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 A904B129A9A for <quic@ietfa.amsl.com>; Thu, 16 Nov 2017 00:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 sfA6wXg0wrLR for <quic@ietfa.amsl.com>; Thu, 16 Nov 2017 00:37:34 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B1112955D for <quic@ietf.org>; Thu, 16 Nov 2017 00:37:31 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 1E07A40D00; Thu, 16 Nov 2017 09:37:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.62]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id DFA461A0074; Thu, 16 Nov 2017 09:37:29 +0100 (CET)
Received: from OPEXCLILM44.corporate.adroot.infra.ftgroup ([fe80::b08d:5b75:e92c:a45f]) by OPEXCLILM5E.corporate.adroot.infra.ftgroup ([fe80::2912:bfa5:91d3:bf63%18]) with mapi id 14.03.0361.001; Thu, 16 Nov 2017 09:37:29 +0100
From: emile.stephan@orange.com
To: Salvatore Loreto <salvatore.loreto@ericsson.com>, Marcus Ihlar <marcus.ihlar@ericsson.com>, Roni Even <roni.even@huawei.com>
CC: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>
Subject: RE: spin bit in QUIC: troubleshooting
Thread-Topic: spin bit in QUIC: troubleshooting
Thread-Index: AdNdMS3xiXFl+idYSdWDiJw89tZdFwAHmowAAAE+vIAAAeNlgAABKzeAAAImHGA=
Date: Thu, 16 Nov 2017 08:37:29 +0000
Message-ID: <27425_1510821450_5A0D4E49_27425_244_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB924E7F1C5@OPEXCLILM44.corporate.adroot.infra.ftgroup>
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> <AM2PR07MB0563ABF6900AD100DF15BE0FED280@AM2PR07MB0563.eurprd07.prod.outlook.com>
In-Reply-To: <AM2PR07MB0563ABF6900AD100DF15BE0FED280@AM2PR07MB0563.eurprd07.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: multipart/alternative; boundary="_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB924E7F1C5OPEXCLILM44corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cVILuI-eiljFygjzA-Dkf_nOLuA>
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: Thu, 16 Nov 2017 08:37:36 -0000
+1 De : Salvatore Loreto [mailto:salvatore.loreto@ericsson.com] Envoyé : mercredi 15 novembre 2017 00:54 À : Marcus Ihlar; Roni Even Cc : Ian Swett; QUIC WG; STEPHAN Emile IMT/OLN Objet : RE: spin bit in QUIC: troubleshooting +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<mailto:roni.even@huawei.com>> Cc: Ian Swett <ianswett@google.com<mailto:ianswett@google.com>>; QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>; emile.stephan@orange.com<mailto: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. _________________________________________________________________________________________________________________________ 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.
- RE: spin bit in QUIC: troubleshooting emile.stephan
- Re: spin bit in QUIC: troubleshooting Ian Swett
- RE: spin bit in QUIC: troubleshooting Roni Even
- Re: spin bit in QUIC: troubleshooting Marcus Ihlar
- RE: spin bit in QUIC: troubleshooting Salvatore Loreto
- RE: spin bit in QUIC: troubleshooting emile.stephan
- Re: spin bit in QUIC: troubleshooting Ian Swett
- Re: spin bit in QUIC: troubleshooting DRUTA, DAN
- Re: spin bit in QUIC: troubleshooting Huangyihong (Rachel)
- Re: spin bit in QUIC: troubleshooting Diego R. Lopez
- Re: spin bit in QUIC: troubleshooting Fossati, Thomas (Nokia - GB/Cambridge, UK)
- R: spin bit in QUIC: troubleshooting Fioccola Giuseppe
- RE: spin bit in QUIC: troubleshooting MORTON, ALFRED C (AL)
- Re: spin bit in QUIC: troubleshooting Gorry Fairhurst
- RE: spin bit in QUIC: troubleshooting Piotr Galecki
- Re: spin bit in QUIC: troubleshooting Gorry Fairhurst
- R: spin bit in QUIC: troubleshooting Fioccola Giuseppe
- Re: spin bit in QUIC: troubleshooting Brian Trammell (IETF)
- RE: spin bit in QUIC: troubleshooting Praveen Balasubramanian
- Re: R: spin bit in QUIC: troubleshooting Liang GENG
- Re: spin bit in QUIC: troubleshooting Martin Duke
- Re: spin bit in QUIC: troubleshooting Spencer Dawkins at IETF
- RE: spin bit in QUIC: troubleshooting emile.stephan
- RE: spin bit in QUIC: troubleshooting isabelle.hamchaoui