Re: [quicwg/base-drafts] Requiring per application data in session ticket seems wrong (#3028)

Martin Thomson <notifications@github.com> Fri, 13 September 2019 05:47 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 CB0AE120086 for <quic-issues@ietfa.amsl.com>; Thu, 12 Sep 2019 22:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.353
X-Spam-Level:
X-Spam-Status: No, score=-6.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 0NOPcqf3JMQi for <quic-issues@ietfa.amsl.com>; Thu, 12 Sep 2019 22:47:22 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E805F120024 for <quic-issues@ietf.org>; Thu, 12 Sep 2019 22:47:21 -0700 (PDT)
Received: from github-lowworker-ca5950c.va3-iad.github.net (github-lowworker-ca5950c.va3-iad.github.net [10.48.17.57]) by smtp.github.com (Postfix) with ESMTP id 453BCA03B2 for <quic-issues@ietf.org>; Thu, 12 Sep 2019 22:47:21 -0700 (PDT)
Date: Thu, 12 Sep 2019 22:47:21 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK32HMDJIV7PUJQH43N3RBI5TEVBNHHB2ZES4M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3028/531106915@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3028@github.com>
References: <quicwg/base-drafts/issues/3028@github.com>
Subject: Re: [quicwg/base-drafts] Requiring per application data in session ticket seems wrong (#3028)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d7b2d693578e_30d3fac6b4cd9647435b"; 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/aPFXpII6BurSAVEOLmrHsvRHPrQ>
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, 13 Sep 2019 05:47:24 -0000

I think that we can address this by saying that clients need to remember this state alongside any ticket.  (And we should make it clear that the server needs to remember this also.  It doesn't have to put things in the ticket, though that might make it easier for it to correctly remember.)

-- 
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/3028#issuecomment-531106915