IETF Logo Mail Archive

Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507)

Kazuho Oku <notifications@github.com> Wed, 18 July 2018 15:52 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 57B44130EEE for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 08:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 nv_pp9Wrd6vT for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 08:52:50 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA0B2130E14 for <quic-issues@ietf.org>; Wed, 18 Jul 2018 08:52:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=MoZRBM3oWpzGZsFOxzcDvFfF3sQ=; b=QEnpoIoizjKTYZrr GBdvPQlTGQJKqBHCSrfDYV6xebAKNTkoX4doksosH90fFdr0GoXzfFf4Y8mI+rPs wD2oiI/WkW0w0/zYsFhtmKxUh1Q4CjxepAqoL3n/165TtBY/H8oKaPVDvbq3rXU0 8ypIVliEyqTr6+cI9aATDKmKusc=
Received: by filter0603p1iad2.sendgrid.net with SMTP id filter0603p1iad2-10630-5B4F624F-61 2018-07-18 15:52:47.973468183 +0000 UTC m=+60451.497324748
Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id f7JkbIOaSqGXJxs1I8eVRg for <quic-issues@ietf.org>; Wed, 18 Jul 2018 15:52:47.819 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id C71EF41075 for <quic-issues@ietf.org>; Wed, 18 Jul 2018 08:52:47 -0700 (PDT)
Date: Wed, 18 Jul 2018 15:52:48 +0000
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba5343506da7f6376d71727b256ef5df0e1cbb09d92cf000000011767244f92a169ce1418d0ad@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1507/405981043@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1507@github.com>
References: <quicwg/base-drafts/issues/1507@github.com>
Subject: Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4f624fc4ef7_423c3fa5f6cbef7c1112c9"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2uSE09U016vHgsu3EETjS+RwfhKyED0ZhsG5 C8K9P4A+SQxqO9xZi8XI5cGQl259iO6BeEj2CRRxyWDbh9WchNiopz2LBuScJC7xAbSzlSs7fuZ6f2 nHlzTKXJvzas+VvC02Ikt7XpiLJ3RqSeKkwX2qAQr7rZNRhFWgV9Y0XwwUf1d2ZYwqFLPRnXukxYl/ g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/3P0ZT2e5JWAm3eLsMbCoPUiFP5A>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 18 Jul 2018 15:52:53 -0000

Note that since -13, the settings of the previous connection will be retained in the token, because we no longer define an extension slot in NewSessionTicket. The conveyer of address validation data _and setting information_ have moved to token.

However, token (which is contained in a Initial that attempts a 0-RTT) is replaced once the server sends a Retry packet.

That makes handling of 0-RTT a bit complicated, especially when the information about previous settings is necessary to determine if a server accepts the 0-RTT (see #1541).

-- 
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/1507#issuecomment-405981043

v2.23.0 | Report a Bug | By Email