CONEX? (was: Re: Q and L loss bits)

Lars Eggert <lars@eggert.org> Thu, 21 November 2019 06:42 UTC

Return-Path: <lars@eggert.org>
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 972EC1200B5 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 WaTeAbK1_64S for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:42:42 -0800 (PST)
Received: from emh02.mail.saunalahti.fi (emh02.mail.saunalahti.fi [62.142.5.108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD28D12000F for <quic@ietf.org>; Wed, 20 Nov 2019 22:42:41 -0800 (PST)
Received: from eggert.org (unknown [62.248.255.8]) by emh02.mail.saunalahti.fi (Postfix) with ESMTP id B12B5200D2; Thu, 21 Nov 2019 08:42:37 +0200 (EET)
Received: from slate.eggert.org (Slate.eggert.org [172.19.235.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id E206D613195; Thu, 21 Nov 2019 08:42:31 +0200 (EET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: CONEX? (was: Re: Q and L loss bits)
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com>
Date: Thu, 21 Nov 2019 08:42:31 +0200
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.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> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>
X-MailScanner-ID: E206D613195.A1C1B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XSlhx6ky7Qc1genwLhCtdgYXnGU>
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: Thu, 21 Nov 2019 06:42:44 -0000

Hi,

I'm wondering whether specifying a CONEX mapping for QUIC would satisfy the needs that quic-lossbits attempts to address? We could reuse an existing piece of IETF work.

See https://tools.ietf.org/html/rfc7713 for an overview and https://tools.ietf.org/html/rfc7786 for the TCP mapping.

Lars