Re: [quicwg/base-drafts] Describe interaction between QUIC and TLS regarding saved 0-RTT state (#2947)

Martin Thomson <notifications@github.com> Fri, 23 August 2019 00:16 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 0476B12011C for <quic-issues@ietfa.amsl.com>; Thu, 22 Aug 2019 17:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_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 olwJOHLDQ-8B for <quic-issues@ietfa.amsl.com>; Thu, 22 Aug 2019 17:16:39 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3522F1200E3 for <quic-issues@ietf.org>; Thu, 22 Aug 2019 17:16:39 -0700 (PDT)
Date: Thu, 22 Aug 2019 17:16:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1566519398; bh=gOcDwEH9tEv70y7SUR1j4mTq2Ufpq1BmrNmNaCK+BaI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PsKc/+aQT/ngq66MmU0WRMAnywnqoPHK7Xu/kJunWhWorO1Cd+Ub1oX/ZgD6aCWDr JlCm0h6YqgwePYDS8iQ5iVU+LOTYaDbXNGLK4YiH726Lhpco1NpKZ23YqF5lg7pVLl IDrg41DdlXRCJqtH9vIexvfNhB3lPk7a2SSBrjHM=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2PENR4JFHVDNRWT6V3NRRONEVBNHHBYXLIMY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2947/review/278745896@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2947@github.com>
References: <quicwg/base-drafts/pull/2947@github.com>
Subject: Re: [quicwg/base-drafts] Describe interaction between QUIC and TLS regarding saved 0-RTT state (#2947)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d5f306623a57_20133fd022ecd95c1409dd"; 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/rb9t6TwD35dBgYSmqiTo4EitBfk>
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, 23 Aug 2019 00:16:41 -0000

martinthomson approved this pull request.

Assuming you take my suggestions, this is good.

>  primary functions:
 
 - Sending and receiving handshake messages
+- Processing stored transport and application state from a 0-RTT capable session
+  ticket and determining if it is valid to accept early data on the connection

```suggestion
  and determining if it is valid to accept early data
```

>  primary functions:
 
 - Sending and receiving handshake messages
+- Processing stored transport and application state from a 0-RTT capable session

s/0-RTT capable session ticket/resumed session/

```suggestion
- Processing stored transport and application state from a resumed session
```

As before with the mention of tickets; and early data is already covered.

> @@ -644,6 +647,27 @@ A client MAY attempt to send 0-RTT again if it receives a Retry or Version
 Negotiation packet.  These packets do not signify rejection of 0-RTT.
 
 
+## Validating 0-RTT configuration

```suggestion
## Validating 0-RTT Configuration
```

> +When a server receives a ClientHello with the "early_data" extension, it has to
+decide whether to accept or reject early data from the client. Some of this
+decision is made by the TLS stack (e.g., checking that the cipher suite being
+resumed was included in the ClientHello; see Section 4.2.10 of {{!TLS13}}). Even
+when the TLS stack has no reason to reject early data, the QUIC stack or the
+application protocol using QUIC might reject early data because the
+configuration of the transport or application associated with the resumed
+session is not compatible with the server's current configuration.
+
+QUIC requires additional transport state to be associated with a 0-RTT session
+ticket. If stateless session tickets are used, this information must be stored
+in the session ticket. Application protocols that use QUIC might have similar
+requirements regarding associating or storing state. This associated state is
+used for deciding whether early data must be rejected. For example, HTTP/3
+({{QUIC-HTTP}}) settings determine how early data from the client is
+interpreted. Other applications using QUIC could have different requiremenets

```suggestion
interpreted. Other applications using QUIC could have different requirements
```

> +decide whether to accept or reject early data from the client. Some of this
+decision is made by the TLS stack (e.g., checking that the cipher suite being
+resumed was included in the ClientHello; see Section 4.2.10 of {{!TLS13}}). Even
+when the TLS stack has no reason to reject early data, the QUIC stack or the
+application protocol using QUIC might reject early data because the
+configuration of the transport or application associated with the resumed
+session is not compatible with the server's current configuration.
+
+QUIC requires additional transport state to be associated with a 0-RTT session
+ticket. If stateless session tickets are used, this information must be stored
+in the session ticket. Application protocols that use QUIC might have similar
+requirements regarding associating or storing state. This associated state is
+used for deciding whether early data must be rejected. For example, HTTP/3
+({{QUIC-HTTP}}) settings determine how early data from the client is
+interpreted. Other applications using QUIC could have different requiremenets
+for determining whether ot accept or reject early data.

```suggestion
for determining whether to accept or reject early data.
```

-- 
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/2947#pullrequestreview-278745896