Re: [quicwg/base-drafts] Transport editorial suggestions (#2731)

ianswett <notifications@github.com> Wed, 19 June 2019 00:44 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 5D5AA120391 for <quic-issues@ietfa.amsl.com>; Tue, 18 Jun 2019 17:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level:
X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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.415, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 uHXqQc4Purpx for <quic-issues@ietfa.amsl.com>; Tue, 18 Jun 2019 17:44:40 -0700 (PDT)
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 6EC6B1201F3 for <quic-issues@ietf.org>; Tue, 18 Jun 2019 17:44:40 -0700 (PDT)
Date: Tue, 18 Jun 2019 17:44:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560905079; bh=4o14VTXu2R7R4L+sVChbrLSwAgoayenyB7U3xMdLVgM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YradUXWlOHFI8WeKplxCjbB4DsmMfEepqtLM4c4Aad9IIIcjVSZ8mRmmQ4uuln81f MNhC4E4CTpYzWY7kqtYPqPQbr78Fo3NgvmMZPlBtxMhrZz8AwY1YTax9esQDos+/jw g9Oyht8cyUrQiJ61ecyaeDUIttX7fCnqaCr/l3/U=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZKFSHGQOPJ2ESDIAN3C237PEVBNHHBVGVFRE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2731/review/251427194@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2731@github.com>
References: <quicwg/base-drafts/pull/2731@github.com>
Subject: Re: [quicwg/base-drafts] Transport editorial suggestions (#2731)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0985778ab62_63633fe9580cd95c235417"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/yTq0kX0qaK7eH9o7asOx0PZC-YQ>
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: Wed, 19 Jun 2019 00:44:43 -0000

ianswett commented on this pull request.

Thanks, I'm going to remove that paragraph.

> @@ -1336,11 +1335,7 @@ and sets the SCIL field to indicate the length.
 The first flight of 0-RTT packets use the same Destination and Source Connection
 ID values as the client's first Initial.
 
-The Destination Connection ID field in the server's Initial packet contains a
-connection ID that is chosen by the recipient of the packet (i.e., the client);
-the Source Connection ID includes the connection ID that the sender of the
-packet wishes to use (see {{connection-id}}). The server MUST use consistent
-Source Connection IDs during the handshake.
+The server MUST use consistent Source Connection IDs during the handshake.

Weirdly, this text was already there, see lines 1342/1343.

But I agree, this is clearly incorrect or depends upon the definition of consistent, which I don't believe is worth defining.  I'm going to remove this paragraph.

-- 
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/2731#pullrequestreview-251427194