Re: [quicwg/base-drafts] Editorial: More concise intro text (recovery) (#3380)

Martin Thomson <notifications@github.com> Wed, 22 January 2020 22:46 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 6F771120091 for <quic-issues@ietfa.amsl.com>; Wed, 22 Jan 2020 14:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 LAprdgnAeyyv for <quic-issues@ietfa.amsl.com>; Wed, 22 Jan 2020 14:46:24 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D20912004F for <quic-issues@ietf.org>; Wed, 22 Jan 2020 14:46:24 -0800 (PST)
Date: Wed, 22 Jan 2020 14:46:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579733183; bh=ssmDGqUSqKdsn4ynz5jXA+T44ERWZweVuDL6W4jSCGU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wFDDRM1PFCbmEqY5Ee9bHFfrKv3Ll9CS+Ufbl+IvnvxxqZfHu+HgVhiJNgCjOf69p DCl5B2jTH2uNxcLFsew+mg0J62lF1sqf0d1MduLlXoY7oTVDyJYQHRHfnwzaZ3ldNQ Pg3BO1Yq0qOTN4MyFoA7HOCgmnoHexsoO/HbjOnU=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7CF3BYOSGK4CD6OL54GYBT7EVBNHHCB75K74@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3380/review/346956484@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3380@github.com>
References: <quicwg/base-drafts/pull/3380@github.com>
Subject: Re: [quicwg/base-drafts] Editorial: More concise intro text (recovery) (#3380)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e28d0bf4d15f_693e3fac486cd96c133662"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/y3e4G0OhYQedgkVp8avtL8RML7Y>
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, 22 Jan 2020 22:46:27 -0000

martinthomson commented on this pull request.

I too found the sell a little too strong.  This is better, but I also find the list of un-referenced claims of where this is inspired to still be a little hard to stomach.

I've made something of a suggestion here about what might be said that doesn't rely on reciting a list of unreferenced sources.

> -attractive as a modern general-purpose transport.  The QUIC protocol is
-described in {{QUIC-TRANSPORT}}.
-
-QUIC implements the spirit of existing TCP congestion control and loss recovery
-mechanisms, described in RFCs, various Internet-drafts, and also those prevalent
-in the Linux TCP implementation.  This document describes QUIC congestion
-control and loss recovery, and where applicable, attributes the TCP equivalent
-in RFCs, Internet-drafts, academic papers, and/or TCP implementations.
-
+QUIC is a new multiplexed and secure transport protocol atop UDP, specified in
+{{QUIC-TRANSPORT}}. This document describes congestion control and loss
+recovery for QUIC. Mechanisms described in this documnet follow the spirit
+of existing TCP congestion control and loss recovery mechanisms, described in
+RFCs, various Internet-drafts, or academic papers, and also those prevalent in
+the Linux TCP implementation. Where applicable, this document attributes the TCP
+equivalent.

This last sentence seems incomplete.  I think that you are saying that the mechanisms here are informed by TCP.  Any differences are necessary as a result of differences in QUIC relative to TCP; or demonstrably advantageous as a result of QUIC lacking some of the limitations of TCP.

-- 
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/3380#pullrequestreview-346956484