Re: [quicwg/base-drafts] What does a server do with Handshake packets not belonging any connection? (#2333)

Marten Seemann <> Mon, 14 January 2019 06:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 30C62130F5C for <>; Sun, 13 Jan 2019 22:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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 a9aI07WYNkFi for <>; Sun, 13 Jan 2019 22:43:54 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 16AE2130F58 for <>; Sun, 13 Jan 2019 22:43:54 -0800 (PST)
Date: Sun, 13 Jan 2019 22:43:53 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547448233; bh=zJc/gWdeuNCHvWWG3h6uP/UtKXl5KDHXeNTkbZk3l/o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Qu8gLqTeo7M/9IE58tPcnCR7XlC8Md4CWc5R0+E+3SbaeBZTpwtpy++Hhce4LT5Om YSWAFmksRWvC4dTboXKQR9dZ5D1HsLhmmBIjF0yE5qoiGHHUdmoJWEEh3EDnQ+8WDv fhxRRSC1FKqUR1nAwmQdpIjfTiYok60yp7tskqWI=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2333/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] What does a server do with Handshake packets not belonging any connection? (#2333)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3c2fa9b798_8193f9050ed45c083488b"; 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, 14 Jan 2019 06:43:56 -0000

I just saw that we already have text about that:
> An endpoint MAY send a stateless reset in response to a packet with a long header. This would not be effective if the stateless reset token was not yet available to a peer. In this QUIC version, packets with a long header are only used during connection establishment. Because the stateless reset token is not available until connection establishment is complete or near completion, ignoring an unknown packet with a long header might be more effective.

Sorry for the noise.

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