Re: [quicwg/base-drafts] Remove timing guidance (#3474)

Mike Bishop <notifications@github.com> Thu, 26 March 2020 15:39 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 50D823A07C6 for <quic-issues@ietfa.amsl.com>; Thu, 26 Mar 2020 08:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 uv3AsO4KHFA3 for <quic-issues@ietfa.amsl.com>; Thu, 26 Mar 2020 08:39:28 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86C553A07A8 for <quic-issues@ietf.org>; Thu, 26 Mar 2020 08:39:27 -0700 (PDT)
Date: Thu, 26 Mar 2020 08:39:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1585237166; bh=I8XSSMD5BbiDMOeh5DXQ+l2XZG+Fhxp8LZgIAD6zmt8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yHJ3PYwwudzTUklbU0NsDU+3uBiuYT4reamIYJjdvSm1Zj8ehltrg2FHqWXMbv0os ShJIekbnDuS9Rtao6+29XqNo+PbcNCG3UMocCCkxFV4KGKnwO3Ov4QFSIaFQKUDKAD KvKy7+M8m4SGNLUNWToCL4f8ImXME8CKxnYHu49c=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2EKCTN4H3X2TDAHNF4RCW25EVBNHHCD3AHXI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3474/review/382136130@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3474@github.com>
References: <quicwg/base-drafts/pull/3474@github.com>
Subject: Re: [quicwg/base-drafts] Remove timing guidance (#3474)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e7cccae769a8_3ad53fdfe9acd95c159897"; 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/hw2EBM894DyQbUdiaehufTc-hek>
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, 26 Mar 2020 15:39:30 -0000

@MikeBishop commented on this pull request.



> +An endpoint might need to stop accepting previously issued connection IDs in
+certain circumstances.  Such an endpoint can cause its peer to retire connection
+IDs by sending a NEW_CONNECTION_ID frame with an increased Retire Prior To
+field.  The endpoint SHOULD continue to accept the previously issued connection
+IDs until they are retired by the peer.  If the endpoint can no longer process
+the indicated connection IDs, it MAY close the connection.
+
+Upon receipt of an increased Retire Prior To field, the peer MUST stop using the
+corresponding connection IDs and retire them with RETIRE_CONNECTION_ID frames
+before adding the newly provided connection ID to the set of active connection
+IDs. This ordering allows an endpoint that has already supplied its peer with as
+many connection IDs as allowed by the active_connection_id_limit transport
+parameter to replace those connection IDs with new ones as necessary.  Failure
+to retire the connection IDs promptly when requested can result in connection
+failures, as the issuing endpoint might be unable to continue using the
+connection IDs with the active connection.

Both, actually.  If you use them and the remote routing infrastructure no longer recognizes them, you'll get a (potentially valid) Stateless Reset.  However, if you stop using them without retiring them, the peer MAY close the connection on you.

-- 
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/3474#discussion_r398672507