Re: [quicwg/base-drafts] Use of "in order" might be misunderstood as an ordering requirement (2) (#4039)

Mike Bishop <notifications@github.com> Thu, 20 August 2020 18:11 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 90F103A10F3 for <quic-issues@ietfa.amsl.com>; Thu, 20 Aug 2020 11:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 GrZ9j1CZfBq2 for <quic-issues@ietfa.amsl.com>; Thu, 20 Aug 2020 11:11:08 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B13D3A10ED for <quic-issues@ietf.org>; Thu, 20 Aug 2020 11:11:08 -0700 (PDT)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id B72D0E01F5 for <quic-issues@ietf.org>; Thu, 20 Aug 2020 11:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1597947067; bh=yIieXE9dgHqNnFvXoZj6Co3mxwhsUsQRvtYxydeRtmA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XCrfGDtUMyJWUeMKKeGYl8LA8H8owQ0nE3FvSzeqrtvOu/ardTuuX3y9+21quEL56 nj9zRrffgvx3lVDBYpcK/De3NuqNNkdeGWo8YYBUQdUVAKbKwO6qq/j+SBJNoGG7G0 gQg/wK4uz7lV+LT/9UoKVEf9Qv7NGfAglCKb9tw8=
Date: Thu, 20 Aug 2020 11:11:07 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK323HGZ6JXR4R2NKCN5JKO3XEVBNHHCRLVK7Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4039/677818693@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4039@github.com>
References: <quicwg/base-drafts/issues/4039@github.com>
Subject: Re: [quicwg/base-drafts] Use of "in order" might be misunderstood as an ordering requirement (2) (#4039)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f3ebcbba65e8_575619641154fd"; 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/zHCXpi7yd77kUiksnkXIlRIiEzk>
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: Thu, 20 Aug 2020 18:11:10 -0000

"in order to" seems like a well-known construction, so I'm not concerned about its existence.  Your rewording loses the implication of "SHOULD... because you'll need to...."

Though I see your point that this sentence could be parsed as "reading in order" being the thing servers SHOULD be able to do.  Perhaps "In order to properly form X, servers SHOULD Y"?

-- 
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/issues/4039#issuecomment-677818693