Re: [quicwg/base-drafts] describe how a client is supposed to handle multiple tokens (#2801)

Martin Thomson <> Thu, 20 June 2019 01:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BD98E1200F7 for <>; Wed, 19 Jun 2019 18:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 pB3ZZBOYp6LD for <>; Wed, 19 Jun 2019 18:06:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2643A120052 for <>; Wed, 19 Jun 2019 18:06:26 -0700 (PDT)
Date: Wed, 19 Jun 2019 18:06:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560992785; bh=LO22w5nLtJgLyq8rNkrlA4qj0g6RHEn44VCxl3OiLWM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l8nmKY65OvOPGDb5d19ba8wMeq8mFqkiJ3ndxPfDTWCAD3ouBTnuOZ8TaCqUVNVuo eEDAobWEUmTlfTlt4ceYNqfsR1spCA/e+7G7bAnffRHQpkbfTINiP/dSQyP4ikQXcz MnXjMvuF+vscVbvQ5AywjWOj87Zw/ZVmrYbH1Lq4=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2801/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] describe how a client is supposed to handle multiple tokens (#2801)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0adc11216c0_4803fee134cd95c11264c"; 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
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: Thu, 20 Jun 2019 01:06:28 -0000

This is fine, and it merely reflects reality: older tokens are less likely to be useful.  But there is no harm in attempting to use any token, provided that it hasn't been used before.

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