Re: Structuring the BKK spin bit discussion

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Mon, 29 October 2018 16:08 UTC

Return-Path: <dtikhonov@litespeedtech.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 1AD5C130FF9 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 8LbsGLKMTCPu for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 9C8331292F1 for <quic@ietf.org>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id z2-v6so9877915qts.1 for <quic@ietf.org>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0cDrHLPf8LYDlsTn/hX+qEGgTuYkEFNiaX68XqC2UVA=; b=JFxcXm82uf2yAbN3vtvR30uqxlPpBtD8x6T/vfx0ZvSgVDuIVAOQ411apqJnQJ4fmX c2tROimSDSBkKaUo99X/IwhdkoDBjJ+TcJT1Jwja3eXkMeQxbdzO9jT9XSGxirnuDQZF yYy2I83NqF0QIXI3mfHHn4zBiu/hOWY3LhVMZgJZNCs54WG9E7L+FppAQIttmId+g2n0 I8L0pQzCiLbVJitTTyqnAwubcie2wuKOootz2HOfkz0cQZDxAR85qJB0yNBmmARzYCzD GNPhfgaEBfLwR4s2T6epEoV1Ehi8aFKwk2OqRzVK90jG2loSs5oT3ZrRGDlzP+PF/1XY xVeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=0cDrHLPf8LYDlsTn/hX+qEGgTuYkEFNiaX68XqC2UVA=; b=sI0NR0bq6nul+KDnDOa5E+EaCSTsmurz6DSGck+ytntu84yFY3G7TlOtj1YDm8gJDY 2DQi5Af+G+SW+tud3rgb13RLT2iwQHfm9GWYtsOCPq5Kg71jQp5CRHx7iKz8bMR4EGhV B9jSgxQOod0M9igca1+sATBZneanCxzf2tgYAaMfnqUOSz0NqzzmJpBBfqFp0Ji/QwNg zCxCQ/E8f6jCUhRTJ7mMkSGMEGabNDzwHFp14QCRFVrri0iQJeN1yCY7406pMSWHHRx4 ehWJo+b/k+drZITXkrwjF9BZmGndm7rF1T5PA6TGNZP7hujGn8h2sCEnSmbvRyxBA6Y5 zGbw==
X-Gm-Message-State: AGRZ1gJSA0QxxuuisK4QJX4xM+oYtqRC0G5JPdgSC3kIG5SeVDwXTFhS zc/Ve41jppngnjANeLEHToTYXg==
X-Google-Smtp-Source: AJdET5c0TmZLTuAkNxFf6lRarCqHB7ehgHLnIRH6mnsUg3/JN4M+km9Y2U4ChRLQvnSqL7aygnx9NQ==
X-Received: by 2002:a0c:d94f:: with SMTP id t15mr11739201qvj.189.1540829285668; Mon, 29 Oct 2018 09:08:05 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id t41-v6sm13038278qte.95.2018.10.29.09.08.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 09:08:05 -0700 (PDT)
Date: Mon, 29 Oct 2018 12:08:03 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Lars Eggert <lars@eggert.org>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Structuring the BKK spin bit discussion
Message-ID: <20181029160802.GD7258@ubuntu-dmitri>
Mail-Followup-To: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fDuLqguR7hKXiJNB89K8DJ3EgB8>
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: Mon, 29 Oct 2018 16:08:09 -0000

On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
> We'd specifically like to ask client and server implementors with
> projected sizable deployments to indicate whether they intent to
> implement and deploy, if the WG decided to include the spin-bit in
> the spec.

LiteSpeed Technologies will support the spin bit -- both in our
server and client QUIC implementations -- if it make it into the
draft.

  - Dmitri.