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

Martin Thomson <> Tue, 19 March 2019 23:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 81EF1127133 for <>; Tue, 19 Mar 2019 16:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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, 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 xAo5U_lkP-rr for <>; Tue, 19 Mar 2019 16:18:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BB53F12008F for <>; Tue, 19 Mar 2019 16:18:03 -0700 (PDT)
Date: Tue, 19 Mar 2019 16:18:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1553037482; bh=8RMpA+o7kdcB69G0IXA+37+8hX+6gE8hHwynxXoM/Ls=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k0S75lz/VQSwlt/v0c+rVcf5RQmLZOY6POm2xDAoZ3GewcF0ZfHTw0afairNbPKQn ybRVv4ceui9TTkhoHjqa4I/qyMnzokgrnGYdeHy81vpEKONIqFicAm9qzU95OhC4g0 mPbrdv+CPBlCdfFXJ3dQfpB6TCV2CrjIM3tVulro=
From: Martin Thomson <>
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_5c9178aabdcc6_54d73faf74cd45c0706240"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Tue, 19 Mar 2019 23:18:05 -0000

As @nharper says, the TLS stack will be expecting data to be delivered in order.  If it can't keep up, or data arrives waaay out of order, that is when the transport needs to decide what to do.  (That is why this text belongs in the transport doc and not the TLS one, in case people were wondering.)

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