Re: [quicwg/base-drafts] Specify behavior for post-handshake CRYPTO messages (#2524)

Marten Seemann <> Mon, 18 March 2019 22:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D75EA127962 for <>; Mon, 18 Mar 2019 15:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Status: No, score=-6.598 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 QpKvdW5sBRin for <>; Mon, 18 Mar 2019 15:37:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0394612AF84 for <>; Mon, 18 Mar 2019 15:37:05 -0700 (PDT)
Date: Mon, 18 Mar 2019 15:37:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1552948623; bh=rqyE+w66lAor75mmJQ3/fiBn2BOjN14I68w8fqzaBt4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QwrLV3dswd0sHly7FdewEW3LjnL9kug5ynJxl2eMcqE+//q6kDWKtiTOfWDWyoeJ2 0zYnJszKtwGcoZ0bTcq1xYRLh29uN0W82tu7S4SkBFfdDneiEifzmC46Aa4JQpHeRQ onAwTGFG8aoenRuJ0rAsSH9arD+mS7bPp0qF9a38=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2524/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Specify behavior for post-handshake CRYPTO messages (#2524)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c901d8fddbab_387c3f86846d45bc110259"; 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, 18 Mar 2019 22:37:08 -0000

I’d prefer to always close the connection instead of silently discarding the frames. The problem with discarding frames is that while it doesn’t really hurt with “normal” TLS 1.3, there might be TLS extensions which require the reliable delivery of post-Handshake messages.
Furthermore, acknowledging a packet means that a peer has processsed all the frames. Silently dropping frames seems like an awkward exception to that rule. 

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