IETF Logo Mail Archive

Re: [quicwg/base-drafts] RFC Editor Copyedits (PR #4956)

Lucas Pardue <notifications@github.com> Tue, 15 February 2022 20:49 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 566DD3A040A for <quic-issues@ietfa.amsl.com>; Tue, 15 Feb 2022 12:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.262
X-Spam-Level:
X-Spam-Status: No, score=-7.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 sA3NIlgXlB9E for <quic-issues@ietfa.amsl.com>; Tue, 15 Feb 2022 12:49:08 -0800 (PST)
Received: from smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F8663A012A for <quic-issues@ietf.org>; Tue, 15 Feb 2022 12:49:08 -0800 (PST)
Received: from github-lowworker-c73936b.ash1-iad.github.net (github-lowworker-c73936b.ash1-iad.github.net [10.56.112.13]) by smtp.github.com (Postfix) with ESMTP id 37DDD840502 for <quic-issues@ietf.org>; Tue, 15 Feb 2022 12:49:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1644958147; bh=C0caS5/TJuzUvX3f13Mhc6VldZFZo7gQ9Pp20iL+8yM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F7vIPf7ga6Rb2XFOGa1jFXVXfD28LwPthRWzHBLghzzmcqPbM69EIzLtkQIbX0pvM esI/Z/NU+2sko8f85bhk5oGuU2tPm1Ku+PWDcuvtfp+Z/2U1y4n8oS8ZagJrndPRJm Y4hrb30wcfQMUmUHkjzkVxDMKa2VB55XM+BMJ+Yg=
Date: Tue, 15 Feb 2022 12:49:07 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7SAEABYMURJYZDCXOAC7ZMHEVBNHHEHZVETM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4956/review/883631900@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4956@github.com>
References: <quicwg/base-drafts/pull/4956@github.com>
Subject: Re: [quicwg/base-drafts] RFC Editor Copyedits (PR #4956)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_620c11c32a718_2cfac6fc4998f"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/pOSR9PL4PMymhU7UZ8E8QufAAN4>
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: Tue, 15 Feb 2022 20:49:12 -0000

@LPardue commented on this pull request.



> @@ -301,11 +302,11 @@ host identifier to an IP address, establishing a QUIC connection to that address
 on the indicated port (including validation of the server certificate as
 described above), and sending an HTTP/3 request message targeting the URI
 to the server over that secured connection.  Unless some other mechanism is used
-to select HTTP/3, the token "h3" is used in the Application-Layer Protocol
+to select HTTP/3, the token "h3" is used in the Application Layer Protocol

I disagree with this one, RFC 7301 only uses the hyphenated term of art "Application-Layer Protocol Negotiation Extension"

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

Message ID: <quicwg/base-drafts/pull/4956/review/883631900@github.com>

v2.8.7 | Report a Bug | By Email