Re: [quicwg/base-drafts] clarify how to handle Retry, as well as stating that a fixed mapping bet. versions and salts is better than nothing (373257b)

Mike Bishop <notifications@github.com> Wed, 30 October 2019 19:40 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 A3BD5120874 for <quic-issues@ietfa.amsl.com>; Wed, 30 Oct 2019 12:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
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: 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 9HkXg4ESj7PS for <quic-issues@ietfa.amsl.com>; Wed, 30 Oct 2019 12:40:51 -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 32432120852 for <quic-issues@ietf.org>; Wed, 30 Oct 2019 12:40:51 -0700 (PDT)
Received: from github-lowworker-6b40fdd.va3-iad.github.net (github-lowworker-6b40fdd.va3-iad.github.net [10.48.16.64]) by smtp.github.com (Postfix) with ESMTP id 8AA7A1C2F53 for <quic-issues@ietf.org>; Wed, 30 Oct 2019 12:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572464450; bh=JKqjaHhAiy6E7nbc7JrCCPKEUtnbFPq1NTHqgcwrDAQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pnQpzRdMjZy93IuZfespjuAiV3ZjXk9em5TO0Wy/MoyYJ1L6JTLVnZto9BrlycZPc b+ItOmK6VHbAUmyK1XLQEU6OgYQGzzf2BH9q7W7M5q5mX2JXqRGUackmOmmXVtvL1h wYd3wXBD68nBjfSzwKQapMyie3+Nfb5aWWiZoCac=
Date: Wed, 30 Oct 2019 12:40:50 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4XBJIZXWUQNHNWCCF3Y4T5FEVBMPHAEIKISM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/commit/373257b7b105ec5fff5251e0dcec0944970c0076/35735699@github.com>
In-Reply-To: <quicwg/base-drafts/commit/373257b7b105ec5fff5251e0dcec0944970c0076@github.com>
References: <quicwg/base-drafts/commit/373257b7b105ec5fff5251e0dcec0944970c0076@github.com>
Subject: Re: [quicwg/base-drafts] clarify how to handle Retry, as well as stating that a fixed mapping bet. versions and salts is better than nothing (373257b)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db9e7426b3e6_289d3f8edb0cd95c14264c"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VVQae2TXpcxyXg4Hcocm8EJwics>
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: Wed, 30 Oct 2019 19:40:52 -0000

This is one possible design, for a server that wants to do minimal work.  A server could, however, extract the salt and put it in the Retry token, no?  We should word this as a suggested implementation, not as the only one.

-- 
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/commit/373257b7b105ec5fff5251e0dcec0944970c0076#commitcomment-35735699