[quicwg/base-drafts] Retry Token Makeup (#1474)

Nick Banks <notifications@github.com> Mon, 25 June 2018 13:31 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 EC3CD130DF0 for <quic-issues@ietfa.amsl.com>; Mon, 25 Jun 2018 06:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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] 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 FOIumWWBIBJO for <quic-issues@ietfa.amsl.com>; Mon, 25 Jun 2018 06:31:27 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98FE4130DED for <quic-issues@ietf.org>; Mon, 25 Jun 2018 06:31:27 -0700 (PDT)
Date: Mon, 25 Jun 2018 06:31:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529933486; bh=NUS5/7xkqmbd/L7+LfaAGePQJh3LTVEUxsgIyAPgdKQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=KCh9o9CTDna0CWM2UwSF8fVbZr53Ne8lLXFumA/TD3mSH9cY+agFCgGJk/J0zk8OO TYbXC7lZc6672eCwfzbTWfhlhB7MPE5RjI8IMzlrZSGYnNPGiIyYXFs68MiWs4zf6D i140vE7Q2He22Q4eEzbFMby7je1tL8nCHGM+DPN0=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab221a8cc98b46d071474e3842b95b8a982835ef8392cf000000011748b0ae92a169ce13fdec96@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1474@github.com>
Subject: [quicwg/base-drafts] Retry Token Makeup (#1474)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b30eeae96bf0_58462ac61bdacf588644f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/8lgh0EE0_pvmOQG33ns3qO0-H_M>
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, 25 Jun 2018 13:31:29 -0000

This issue is related to the new Stream 0 dt PR (#1450).

Is a client allowed to change its connection ID in response to a Retry packet from a server?

The reason I ask is that it is possible to conceive of a server generating a token for a stateless Retry that encodes the client's original CID (among other things) in it for validation purposes. If the client is allowed to change its CID, then that obviously would break. So I feel we should have text either explicitly saying the client may (which I don't see how we could prevent) change its CID, and that a server shouldn't try to use the CID for stateless Retry validation or that a client must not change its CID so the server can use it for validation in stateless Retry.

-- 
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/1474