[tsvwg] closing L4S issue #17 on FQ interaction
Wesley Eddy <wes@mti-systems.com> Tue, 04 February 2020 15:40 UTC
Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8B2120838 for <tsvwg@ietfa.amsl.com>; Tue, 4 Feb 2020 07:40:17 -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=mti-systems-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 oOwxYUnNPXUH for <tsvwg@ietfa.amsl.com>; Tue, 4 Feb 2020 07:40:16 -0800 (PST)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 DC65F12082A for <tsvwg@ietf.org>; Tue, 4 Feb 2020 07:40:15 -0800 (PST)
Received: by mail-qk1-x72f.google.com with SMTP id 21so18366003qky.4 for <tsvwg@ietf.org>; Tue, 04 Feb 2020 07:40:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=2/jMGt5S4smhqJnpjwDyCBn0R3G8+XH58JjUzVz4hKw=; b=WMK+R66zV0K2HflSc5LMTTIX10rbDI4DAqf1K0ENlRBQQq8idejKg3VBwcxk7KMT0O XDICiKgVZaxeCPaI8o+GJ2gUaXMngz6puUvQgkgrMSw5V1qN8FkuWbq3OSIdMTFlMRCp sxq1WvV/fdAlDAMGibmJdnzxGFqYgE3cEi4xnF7+XMXe+77TPbdHfVYURSRfZfQf9VND EHoYovKTb6+05FYt0lT88qQ66HGbkjiY849FVNAsCpiRSzigpz/QOid7cYd+KHg3BJV8 Bw1GunVaOEQMNfZHoQ55KQpQr8ULJBQTmWlUS/AyVVjajfCZQ6Oh7Wws+wVzZiIULU2L U7CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=2/jMGt5S4smhqJnpjwDyCBn0R3G8+XH58JjUzVz4hKw=; b=BS347uonu1XWikoV4gwntWRphgdglMXX4hl+rJXtbZGE04QN+Y7qUN8rCSMRt4BB85 pR6pTq+IlhtV10v7s+ad3x7N3aKM4YkQ4Ric/TQL7GgSwhdD5TDSpGXrhcDcxJMWqRQ8 xISrDoDbpfvvnmKGWB9U1ruOg2cgmvhcwuNHZjLPkZBsrG0o2jDCAHfmb1qom/73MmF6 jWpb0KPJA8+UnlF0ZQaFTgaKCM/ARB6q+1ypoYDXDsHEOolrjEWJ/TNt2ruRt37nSntr NUBbAtaczXmTGoonTq0TA8NK92Xsp8VqDFmjYKJRu3uewEicoA6eLUf/W/2N+0ZpEK+9 x2JA==
X-Gm-Message-State: APjAAAVjnTPL4HkbSTOL1biTyGOnhEchrFgkJB9qN8ALsTEmwmzxagJN BnrT81Mud/3xtq++LnHklPZqBofrADE=
X-Google-Smtp-Source: APXvYqwNdFQzhqWqKFFYFHGd1QQ1ax2fKW5ZmkSznDqZdNwlG0nhUm04QE22ojkjmhjF2Z2zIcBaYQ==
X-Received: by 2002:ae9:e40e:: with SMTP id q14mr28032588qkc.77.1580830814874; Tue, 04 Feb 2020 07:40:14 -0800 (PST)
Received: from [10.100.1.112] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id n4sm11806099qti.55.2020.02.04.07.40.14 for <tsvwg@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Feb 2020 07:40:14 -0800 (PST)
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <862c1335-1ca7-d82c-3586-8753a18533c0@mti-systems.com>
Date: Tue, 04 Feb 2020 10:40:10 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ps1thZ9eYmAhrzqL4UNjeCVkZZg>
Subject: [tsvwg] closing L4S issue #17 on FQ interaction
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 15:40:18 -0000
It looks like we have mostly converged on the L4S issue tracker entry for FQ interaction: https://trac.ietf.org/trac/tsvwg/ticket/17 Greg's last comment there sums it up well, I think. Based on the threads and meeting notes, I'm not sure if anything specific needs to be done to the L4S drafts, other than making sure that the TCP Prague discussion there reflects what the testing has revealed is important to be done. So, I think when the drafts are updated, we will be able to close this issue. Please correct if this is wrong.
- Re: [tsvwg] closing L4S issue #17 on FQ interacti… Greg White
- [tsvwg] closing L4S issue #17 on FQ interaction Wesley Eddy
- Re: [tsvwg] closing L4S issue #17 on FQ interacti… Jonathan Morton
- Re: [tsvwg] closing L4S issue #17 on FQ interacti… Wesley Eddy
- Re: [tsvwg] closing L4S issue #17 on FQ interacti… Jonathan Morton
- Re: [tsvwg] closing L4S issue #17 on FQ interacti… Luca Muscariello