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

Nick Harper <notifications@github.com> Tue, 19 March 2019 17:46 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E317813161C for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 10:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZaNynKS1xrC for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 10:46:04 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DD5313160A for <quic-issues@ietf.org>; Tue, 19 Mar 2019 10:46:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=DBKOfN+kqJfiRehNSjvJHX4Uy/I=; b=O167aR8pxGSatMkn ITWzyyygE5PlgtiNe1zjVPe0uYWy+Luyho6EI5Y/cElqy94lMoUGNm0cigPMkwUy pHN84J16ZTekyL3x0GsUTRJr/iHgXlYSlaLpY6XOk4iuRaXFBLiP1vmX+4g5DUT+ dKhQ8vX2TCCFBKGQIF4Yve3lWB4=
Received: by filter0239p1iad2.sendgrid.net with SMTP id filter0239p1iad2-14193-5C912ADA-22 2019-03-19 17:46:02.721996697 +0000 UTC m=+345786.752087229
Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0015p1iad1.sendgrid.net (SG) with ESMTP id hY54rxq-RzmFjaY_Qhi49w for <quic-issues@ietf.org>; Tue, 19 Mar 2019 17:46:02.690 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id A6C79A80B0D for <quic-issues@ietf.org>; Tue, 19 Mar 2019 10:46:02 -0700 (PDT)
Date: Tue, 19 Mar 2019 17:46:02 +0000 (UTC)
From: Nick Harper <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2d137370c21da6a574c03b5ef3c357be07eeffa792cf0000000118a8ecda92a169ce192348df@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2524/c474491576@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2524@github.com>
References: <quicwg/base-drafts/pull/2524@github.com>
Subject: Re: [quicwg/base-drafts] Specify behavior for post-handshake CRYPTO messages (#2524)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c912adaa4ddb_404a3fc3314d45c042435d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nharper
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak03vFvrSm3MxZyO90uW1Ep4w53Iw4A/ia0BrS f3tsoRLyWxNo7pIlRThZSbT+wbK2oL6AKISnbO6TTvx0s/exmaRvGBLuLNgH/EfH+RAf73vfuBH1KK VDyUpRCzFoSt1uVYo285aPQlTdgs4zxP61dl9HwzQvb3Z5pqMxivdzLH6J1RFBN0XmsKEQT/KfqInN M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bWo867CW1Kmfez9fgqbkieMKfsM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2019 17:46:15 -0000

> Is this buffering covering the internal TLS state engine, or is that separate?

This is buffering in the QUIC layer (specifically buffering out of order data that can't be delivered to the TLS stack) - the TLS stack probably has its own internal buffers, but that's opaque to QUIC.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2524#issuecomment-474491576