Re: [quicwg/base-drafts] Does a Retry really need to change the CID? (#2837)

Mike Bishop <> Tue, 25 June 2019 18:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2628D120233 for <>; Tue, 25 Jun 2019 11:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gSXrfjs1_g7Z for <>; Tue, 25 Jun 2019 11:22:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 283E4120018 for <>; Tue, 25 Jun 2019 11:22:44 -0700 (PDT)
Date: Tue, 25 Jun 2019 11:22:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1561486963; bh=XDMe8q9doQca9UFhZhZkvIgBEv9DSoaNn7hb71pYV2U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CH1QyDlQdnUy16unik19GmaUyGjTZs9mjO55Ej/Pf4KpLOXH/3NbgC6ai6z+hGDZg S5mKeWxAVY+vIB/fbt2lnVGAufzGdpid0gjn22ChHfS8lJOxXFeItuwHqCpq/Npi+/ 6Opgbrsov+QvL3Ta/MImCxfbNcTKXHmc5LYZgXYQ=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2837/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does a Retry really need to change the CID? (#2837)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d1266731a186_93d3fc95a6cd96069306b"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Jun 2019 18:22:46 -0000

We had other reasons why this was critical, but we've changed other requirements in the spec that eliminated them.  (For example, when the client was permitted to change the ClientHello following a Retry, you had to know *which* Initial the server wound up responding to or the handshake would fail.)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: