Re: [quicwg/base-drafts] Saving a round-trip time in the initial handshakes with retry (#2552)

Martin Thomson <notifications@github.com> Mon, 01 April 2019 09:25 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 3615A1200D6 for <quic-issues@ietfa.amsl.com>; Mon, 1 Apr 2019 02:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 bn-QeqTHXaGC for <quic-issues@ietfa.amsl.com>; Mon, 1 Apr 2019 02:25:13 -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 24A821200CE for <quic-issues@ietf.org>; Mon, 1 Apr 2019 02:25:13 -0700 (PDT)
Date: Mon, 01 Apr 2019 02:25:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554110712; bh=fP0kjyxm07Yat8quw6MGgPSLTm+W8Z6AWHZSH829fW4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GuFv/4BYnIKNvsOM3MmdeHovu7aboit7ISggnxF+EuMsNxNPNGeBqZ++HVvpj/AGP 7amGZr8Nbmq5CYev8TfrZAgsmRjUsl/v2WPmNCPlisyKbk5CUzJFZN0q47ee6lcnJX iojt4v4CSEzGPR1m5oA65bIZ5+pHjiRiAU+jRyxg=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1c65d36003966a0adac6472831d07796b8b4aeae92cf0000000118b99af892a169ce195632b6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2552/478504239@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2552@github.com>
References: <quicwg/base-drafts/issues/2552@github.com>
Subject: Re: [quicwg/base-drafts] Saving a round-trip time in the initial handshakes with retry (#2552)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca1d8f832873_16c03fc57e0d45c05406c"; 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/eqDj9X10HFVlkDi9h3MFAhGCYSg>
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: Mon, 01 Apr 2019 09:25:15 -0000

To expand on this a little.  I don't anticipate Retry being used very often.  QUIC provides Retry for extraordinary circumstances only.  Most servers will be able to complete the handshake without an explicit address validation step, relying on the implicit address validation provided by the sending and receipt of encrypted packets.  Retry might be used by servers with absurd certificates (maybe), by servers deploying massive PQ key exchange messages (maybe in future), or when servers are under load and they want to validate clients before expending resources.

This therefore less useful than a cross-origin TLS session ticket.  It might have some utility, but I suspect that it won't be necessary in the general case.

-- 
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/2552#issuecomment-478504239