IETF Logo Mail Archive

Re: [quicwg/base-drafts] Massive batch of probably-editorial nits (#3805)

Mike Bishop <notifications@github.com> Sat, 11 July 2020 00:23 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 0BD533A094B for <quic-issues@ietfa.amsl.com>; Fri, 10 Jul 2020 17:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.544
X-Spam-Level:
X-Spam-Status: No, score=-1.544 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, T_SPF_TEMPERROR=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 nHI-WPW2QZYx for <quic-issues@ietfa.amsl.com>; Fri, 10 Jul 2020 17:23:10 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E6B13A0949 for <quic-issues@ietf.org>; Fri, 10 Jul 2020 17:23:10 -0700 (PDT)
Received: from github-lowworker-39b4a70.va3-iad.github.net (github-lowworker-39b4a70.va3-iad.github.net [10.48.16.66]) by smtp.github.com (Postfix) with ESMTP id 2C871661197 for <quic-issues@ietf.org>; Fri, 10 Jul 2020 17:23:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594426989; bh=LOTxEaHfMNkSZkCu8gY8wTpf2NoLlTRBZXcPTX+uzDs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OzpyIeS3PhL6TyVXMCcVmqTqTJ2bXb2XHtCuX6rkWxuqzBy77eozHJcYnveTIDAzR 0PI6yFEae6sBz+gvF5hOxXsHz9+bVYP8/z8LTFzIsgC6XmSTNWzY7XGtRSqUtRDLiO xRIuWAGdQwCukTBB2Jp9h2lAa6kCxc9mC2EH1mw8=
Date: Fri, 10 Jul 2020 17:23:09 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZFEQRY4V7AMKT3CCV5CTTW3EVBNHHCNKDJHI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3805/review/446758837@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3805@github.com>
References: <quicwg/base-drafts/pull/3805@github.com>
Subject: Re: [quicwg/base-drafts] Massive batch of probably-editorial nits (#3805)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f09066d1c4c2_7cd53ff6a3ecd964186735"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/k1YXFhYINp-nKVQzwqXqQRe7Rl0>
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: Sat, 11 Jul 2020 00:23:15 -0000

@MikeBishop commented on this pull request.



>  
 Client:
 
 : The endpoint initiating a QUIC connection.
 
 Server:
 
-: The endpoint accepting incoming QUIC connections.
+: The endpoint accepting an incoming QUIC connection.

Can you expand on why?  I'm adjusting it because nothing in the server role requires it to be accepting multiple connections.  We speak about clients initiating "a QUIC connection," and for symmetry should talk about a server accepting an individual QUIC connection.  Dealing with multiple simultaneous connections is something clients and servers both might do, but it's not fundamental to the definition of either client or server.

-- 
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/3805#discussion_r453130041

v2.28.0 | Report a Bug | By Email | System Status