IETF Logo Mail Archive

Re: [quicwg/base-drafts] Don't reset an active connection (#3894)

Martin Thomson <notifications@github.com> Mon, 13 July 2020 04:09 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 365543A0CA7 for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 21:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.081
X-Spam-Level:
X-Spam-Status: No, score=0.081 tagged_above=-999 required=5 tests=[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_24=1.282, 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 c1y3xYqbnzGM for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 21:09:35 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D5FC3A0C9B for <quic-issues@ietf.org>; Sun, 12 Jul 2020 21:09:35 -0700 (PDT)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [10.52.16.66]) by smtp.github.com (Postfix) with ESMTP id 390786E06B7 for <quic-issues@ietf.org>; Sun, 12 Jul 2020 21:09:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594613374; bh=4o3CqSGAStsq+iMppDx6Vy6LWfpjs7Pg7JTetiFwmV8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Otf/84RNF3wSRvHfOUNxlPkBvz+9+4APwioTHFk8uAIsf/Qj6Lo5PrHW5LZwBBKSO LQqYpr4sRVfPniQRSgvXXod3CXucMyqdNsRthBoVGnRAiu4rmtPs8PPpprGfW9wrbS Eb+zyTxO1NneTtvVxpXMyV3YYQX8izUwzEDMzrYw=
Date: Sun, 12 Jul 2020 21:09:34 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK67MGLNOC7DMUH5HCF5C67X5EVBNHHCOEYR5Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3894/review/446969544@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3894@github.com>
References: <quicwg/base-drafts/pull/3894@github.com>
Subject: Re: [quicwg/base-drafts] Don't reset an active connection (#3894)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0bde7e2915c_4f6c3fd31eacd95c8230e4"; 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/_ZF1Np1sLoM-xcjpFqBVoLcPIIM>
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: Mon, 13 Jul 2020 04:09:36 -0000

@martinthomson commented on this pull request.



> @@ -6369,14 +6369,17 @@ endpoints that share a static key for stateless reset (see {{reset-token}}) MUST
 be arranged so that packets with a given connection ID always arrive at an
 instance that has connection state, unless that connection is no longer active.
 
+More generally, servers MUST NOT generate a stateless reset if a connection with

Yes, I think that "valid" is implied.  In the case of one server generating a stateless reset based on a connection ID that came from another server, that wouldn't affect that other connection. It would only affect the connection that the server generating the stateless reset might have created, if there was such a connection.

-- 
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/3894#discussion_r453424371

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