Re: [quicwg/base-drafts] What if a client sends a NEW TOKEN frame? (#2382)

Martin Thomson <notifications@github.com> Mon, 26 August 2019 10:13 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 3A4FD120043 for <quic-issues@ietfa.amsl.com>; Mon, 26 Aug 2019 03:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, 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 RuTnO_jNrS0U for <quic-issues@ietfa.amsl.com>; Mon, 26 Aug 2019 03:13:20 -0700 (PDT)
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 EE8A5120041 for <quic-issues@ietf.org>; Mon, 26 Aug 2019 03:13:19 -0700 (PDT)
Date: Mon, 26 Aug 2019 03:13:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1566814399; bh=csEMj23sZD00Fpx7wAvLr+etLxeftVR3uy6hPVWEZlE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aNR4x3sVF5haCA5sVxRDjY8ItXq6xBUGsGm4cLje+TyC4Samgbftd1K3Kt+TDZNWc v4hwwLc+ltBgyYmkDLfqXcUdBW58AFwkUyuMr4IMaEv+MgZ3a2gu1NWmxba6tgkFLS STyhup80cZMhEYLqa9YHYDmd3KSYmpTgH79wNENQ=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZJXUIFO4FWIZ64FW53ODRT7EVBNHHBQFPF2E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2382/524804749@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2382@github.com>
References: <quicwg/base-drafts/issues/2382@github.com>
Subject: Re: [quicwg/base-drafts] What if a client sends a NEW TOKEN frame? (#2382)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d63b0bf453e3_63603f878d8cd9688135a"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VHbFz__DCZtuOB1qMXESJaed_FM>
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: Mon, 26 Aug 2019 10:13:21 -0000

I'll bite.  Yes, a P2P app that used mutual authentication in a way that would allow a former server to associate a token with an attempt to connect to a peer that was previously a client, might be able to use NEW_TOKEN.

That's a little outside our remit.  I'm going to take this as an editorial change on the understanding that a design issue could be opened to allow the asymmetry.

Anyone who is serious about that should also consider the fact that NewSessionTicket in TLS is potentially symmetrical by the same logic.  Which suggests that 0-RTT isn't out of the question either.

-- 
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/2382#issuecomment-524804749