Re: [quicwg/base-drafts] HTTP/3: Add RFC8446 reference for TLS 1.3. (#3483)

Martin Thomson <notifications@github.com> Mon, 24 February 2020 21:26 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 9CFB23A1378 for <quic-issues@ietfa.amsl.com>; Mon, 24 Feb 2020 13:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level:
X-Spam-Status: No, score=-3.1 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 Wys5dkmbW68z for <quic-issues@ietfa.amsl.com>; Mon, 24 Feb 2020 13:26:05 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E23D3A1376 for <quic-issues@ietf.org>; Mon, 24 Feb 2020 13:26:05 -0800 (PST)
Received: from github-lowworker-943b171.ac4-iad.github.net (github-lowworker-943b171.ac4-iad.github.net [10.52.22.59]) by smtp.github.com (Postfix) with ESMTP id 864F39604A2 for <quic-issues@ietf.org>; Mon, 24 Feb 2020 13:26:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582579564; bh=4+o2IVH/ISFgVnVDg94imOws7hdyF3eFpK2ILxrSC3w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NU9iABEc4Fz28hn0Ahj57QXo7k6AcQp/vT61iRh7a4LDVR91rS/MDgsxyVSk4FdEv nYco3T51uTJaVbO49YptfbufHGKXj7ekj3vqQft3xrfj9NrgvelKZKg4tevM3argfV Zb49+VJqIYEWUmBTD1NVFHU6rS3DQ21O9eL1evT4=
Date: Mon, 24 Feb 2020 13:26:04 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZH4WVZYHVWDU6RVPF4MFY6ZEVBNHHCD6UT7Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3483/review/363711599@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3483@github.com>
References: <quicwg/base-drafts/pull/3483@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3: Add RFC8446 reference for TLS 1.3. (#3483)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e543f6c76924_8e93fe18cacd96c13255c"; 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/Dz5cFM-3GqwOSHjI91IT5mGtJJE>
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: Mon, 24 Feb 2020 21:26:07 -0000

martinthomson approved this pull request.

I've suggested some symbolic references.

> @@ -112,9 +112,9 @@ The QUIC transport protocol incorporates stream multiplexing and per-stream flow
 control, similar to that provided by the HTTP/2 framing layer. By providing
 reliability at the stream level and congestion control across the entire
 connection, it has the capability to improve the performance of HTTP compared to
-a TCP mapping.  QUIC also incorporates TLS 1.3 at the transport layer, offering
-comparable security to running TLS over TCP, with the improved connection setup
-latency of TCP Fast Open {{?RFC7413}}.
+a TCP mapping.  QUIC also incorporates TLS 1.3 {{?RFC8446}} at the transport

```suggestion
a TCP mapping.  QUIC also incorporates TLS 1.3 {{?TLS13=RFC8446}} at the transport
```
(note line wrapping is again likely needed here)

> @@ -112,9 +112,9 @@ The QUIC transport protocol incorporates stream multiplexing and per-stream flow
 control, similar to that provided by the HTTP/2 framing layer. By providing
 reliability at the stream level and congestion control across the entire
 connection, it has the capability to improve the performance of HTTP compared to
-a TCP mapping.  QUIC also incorporates TLS 1.3 at the transport layer, offering
-comparable security to running TLS over TCP, with the improved connection setup
-latency of TCP Fast Open {{?RFC7413}}.
+a TCP mapping.  QUIC also incorporates TLS 1.3 {{?RFC8446}} at the transport
+layer, offering comparable security to running TLS over TCP, with the improved
+connection setup latency of TCP Fast Open {{?RFC7413}}.

```suggestion
connection setup latency of TCP Fast Open {{?TFO=RFC7413}}.
```

-- 
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/3483#pullrequestreview-363711599