IETF Logo Mail Archive

[quicwg/base-drafts] Rejection of 0-RTT: start over? (#761)

Martin Thomson <notifications@github.com> Wed, 06 September 2017 01:00 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 AFC91132E45 for <quic-issues@ietfa.amsl.com>; Tue, 5 Sep 2017 18:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level:
X-Spam-Status: No, score=-0.402 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 iSMaQtU06A9o for <quic-issues@ietfa.amsl.com>; Tue, 5 Sep 2017 18:00:20 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 5F2F41252BA for <quic-issues@ietf.org>; Tue, 5 Sep 2017 18:00:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=vhF/5r7Qcz0s4OiVunKbanfxFg0=; b=eKmenKKwPtoG+BD8 /yLW7XtvKq2hV6KgGljUZ2W5cvQ6rkSNZKhHdrKubY4Nn0StKbz0WtS0lFOe9Sxt ZfdUjrjOM+tY8tTCAXqr1WdczYIDe49GjN9ndUi/ErAE8n0nkpAesGNFynEO/MKd IC2/HgE6N0JwRbyq6gcxx4m2Bvs=
Received: by filter0594p1mdw1.sendgrid.net with SMTP id filter0594p1mdw1-21676-59AF48A0-38 2017-09-06 01:00:16.600846951 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0030p1mdw1.sendgrid.net (SG) with ESMTP id 4iMmLUFOTu6IjrDL3mTYqw for <quic-issues@ietf.org>; Wed, 06 Sep 2017 01:00:16.651 +0000 (UTC)
Date: Wed, 06 Sep 2017 01:00:16 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4f6c206b64045979633fba20aea8c6d1d4ebe8e192cf0000000115c70aa092a169ce0f39dd03@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/761@github.com>
Subject: [quicwg/base-drafts] Rejection of 0-RTT: start over? (#761)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59af48a065615_54553fa866707c3810345d"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1h5IgN8XbxGc6sSEmXg8Zg+0lyPJiYClKmWw 95kpgdERHCNFEzQ6xdeKrZ/A0aezam2yRtDSYN2AedH+G9OQiZDjLRp8+CPvXUexA+iwecwTZ8JViP VEGJ+KKJ4xwc1D3+WGiNj/5iHQBHEU2/GZ6jTqWpTUcpDqmW1HZmJndMlo+Ul97OIyaL5i1eRifpQ8 g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/GDDS219S-bHzat0ninCX2t1aRug>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Sep 2017 01:00:22 -0000

If 0-RTT is rejected should the client:

1. start over at the application layer
2. close all streams that it initiated (can't do that because stream 1 is special)
3. just pretend that the packets were lost and need retransmission

Previously, people (@RyanAtGoogle) advocated for 3.  So far the preponderance of feedback on the list has been in favour of 1, which is at least consistent with the approach in TLS.

-- 
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/761

v2.31.3 | Report a Bug | By Email | System Status