Re: Q and L loss bits: which is which?

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Tue, 19 November 2019 15: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 89B7A12092C for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 07:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 lAnSC12fmKw5 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 07:08:33 -0800 (PST)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 E860312093C for <quic@ietf.org>; Tue, 19 Nov 2019 07:08:32 -0800 (PST)
Received: by mail-qk1-x72c.google.com with SMTP id 15so18066043qkh.6 for <quic@ietf.org>; Tue, 19 Nov 2019 07:08:32 -0800 (PST)
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=HBD4lVojko/CD4sPjsqpsgxTRnRTCKDpQUGndKhQIuI=; b=m1CuUOX4rWGPy84iJomN3saKimv2BVfJVqXVAmNukVZjKCVLGs70bQyJAEqGY8YwHY ta1GNrM9nYAOfFvwr/mAm7rfd1saV7LTupTXBczTxjJ4VdnJZZ0XXzcdmxEV1xSFyJXn oywiuFAnZD+b4KOaTvuWu4MRip507jy2g9vbAOyCtl4SyvKjQuKUAZvmrkwi6yr7df+x QY0RgjPdzMdp1DwRxrIQ2OMhcM4m48I8H0orS14zP6lEbDGGEAB/dhsTON0j9P7+Rvkz IaB4qhg5K3IP83Oha9Ogu3BLSoiZxe+3/cIA4WJAr2EFFARfFHDHg0/pJUnYVgOz7c/1 60/g==
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=HBD4lVojko/CD4sPjsqpsgxTRnRTCKDpQUGndKhQIuI=; b=Jbe8hgmzAGeDpvquyPerYAFb1MjJne8er8uoQunGFc8hejoVk+7C2NG4P0FdD1sg3G JE7azTfePuyogi/wt1J9IGu8YlKty5E3fNtrz8nvhpECNC2UcP2RC50JwVBs+kI3T2xO mG3ogFLVd6jONOGvQPJ8pgXQoRkaao5RPmQU/cMfrWxG3KZUAIpcmmUWpO9t67/G6a9a 1bveEaYyVhH4AJcxjxez6s0k6JVNOao9keiOiQx4jo3h0GBbZe9kHY4dNgB6XsKHIMt2 4DvBKSZGDpIfTHdweG/hJotdlL7C1jaNEbTan7kjsX/VLSkvJBQlBH6tn+mFCdjxPgsf LKqA==
X-Gm-Message-State: APjAAAUJnkvtsrkkvo4Gd9qS1zY3Tz0/Tp0rwZ8fTjmrIfqjQVmI6H3A ePSemulbNWd6kGC+m8ZsWqGMqw==
X-Google-Smtp-Source: APXvYqwQV4fmZsVA0AAUBw8sghp7CE49SoDoVJJYB3FylZQcRw+6rV608tcP8ro1fwWUp3sGutHQWg==
X-Received: by 2002:a37:6d41:: with SMTP id i62mr16802376qkc.211.1574176111993; Tue, 19 Nov 2019 07:08:31 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id g11sm10148736qkm.82.2019.11.19.07.08.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 07:08:31 -0800 (PST)
Date: Tue, 19 Nov 2019 10:08:29 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: alexandre.ferrieux@orange.com
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Q and L loss bits: which is which?
Message-ID: <20191119150829.GD2789@ubuntu-dmitri>
Mail-Followup-To: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zse1M01VPjddYWo648RbmOabb78>
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: Tue, 19 Nov 2019 15:08:34 -0000

On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@orange.com wrote:
> Thanks for your offer: experimentations are very welcome !
> You're right we forgot to just define which is what, we'll fix the
> draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
> This means the first byte layout becomes:
>  |0|1|S|Q|L|K|P P|

Thank you!

I also assume that these two bits would now be outside of the header
protection?  That is, the short header header protection mask [1] is
now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
don't see how an observer could get at those bits otherwise.

  - Dmitri.

1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1