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

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 20 November 2019 01:48 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 02C3A12093B for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 17:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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] 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 F80lA5RGBevc for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 17:48:53 -0800 (PST)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 7451D12092A for <quic@ietf.org>; Tue, 19 Nov 2019 17:48:53 -0800 (PST)
Received: by mail-qt1-x831.google.com with SMTP id t20so27123133qtn.9 for <quic@ietf.org>; Tue, 19 Nov 2019 17:48:53 -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=7tlHXPdxdRI6LTbixIbcbE5VcvRYjYoXHU01kT2gaX8=; b=qS5DNJksfRESGKD+cD8EN3xXvgwDcMG67YgogZK+N+BurIRDKFHzQsoj1KB2SvuJBo weaS3cWQEN65JuZ0GuNbPp1GR9b3ASTZLCkXihsFI+Anrp9irFAOlYRxpF0eblTXjGFO PWbUK7IBu4mcB9spDkHiYf586GIQFgTFadY7BB/hjdCdBZ64JuoLN9SziqeCnSA8kNGe qweXyGxlMn34FZ4LuY6wF5+i5gVRD9OJhL6txCn0HTgQl42mqg8tiQcwEzXTv4PmASDo A+WgXLPPqG2IPz6ci7Ly9qIciTEDJOVB10cMXbTB5eZwuA2z3HUV16YYsU72Va1l0sJq 6iGA==
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=7tlHXPdxdRI6LTbixIbcbE5VcvRYjYoXHU01kT2gaX8=; b=LFvzdD9/WlESdM0XVxdXCGomEutzElemFJmrjjcj9qnxZbC71WZz5s9hNr6VjLDkP+ qwGXobMjl7Y/5fq5K4gkuAJK30yh6f7bVLxPj4asWqp0VqG+40C+y64aRNeyMMZObErt N+SPha/nLSlozzuylz712yQI9ww5gFHMPSAjbAoMbK3/3mtEOGTtqIgexIfwDGhAxmuj +m+MwwW3NpEI7HvUOpvKvsB1+SF41x3+HneUxGaIOwW3oWaLnED+pEfoysmXqQaxJT06 k+RlUl2ki3W5eVVmsnhnqoY7rEpJtFPMhTJsQX+QfADZbGVLEYctsunxXvNjMB6yj8e7 365g==
X-Gm-Message-State: APjAAAVuqlx4hr46Bx7oNYftybvqF0FN6zZUEtLnbgWpU/ixUJ6zg2hP QzwYL4qB4HyMuwmkoJuiPNLlzw==
X-Google-Smtp-Source: APXvYqyjTKfZDEsWtKhQkExtZ3njGQMCV5+rWRCCtg3Zq8ylLNzbxCWxYnf+EY29VjSv0ZaqEkDosg==
X-Received: by 2002:ac8:3209:: with SMTP id x9mr330502qta.293.1574214532494; Tue, 19 Nov 2019 17:48:52 -0800 (PST)
Received: from ubuntu-dmitri (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id w23sm13904214qtw.87.2019.11.19.17.48.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 17:48:52 -0800 (PST)
Date: Tue, 19 Nov 2019 20:48:50 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Christian Huitema <huitema@huitema.net>
Cc: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
Subject: Re: Q and L loss bits: which is which?
Message-ID: <20191120014850.GC16017@ubuntu-dmitri>
Mail-Followup-To: Christian Huitema <huitema@huitema.net>, 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> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/W75mWl52BDx78WVqfEdDq94YAZQ>
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: Wed, 20 Nov 2019 01:48:55 -0000

On Wed, Nov 20, 2019 at 07:19:09AM +0800, Christian Huitema wrote:
> I am willing to do the same in Picoquic, but I would really like to get
> the transport parameter defined first.

Once there is a TP and a draft, we plan to include this option into
main line of lsquic.

  - Dmitri.