Re: [quicwg/base-drafts] NEW_TOKEN should be symmetric (#2760)
Kazuho Oku <notifications@github.com> Fri, 31 May 2019 06:34 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 8AC9B12007A for <quic-issues@ietfa.amsl.com>; Thu, 30 May 2019 23:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Level:
X-Spam-Status: No, score=-6.391 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_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, T_DKIMWL_WL_HIGH=-0.01] 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 eBOYMOyFFJ9t for <quic-issues@ietfa.amsl.com>; Thu, 30 May 2019 23:34:00 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6249212008D for <quic-issues@ietf.org>; Thu, 30 May 2019 23:33:58 -0700 (PDT)
Date: Thu, 30 May 2019 23:33:57 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1559284437; bh=vR8Uxg27PReL/Vjrgkb38MY7Zbbskhy8BsNqmLOsqWo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q8+EG3nuapdkLiGe2LvcVbOI/7Rj7ZtB2ChQnJrdBpNfDjpbUgwlSTNnTRQ193Orj yze0I381Pq3nHChE+lvk2rGfYe2WE3bBMvhS1jigJ4qmKfQG4CKDg7LkYcn3xySB4U dLOaGt2atf+X3cgjLItHPuJ3SiWj4awquPXoZhQI=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYG374JT5LRQVDVITF27X6VLEVBNHHBVVRQLI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2760/497593367@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2760@github.com>
References: <quicwg/base-drafts/issues/2760@github.com>
Subject: Re: [quicwg/base-drafts] NEW_TOKEN should be symmetric (#2760)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cf0cad52aae_207f3ff3b26cd9601164cc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/XTuIX8FwMEe3flqWKETGx6CO81U>
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: Fri, 31 May 2019 06:34:03 -0000
While I can understand the desire, I am wary of the complexity that it might introduce. I am not sure if we could consider (and continue to consider) the use-case during the development and the maintenance of the protocol. Hence the question: how important is it? The only case you'd benefit a round trip from using a NEW_TOKEN token is when you can do 0-RTT. However, 0-RTT can only be used when a connection in the same direction has been established before. Considering that, I wonder what the benefit is. -- 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/2760#issuecomment-497593367
- [quicwg/base-drafts] NEW_TOKEN should be symmetri… Marten Seemann
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Dmitri Tikhonov
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Marten Seemann
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Jana Iyengar
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Marten Seemann
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Kazuho Oku
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Marten Seemann
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… MikkelFJ
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Kazuho Oku
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… ekr
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Martin Thomson
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Marten Seemann
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… MikkelFJ
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Martin Thomson
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Martin Thomson
- Re: [quicwg/base-drafts] NEW_TOKEN should be symm… Martin Thomson