[quicwg/base-drafts] Do you need to supply max_early_data in NST to enable 0-RTT (#942)
ekr <notifications@github.com> Fri, 17 November 2017 01:42 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 AA06A12726E for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 17:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level:
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 6nE9V5MI0wQs for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 17:42:40 -0800 (PST)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 51ADB124239 for <quic-issues@ietf.org>; Thu, 16 Nov 2017 17:42:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zq3BWJdds20J7glKf45m9+4CaXA=; b=R07uGfATrVZWn4b0 9Njg9Y6Ah/fNixlO6p0TZi8QID7HzkFTaURQeRPO+VN3lf8mp8QiWDzhTnskxXlc L01uV/GSb0nnGjHwkUXbBj1tTGTlEwgvWTN+Fq5lxMm/9Emt93la8O3geB2C2uxk 8EmbnBs5LHMYJi4rmE1lUngIH3g=
Received: by filter0255p1iad2.sendgrid.net with SMTP id filter0255p1iad2-14949-5A0E3E8F-1A 2017-11-17 01:42:39.295533392 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id nUfzTbsvSvK9mdHNOJwnQw for <quic-issues@ietf.org>; Fri, 17 Nov 2017 01:42:39.285 +0000 (UTC)
Date: Fri, 17 Nov 2017 01:42:39 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb2de45660b904e09b8f931f0ed67fa2397718d3392cf000000011626008f92a169ce105ff5a6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/942@github.com>
Subject: [quicwg/base-drafts] Do you need to supply max_early_data in NST to enable 0-RTT (#942)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a0e3e8f198e6_6e3d3f9c5145ef34120880"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1dc7KX2i9+xIEMHtZnC+5uXdPnWDilXI86c8 gunO1T+Jb8waMIibARF6J5lZbY6wgv3RS/m+Hi3ZnGjUBRbts9mJeyoIYc+TQYusey2lMRoMfx/LBq yJEAvvBYhGqvSgYpMPXt5hBXRU8VoCDJxpBvwi2xCFciLjh/3QbFjl3/KQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/m-FicoiMXVFeQ2-H22GXKpfstB0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Nov 2017 01:42:41 -0000
In TLS 1.3, servers have to opt-in to early data by sending "max_early_data". We need to clarify whether this is required in QUIC. I believe @martinthomson 's view is "no" but we need to decide one way or the other. -- 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/issues/942
- [quicwg/base-drafts] Do you need to supply max_ea… ekr
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson
- Re: [quicwg/base-drafts] Do you need to supply ma… ekr
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson
- Re: [quicwg/base-drafts] Do you need to supply ma… ekr
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson
- Re: [quicwg/base-drafts] Do you need to supply ma… Christian Huitema
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson
- Re: [quicwg/base-drafts] Do you need to supply ma… Martin Thomson