Re: spin bit in QUIC: troubleshooting

Ian Swett <ianswett@google.com> Tue, 14 November 2017 14:51 UTC

Return-Path: <ianswett@google.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 F0EAF124D6C for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 06:51:19 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 awjt9KQDEZxn for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 06:51:18 -0800 (PST)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45A98124C27 for <quic@ietf.org>; Tue, 14 Nov 2017 06:51:18 -0800 (PST)
Received: by mail-io0-x22b.google.com with SMTP id i38so10094795iod.2 for <quic@ietf.org>; Tue, 14 Nov 2017 06:51:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NIM+EQMfjqavnNTvjQsWTCCzOI5YJCGEcp3tR1RAqtQ=; b=ZwfsjUJiqTWUOAKoPb7RLQZ+kp67AFSE3rTm3yWYcuJlsA72tkm5sHlXJzI2PAch7Y EErHjrArF4e8Vbpq8gfVQSS3JFfqOoTYG94D/Y0pWG/VEmQF1/qMGctcS7H8pZFdhBe6 0qdSj+ntwh6nH/akNDW5xnL3qklscjJ/aTwqSG/d3fbr6PM/gFKevqiO1cJMSiObf1tT YbuueEAeCmhwpFuy02acKb4dA8vMKGQEBdosJOfmOdHaRp9MlWWyKDyHbFdbJIevyZPv Y9j3H3qv8A5AzPKNCkyMhCUYeVhAR7Gpbsu3D2OCUxRbXGYJPDmTwKCsQky/FJSG2I57 PMiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NIM+EQMfjqavnNTvjQsWTCCzOI5YJCGEcp3tR1RAqtQ=; b=Jr8E478Qz2TaN1eJcDcZB4hKDdTLhiSbNpbuxNYV/FnWRfMB+QEw4JTNR7UW1V+VUx Ax6O+hy3043RRZ+cF8B3Quox4/EOD07eluZEdxXGvkKHngkue90UyFR0AAOx3q3n7LhG 53S3mQ8gL3pUYCgOgGmy0qz9fg1GLw5/b0t/RNwWePS6s1fW8EQK5fo9M94zByFVPwJP 6BZGANwbHPX832JOoQTP+OKIZw6IT47Ux+dcK9rA7PAkOSWyV/4PYH1KWgRWD5R0mhpD jrOV32AAOVtyiFSw+12iOn+jclXBxHza0NTixfK+bied/1bqIr13ZN4a66Yt8amBrSZI SbZg==
X-Gm-Message-State: AJaThX4ht8DGsbGAmAxo3fFPGeXu1XQzpwKBi31TbWBvQf8RndBXJWIU Ai99EbVe08C6e3GYmlvDN97nA/RKmOVALm5la7Ighw==
X-Google-Smtp-Source: AGs4zMaSYR+RzGXsI2hdSN//Jq+CIhH7sp21J0XQ53RwyKaWzikzJ9YEQ8YTLPe3TxG9NIpEtWchqwLlaxzzbts8xYI=
X-Received: by 10.107.163.15 with SMTP id m15mr14516740ioe.61.1510671077477; Tue, 14 Nov 2017 06:51:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.130.35 with HTTP; Tue, 14 Nov 2017 06:50:56 -0800 (PST)
In-Reply-To: <11937_1510654451_5A0AC1F3_11937_138_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB924E7E4C5@OPEXCLILM44.corporate.adroot.infra.ftgroup>
References: <11937_1510654451_5A0AC1F3_11937_138_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB924E7E4C5@OPEXCLILM44.corporate.adroot.infra.ftgroup>
From: Ian Swett <ianswett@google.com>
Date: Tue, 14 Nov 2017 09:50:56 -0500
Message-ID: <CAKcm_gPRtyzL+jAd6kBSHvDaCYQtbFwXMVVph1SWezVzmNuU_A@mail.gmail.com>
Subject: Re: spin bit in QUIC: troubleshooting
To: emile.stephan@orange.com
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11402f14f2b742055df28427"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/D6YwGHMgs0N6uUyFkRmSVRD2fK0>
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 14:51:20 -0000

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> 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.
>
>