Re: [quicwg/base-drafts] Handshake failure after Retry (#1784)

ianswett <notifications@github.com> Fri, 21 September 2018 15:16 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 6CF9212777C for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 08:16:31 -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 Lhv4EEFYG-kP for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 08:16:29 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E576130E09 for <quic-issues@ietf.org>; Fri, 21 Sep 2018 08:16:29 -0700 (PDT)
Date: Fri, 21 Sep 2018 08:16:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537542987; bh=O0sPEEycfG/tKjTEK37UWxiDMXR5gDp3vhkCThWh3sA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mONqF8z14t1ZfO4qlLYwFT35Fmgt4HuOPbsXcLkh5dS0m23utJadarj/0hXvRI2ma 76eYNuM3ENBPUWjZ8Ai84MX8axUcwv1C+A486jp1WSGZWvsdcr1Tq0cjF5iGDN1me9 KDywc40LnOn/3++di8Rq/ErlIXwN7lW8Ez237gKs=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab549da522efd52e41176d61b6ac743db980a5b11492cf0000000117bccd4b92a169ce159d75ca@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1784/423569167@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1784@github.com>
References: <quicwg/base-drafts/issues/1784@github.com>
Subject: Re: [quicwg/base-drafts] Handshake failure after Retry (#1784)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba50b4bea1fd_1bd53fea952d45b428187"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/5iH9zEYNB3oRZ6o0KEk1CN7MnxE>
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: Fri, 21 Sep 2018 15:16:31 -0000

My previous assumption was that if the client the connection ID the same,
it was the same connection, and therefore the TLS context should be kept
the same.

a) is likely ok, but I believe the variant of b) above fits better with the
design we have I believe?

On Fri, Sep 21, 2018 at 10:42 AM Nick Banks <notifications@github.com>
wrote:

> I guess the solution is to either:
>
> a) Require Retry to change the CID.
> b) Restrict the client from starting a new TLS context in response to
> Retry.
> c) Have some other way for the client to differentiate between Retries,
> other than CID.
>
> a) sounds like the simplest option to me.,
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1784#issuecomment-423556054>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ATJJcSr8v9UPI1m-htRqfb1VvBA8PDHIks5udPrDgaJpZM4W0RMP>
> .
>


-- 
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/1784#issuecomment-423569167