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

mirjak <> Thu, 23 January 2020 09:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4556412022E for <>; Thu, 23 Jan 2020 01:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_IMAGE_ONLY_32=0.001, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5vK4dF6EudD7 for <>; Thu, 23 Jan 2020 01:27:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 09DF312001E for <>; Thu, 23 Jan 2020 01:27:26 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1C30A2C0AF1 for <>; Thu, 23 Jan 2020 01:27:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579771645; bh=DzpTDwXA6H+ydMjXwLDWJr0WHqQnptLo6Uve1DvOEcQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lvr7U2Ste5FQTskn4nvX7DKJiPrKkahgm92v+iMMw1LPHO/kYBdphVvZjEy8IdoW+ BKjOUydBzkFOJ7FcvXaTCQHUz9ckonF1eydZNuJFoCGeaWtMfytrOa2dwKFo1TwOkp phWNpnVzfN6PsdEzJJO4XCLo+CqErirtMkvwMbE4=
Date: Thu, 23 Jan 2020 01:27:25 -0800
From: mirjak <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3380/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Editorial: More concise intro text (recovery) (#3380)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e2966fdbe19_1b883ff919acd96867491"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jan 2020 09:27:27 -0000

mirjak commented on this pull request.

> -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

I just took that from the old intro. Removed now.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: