Re: [quicwg/base-drafts] Allow use of token after client address changes (#3307)

ianswett <notifications@github.com> Wed, 18 December 2019 15:12 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 AC62C12004E for <quic-issues@ietfa.amsl.com>; Wed, 18 Dec 2019 07:12:08 -0800 (PST)
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 X-fko41U8Lm6 for <quic-issues@ietfa.amsl.com>; Wed, 18 Dec 2019 07:12:07 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C49F120241 for <quic-issues@ietf.org>; Wed, 18 Dec 2019 07:12:07 -0800 (PST)
Received: from github-lowworker-6349a71.ac4-iad.github.net (github-lowworker-6349a71.ac4-iad.github.net [10.52.18.20]) by smtp.github.com (Postfix) with ESMTP id 9A9C65210DF for <quic-issues@ietf.org>; Wed, 18 Dec 2019 07:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1576681926; bh=F3n0hLABSj+nexIzhwqVS6HDvSUrvki8Bv3kElFfZiw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TKLnBebam9sSl9Qz4Ya+EkNvrZZhr9z/zsbsqLxHGR7lAy8IK9KeVKsu2LgW826bH hwiZA3nPLMP+ar1MmB8oC0p1TEkQat3923GHGKaGNwtj/6DKeuJAn2RUsf5lgUxGRV vvpq9Bi7u9l0ek3L1WYszQq00iQ0phloyUpL3xFU=
Date: Wed, 18 Dec 2019 07:12:06 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6YCMQV65U6V5BOEKN4A52ENEVBNHHCAJ5MJU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3307/567073179@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3307@github.com>
References: <quicwg/base-drafts/issues/3307@github.com>
Subject: Re: [quicwg/base-drafts] Allow use of token after client address changes (#3307)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dfa41c68a1df_751a3f8cd46cd9642049e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/u_jEMuTCKYqvSFeL7_2y8wNHpF8>
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, 18 Dec 2019 15:12:09 -0000

I agree this seems unnecessary, given tokens cannot be used multiple times.

The worst case scenario is including the token increases the number of Initial packets the client needs to send to two packets from one and the token turns out not to be useful for address validation.

-- 
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/3307#issuecomment-567073179