Re: [quicwg/base-drafts] Second set of editorial nits (#3770)

Gorry Fairhurst <notifications@github.com> Wed, 17 June 2020 09:59 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F913A08BD for <quic-issues@ietfa.amsl.com>; Wed, 17 Jun 2020 02:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 2rGmK2wFkco0 for <quic-issues@ietfa.amsl.com>; Wed, 17 Jun 2020 02:59:19 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7D4A3A08BA for <quic-issues@ietf.org>; Wed, 17 Jun 2020 02:59:19 -0700 (PDT)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id D50426A011C for <quic-issues@ietf.org>; Wed, 17 Jun 2020 02:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592387958; bh=qt65LI0rKcehVHCneSPf0GcrqUy9PaxBadYAr/+8974=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wyCx00Xg60Meh2FTkwWW7nU0g0L2UulJmbWnn9u3rC/VqVPWz+lFBrz3iupejJviO lAdNgAKz7Mzuho8lM9hNeTHrOJM+7gq+pbsm+AAywV0QaOCR/FPUYUvsPo7X8LVt2Q 5J7vuPWABKW6PY7plwG4S3JhlCosiMl938bfGbwM=
Date: Wed, 17 Jun 2020 02:59:18 -0700
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK62A23SDRG2GP2Y2JV46XFHNEVBNHHCMKRPF4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3770/c645277963@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3770@github.com>
References: <quicwg/base-drafts/pull/3770@github.com>
Subject: Re: [quicwg/base-drafts] Second set of editorial nits (#3770)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ee9e976c671e_28dd3fa161ccd96c142034"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7aOLWwwKGhGmJlVQ6_4NpAYA6RU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 09:59:21 -0000

Fine and thanks for looking to these.

I do think something more needs to be said about the need to avoid collateral impact on the forward traffic of this and other traffic sharing a path. To me this really important in an IETF Transport specification, especially one that might displace TCP.
/It can also improve connection throughput on severely asymmetric links; see Section 3 of {{?RFC3449}}./ 

To me, a note to make sure this isn't ignored would seem enough, but I'd be happy to take this up as a separate WGLC comment if that seems better.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3770#issuecomment-645277963