Re: [quicwg/base-drafts] clarify the scope of a NEW_TOKEN token (#3156)
MikkelFJ <notifications@github.com> Thu, 14 November 2019 10:26 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 E887B1207FE for <quic-issues@ietfa.amsl.com>; Thu, 14 Nov 2019 02:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 zmIHmqhmTx58 for <quic-issues@ietfa.amsl.com>; Thu, 14 Nov 2019 02:26:19 -0800 (PST)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3EA012022D for <quic-issues@ietf.org>; Thu, 14 Nov 2019 02:26:18 -0800 (PST)
Date: Thu, 14 Nov 2019 02:26:18 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573727178; bh=tU+BPfyO8ZT9s/yX+WEXiDtdUJ0t3tDGFXOep5awd90=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UOYuNx3zFmBoNL2d0O0Uwv2s1RxQOjONMUy5E/YnVxeKXEsHI134tXIKS88JFCjq+ +x5Bg1QInsXGiZ/4tFd4WtQaEgEOLhlTD+PxKGQ87xSK+A7+qDN7Rg9K6o+0m+C2S9 HvwMLjro/81Kr9G4wBDOLnijv86D9G8i2SQMDtYE=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7SLYLJZI4D4OSRFGV33JPETEVBNHHB5FNSNM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3156/review/316849641@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3156@github.com>
References: <quicwg/base-drafts/pull/3156@github.com>
Subject: Re: [quicwg/base-drafts] clarify the scope of a NEW_TOKEN token (#3156)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dcd2bca104e_2cb53fe17c8cd96023943ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/82ccO-LdOTyz4h6YANTXYSRoX3g>
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: Thu, 14 Nov 2019 10:26:22 -0000
mikkelfj commented on this pull request. > @@ -1698,10 +1698,15 @@ encrypted form in the token. It is unlikely that the client port number is the same on two different connections; validating the port is therefore unlikely to be successful. -If the client has a token received in a NEW_TOKEN frame on a previous connection -to what it believes to be the same server, it SHOULD include that value in the -Token field of its Initial packet. Including a token might allow the server to -validate the client address without an additional round trip. +A token received in a NEW_TOKEN frame is applicable to any server that the +connection is considered authoritative for (e.g., server names included in the +certificate). When connecting to a server for which the client retains an +applicable and unused token, it SHOULD include that token in the Token field of +its Initial packet. Including a token might allow the server to validate the +client address without an additional round trip. A client MUST NOT include a +token that is not applicable to the server that it is connecting to, unless the +client has the knowledge that the server that issued the token and the server +the client is connecting to are jointly managing the tokens. I see thanks, even I participated in that, too many things going on I guess. -- 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/pull/3156#discussion_r346232971
- [quicwg/base-drafts] clarify the scope of a NEW_T… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Martin Thomson
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Martin Thomson
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Martin Thomson
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Jana Iyengar
- Re: [quicwg/base-drafts] clarify the scope of a N… MikkelFJ
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… MikkelFJ
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… MikkelFJ
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… MikkelFJ
- Re: [quicwg/base-drafts] clarify the scope of a N… ekr
- Re: [quicwg/base-drafts] clarify the scope of a N… MikkelFJ
- Re: [quicwg/base-drafts] clarify the scope of a N… Kazuho Oku
- Re: [quicwg/base-drafts] clarify the scope of a N… Martin Thomson