Re: [quicwg/base-drafts] Error for frames in the wrong packet (#3859)

Marten Seemann <> Wed, 08 July 2020 05:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB2733A082A for <>; Tue, 7 Jul 2020 22:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ybLocn8m8JEk for <>; Tue, 7 Jul 2020 22:13:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A5A953A0828 for <>; Tue, 7 Jul 2020 22:13:21 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E13A51212A6 for <>; Tue, 7 Jul 2020 22:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1594185200; bh=ebvZzy5gCUJLCFSnKOBwvu3znDkWlyD+ZEqsTgelkqk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LcnDJRtLMRJjHjkSKd1ISjbyUYYcWMxSiD1r65K7mqBqVo5R3KEf2g7mTujt2FZ1i EKEFusus3FlO+VDnDx8tasfQ+cB/vOrVtoshJpHgLMp3PZrka4mkVrm6jRluW4pki6 c91ON5gK2hLeq2sHrSbfpGkJQMVz3n0bYVxML8sM=
Date: Tue, 07 Jul 2020 22:13:20 -0700
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3859/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Error for frames in the wrong packet (#3859)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0555f09b583_5b953f91ad4cd96096124"; 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: Wed, 08 Jul 2020 05:13:23 -0000

@marten-seemann commented on this pull request.

> @@ -3354,7 +3354,9 @@ ih:
 Section 4 of {{QUIC-TLS}} provides more detail about these restrictions.  Note
-that all frames can appear in 1-RTT packets.
+that all frames can appear in 1-RTT packets.  An endpoint MUST treat receipt of
+a frame in a packet type that is not permitted as a connection error of type

Depends on what your definition of "context" is. If it is "the bytes that this frame is composed of", then no. If you include the encryption level you received those bytes with, then "yes". You might want to do that, because the encryption level is not connection-level state.

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