Re: [quicwg/base-drafts] Provide guidelines on token validation (#2132)

Martin Thomson <> Fri, 09 August 2019 04:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E41601200F6 for <>; Thu, 8 Aug 2019 21:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Status: No, score=-6.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 sixOU3qfmQEC for <>; Thu, 8 Aug 2019 21:24:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 884F21200A3 for <>; Thu, 8 Aug 2019 21:24:55 -0700 (PDT)
Date: Thu, 08 Aug 2019 21:24:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565324694; bh=sKeroA+fOyLAzstJDGaubQe2/o6j8GlLCoWtxjpOJRg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T+XqyAWBuwbtAkaMsnWO0TFDy7HT8ZXUCXgl1f4kpsLhG2AST8DZXhB6XAvPIW4QW uWUnQv8hCYwP0it7qxP8JhifsIIguCLmuZDUh3/KFP+0OpZiG0hMN+rE4DPgTxRO5I BFdydfBT8w1Mnh1Vmlhxf8wV46FuKZyUmg8ZuSIk=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2132/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Provide guidelines on token validation (#2132)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d4cf596cf666_14d73fb8b86cd96846439f"; 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: Fri, 09 Aug 2019 04:24:57 -0000

I think that we already have most of this.  The text lacks some of the specificity you might desire, but that's the nature of specifications.  For instance, we can't bind NEW_TOKEN to an IP address with a "MUST" in the spec because a server might reasonably identify connections from the same NAT as being equivalent and therefore valid (or it might not, depending on circumstance).

I don't plan to do anything about this issue, but I would entertain a PR that improved the text.

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