Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507)
Martin Thomson <notifications@github.com> Mon, 02 July 2018 04:19 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 C0D0A130F4A for <quic-issues@ietfa.amsl.com>; Sun, 1 Jul 2018 21:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, URIBL_BLOCKED=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 ur-jFwN35bu9 for <quic-issues@ietfa.amsl.com>; Sun, 1 Jul 2018 21:19:35 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E15A2130F50 for <quic-issues@ietf.org>; Sun, 1 Jul 2018 21:19:34 -0700 (PDT)
Date: Sun, 01 Jul 2018 21:19:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530505174; bh=fXThVnqy6Sdd0bZA4FDTYWbVwaPERY8JE0lCS2R+qJY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pYhtC7a1E3HSlO/3SuvbNVDjljmbWHSBDr3K15L0nMGJiSGiDFZYOHep9HXl4IJ8F gOJmDb40SNdwD1VG5+nVlzy+Rd3kl7JBriGnBe/G3RBlbjLfyNw1FfjIBa5AzMKXcA oODvAkx/tmg7K6b7APd8GyDjxT/as4xHwe8LCbi4=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe2ca93c0d6cf912b71f67cd640e6243b7c46c48892cf00000001175169d692a169ce1418d0ad@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1507/401668401@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1507@github.com>
References: <quicwg/base-drafts/issues/1507@github.com>
Subject: Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b39a7d64c8d8_109473fc535a62f7c1356312"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1QYk94R2D1zNiMK32TEEuDFyzH4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 02 Jul 2018 04:19:43 -0000
The point is that if the handshake is successful, then the ClientHello and all the 0-RTT have the same destination connection ID, so they probably end up at the same point. Add Retry and they might not. I think that the TLS analogy is fine. In TLS, a server could want a different key share, but find the PSK perfectly adequate for the purposes of 0-RTT. There's no reason a server that sends HelloRetryRequest would need to stop accepting 0-RTT. -- 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/1507#issuecomment-401668401
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Nick Banks
- [quicwg/base-drafts] Can a client send 0-RTT data… Kazuho Oku
- Re: [quicwg/base-drafts] Can a client send 0-RTT … ekr
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Martin Thomson
- Re: [quicwg/base-drafts] Can a client send 0-RTT … ekr
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Martin Thomson
- Re: [quicwg/base-drafts] Can a client send 0-RTT … MikkelFJ
- Re: [quicwg/base-drafts] Can a client send 0-RTT … ekr
- Re: [quicwg/base-drafts] Can a client send 0-RTT … MikkelFJ
- Re: [quicwg/base-drafts] Can a client send 0-RTT … ekr
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Kazuho Oku
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Martin Thomson
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Kazuho Oku
- Re: [quicwg/base-drafts] Can a client send 0-RTT … Martin Thomson