IETF Logo Mail Archive

Re: [quicwg/base-drafts] #3348 Clarify that you can use any issued CID at any time, even during the handshake (#3438)

Martin Thomson <notifications@github.com> Sun, 09 February 2020 21:56 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 4199812006D for <quic-issues@ietfa.amsl.com>; Sun, 9 Feb 2020 13:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 vwpibvky5_WU for <quic-issues@ietfa.amsl.com>; Sun, 9 Feb 2020 13:56:45 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79492120026 for <quic-issues@ietf.org>; Sun, 9 Feb 2020 13:56:45 -0800 (PST)
Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id 49F7F1C0DF6 for <quic-issues@ietf.org>; Sun, 9 Feb 2020 13:56:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1581285404; bh=jIzvN1ae9ffkGSpB7dZLju1k/io0sbYbMptwrQJJwMk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y4s+dBdeDmQm7eJ9iMvp0wuhyzcuVoWlv3TDJNqRFjIUjnTFQhkEVA5gWPVsIWirs bfkaSpVouOIfDbLQeEdZFS9DfS+hJ7y+hbxArwRm5ZLcFp18cx5NzfPgEKw+8lmzV+ sYFYFRZUfV6WrfDyiQzwY0xVC/Ia325qTg6Kg9vA=
Date: Sun, 09 Feb 2020 13:56:44 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2TEHW76NB54KZFPPV4JWZJZEVBNHHCC34JKQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3438/review/355636697@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3438@github.com>
References: <quicwg/base-drafts/pull/3438@github.com>
Subject: Re: [quicwg/base-drafts] #3348 Clarify that you can use any issued CID at any time, even during the handshake (#3438)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e40801c3990a_1c563fca0f8cd96c9746"; 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/lakWHjyTBjYDozKrPad0DyxaXrc>
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: Sun, 09 Feb 2020 21:56:47 -0000

martinthomson commented on this pull request.



> @@ -1002,7 +1002,9 @@ When an endpoint issues a connection ID, it MUST accept packets that carry this
 connection ID for the duration of the connection or until its peer invalidates
 the connection ID via a RETIRE_CONNECTION_ID frame
 ({{frame-retire-connection-id}}).  Connection IDs that are issued and not
-retired are considered active; any active connection ID can be used.
+retired are considered active; any active connection ID is valid for use at any
+time, including during the handshake.  This includes the connection ID issued by

Both those Initial cases are interesting, but probably not worth extra text :)

The "any packet type" comment is worth the text.

-- 
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/3438#discussion_r376819248

v2.23.0 | Report a Bug | By Email