IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify OOO CRYPTO data handling (#1787)

Marten Seemann <notifications@github.com> Sat, 22 September 2018 02:42 UTC

Return-Path: <noreply@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 632D2130EAB for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 19:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 04LJBI3HXU6p for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 19:42:47 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BD7D130DD6 for <quic-issues@ietf.org>; Fri, 21 Sep 2018 19:42:47 -0700 (PDT)
Date: Fri, 21 Sep 2018 19:42:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537584166; bh=30TPynM8VJpPu6iy3d9Q1GS92MAwmf6djjzGoix71LA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aznbOYSK1dYkHl/LS+8EYF3HfslwCHolIP6qV8gpt2eayE/G5SG4vG+6Om12TwZ98 oDCWKgT91mBPeiPcZEnGYkPSAWO6l2g2mTRFEmCrcyUUSjzlWRXGNVam9Y0XkpVClY mhjEGQ6uo1Hjs/Wcic6Rxn36AyD5o/k3U8SSZtKQ=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc2d3f41021476a4776289109445775851ac17f5292cf0000000117bd6e2692a169ce159f38fc@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1787/c423711148@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1787@github.com>
References: <quicwg/base-drafts/pull/1787@github.com>
Subject: Re: [quicwg/base-drafts] Clarify OOO CRYPTO data handling (#1787)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba5ac2645a1e_69a23ffaf1ad45b8324850"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/MDz91thRPHwscltK6sw1FfIKJ_4>
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: Sat, 22 Sep 2018 02:42:50 -0000

That's clearer now, however I think this is already described in the TLS document in the section "Sending and Receiving Handshake Messages", isn't it?

-- 
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/1787#issuecomment-423711148

v2.29.0 | Report a Bug | By Email | System Status