Re: [quicwg/base-drafts] Server should not accept 1-RTT traffic before handshake completion (#3159)

Kazuho Oku <> Mon, 28 October 2019 12:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DAA001200D7 for <>; Mon, 28 Oct 2019 05:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 ePPcLM8BmJTO for <>; Mon, 28 Oct 2019 05:25:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1BDAD12001E for <>; Mon, 28 Oct 2019 05:25:40 -0700 (PDT)
Date: Mon, 28 Oct 2019 05:25:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572265539; bh=Nd3ouzJ+tK7LkqgvdL1azY7FYvKn1xZH2LNM35Iq0q0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EkRJ318imd/OvUgubrlNM/edRvg9rCfX9ti9C7Zk2z+ou0ZJ+4fhUTuoSj1UwDRCy zTuWT5SHj3A9+6euUBRDJlZGCNVuZkrIzoAA2fn7Dp4fh7wbEbjJujUuFY5m/vqpEi p2CddfXNdcymcDTt8mbs01MapvXkGCcmuBJqQZac=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3159/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Server should not accept 1-RTT traffic before handshake completion (#3159)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db6de4350219_5fd3faae88cd96c6156c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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, 28 Oct 2019 12:25:42 -0000

> In QUIC, the server may receive 1-RTT packets before the client finished.

While this is true, I wonder if we have the issues you point out, because we prohibit the use of such packets until the server receives Client Finished.

[Section 5.7 of the TLS draft]( states that _a server MUST NOT process data from incoming 1-RTT protected packets before the TLS handshake is complete,_ where "handshake complete" is defined as _when the TLS stack has both sent a Finished message and verified the peer’s Finished message_ ([section 4.1.1](

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