Re: [quicwg/base-drafts] Discarding connection state at server on unvalidated client (#2656)

Marten Seemann <> Mon, 29 April 2019 03:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6C69112017D for <>; Sun, 28 Apr 2019 20:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id O-kZYfNwzay3 for <>; Sun, 28 Apr 2019 20:06:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 302A31200E3 for <>; Sun, 28 Apr 2019 20:06:47 -0700 (PDT)
Date: Sun, 28 Apr 2019 20:06:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556507206; bh=DRD4EXhh0Pesjj5FFhtOHYppyeBD2FlYL0IGcz5hAuw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u44vuCDNcYrOrra6MTiI6F4iqzmxxC7CA01QM4JF9Ys5nLQcoauYmE6SuiO3uRwh9 vTInScUdAT8KPfryulOjrmKEagKS9jXpO2w+WwZrvDrctRpVM3P8cZg5gSwMw05HRw qUwN1+A9uUcqZ7qW+hA/yoRBdfuDBabcEX0/JY6I=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2656/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Discarding connection state at server on unvalidated client (#2656)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc66a467186_4cb13f8c250cd9601848ba"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Apr 2019 03:06:49 -0000

I agree with @ianswett that this is a transport issue, and doesn't belong in the recovery document. There we are only talking about the timers needed for loss recovery, and I would find it confusing to talk about closing connections there.
I'm not sure if we need to have any text about a handshake timeout. An idle timeout should be sufficient to garbage-collect connections that aren't active any more. Having a (shorter) handshake timeout is an optimization that implementations might or might not want to have, depending on the threat model.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: