IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Mon, 13 July 2020 04:00 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 094213A0C9E for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 21:00:37 -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 hLwK9E-QtrY7 for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 21:00:36 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB963A0C9C for <quic-issues@ietf.org>; Sun, 12 Jul 2020 21:00:35 -0700 (PDT)
Received: from github-lowworker-9d2806a.ash1-iad.github.net (github-lowworker-9d2806a.ash1-iad.github.net [10.56.102.50]) by smtp.github.com (Postfix) with ESMTP id 95EAA261594 for <quic-issues@ietf.org>; Sun, 12 Jul 2020 21:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594612835; bh=8tXFFK2allO5iFSOjv82d2qb/Q40HIjXePaIQK2JV1Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HwrMtJehSgQCY831PK5w4yoF3I9HIZSS6ZEdY6m33n4zbmLjoMzq7kVvyexL09M6R miHyR/2XevoXOqCQN5UOPJ9P+A8v6hTRJQCa/3USClD2a1ATsST0B0Q7FlWWFMalOV Qw2x1VVq5UESPfnbObPMP6uB1MBUIGeUKkXjLLKk=
Date: Sun, 12 Jul 2020 21:00:35 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZPMM4TQGKOQQR3AY55C66WHEVBNHHCOEYR5Q@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/446967475@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_5f0bdc6350858_4a183fa3a0acd96486688f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/1DtbLdm1SlUE0kysQtD7TEEvneg>
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:00:37 -0000

@igorlord 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

So we choose to omit saying "_valid_ stateless reset", assuming this is implied?  I.e. a server may generate a stateless reset for a connection handled by a different server, but it is ok if they do not share stateless reset secret, since the resulting stateless reset will be invalid.

-- 
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#pullrequestreview-446967475

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