IETF Logo Mail Archive

Re: [quicwg/base-drafts] Tickets and tokens are not for communication (#3820)

ekr <notifications@github.com> Fri, 03 July 2020 22: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 418163A09D5 for <quic-issues@ietfa.amsl.com>; Fri, 3 Jul 2020 15:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 0oH0V3y8-LpE for <quic-issues@ietfa.amsl.com>; Fri, 3 Jul 2020 15:34:33 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFF463A09D4 for <quic-issues@ietf.org>; Fri, 3 Jul 2020 15:34:32 -0700 (PDT)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net (github-lowworker-3a0df0f.ac4-iad.github.net [10.52.25.92]) by smtp.github.com (Postfix) with ESMTP id D58B48C0356 for <quic-issues@ietf.org>; Fri, 3 Jul 2020 15:34:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1593815671; bh=WHVtj1NOKjTk9rVY2wy02HnJ+ySJs6tKIGhW8YKLF5k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nmitTUndmczyJFNGJvrmpL+hf800yUiHr7e72PlRln0nN4XY4M84gx5p572Tw9GW7 O/iaLxO0gbhuYuPeJ11JvDxCKizPYMnmiS8S/Qrlcl/Lmo6uJAGkGt7JuhPFqIiHlZ TjVJgwlhaghLy3a3Ly/oMGRw3ArJygWQAt5bjWEk=
Date: Fri, 03 Jul 2020 15:34:31 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7B4DLFNVY5TSAYBHV5BOJXPEVBNHHCNQ4BGY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3820/review/442570064@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3820@github.com>
References: <quicwg/base-drafts/pull/3820@github.com>
Subject: Re: [quicwg/base-drafts] Tickets and tokens are not for communication (#3820)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5effb277c6145_6a383fb6a82cd960135762a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/UzbynzJLGmftOacrQ_dDfY5TOyA>
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, 03 Jul 2020 22:34:34 -0000

@ekr commented on this pull request.



> @@ -1763,8 +1763,10 @@ those produced by the application protocol that QUIC serves.
 Note:
 
 : TLS session tickets and address validation tokens are used to carry QUIC
-  configuration information between connections.  These MUST NOT be used to
-  carry application semantics.  The potential for reuse of these tokens means
+  configuration information between connections.  Specifically, to enable a
+  server to efficiently recover state that is used in connection establishment
+  and address validation.  These MUST NOT be used to communicate application
+  semantics between endpoints.  The potential for reuse of these tokens means

This actually seems pretty subtle. Instead, I would say:

These have no application-level semantics; clients MUST treat them as opaque values.






-- 
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/3820#pullrequestreview-442570064

v2.23.0 | Report a Bug | By Email