[quicwg/base-drafts] 3b7569: Permit 0-RTT after Retry and VN

Martin Thomson <martin.thomson@gmail.com> Tue, 03 July 2018 05:57 UTC

Return-Path: <bounce+565321.40f-quic-issues=ietf.org@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 28253130DF3 for <quic-issues@ietfa.amsl.com>; Mon, 2 Jul 2018 22:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 qOCc6zfcBicC for <quic-issues@ietfa.amsl.com>; Mon, 2 Jul 2018 22:57:08 -0700 (PDT)
Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 92CEF120049 for <quic-issues@ietf.org>; Mon, 2 Jul 2018 22:57:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530597427; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=hc82EWO+GG4CHh7AvTXoElznBnw9BEKLchjUKB9VqAI=; b=qFT8YVpFx3ta8hh+amqb/wwFjjg68+OBs4ktVjakfvUezWpQmVCisS2ZEcJGpK27D/PxGWy6 go7dbFz1vICe88dPuHwelNBU2FMdHVzClXJ+CBTD2xfuD8l2FMNjhdu3ZTCvIF8YboM1mCY3 p/AYFyFYNuKmhL8z5DIExAnnscw=
X-Mailgun-Sending-Ip: 166.78.71.131
X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ==
Sender: martin.thomson=gmail.com@github.com
Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3b1033.7f5dc2bb6bd0-smtp-out-n03; Tue, 03 Jul 2018 05:57:07 -0000 (UTC)
Date: Mon, 02 Jul 2018 22:57:06 -0700
From: Martin Thomson <martin.thomson@gmail.com>
Reply-To: Martin Thomson <martin.thomson@gmail.com>
To: quic-issues@ietf.org
Message-ID: <5b3b1032a5589_1792abde016fc10804fe@hookshot-fe-88eb02d.cp1-iad.github.net.mail>
Subject: [quicwg/base-drafts] 3b7569: Permit 0-RTT after Retry and VN
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_5b3b1032a51f2_1792abde016fc108039c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tRqi9YcfGhhn4MJzJlBTcY8wX6A>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
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: Tue, 03 Jul 2018 05:57:11 -0000

  Branch: refs/heads/allow-retry-0rtt
  Home:   https://github.com/quicwg/base-drafts
  Commit: 3b756980be074f9bf8115737a4ad1e95802d747c
      https://github.com/quicwg/base-drafts/commit/3b756980be074f9bf8115737a4ad1e95802d747c
  Author: Martin Thomson <martin.thomson@gmail.com>
  Date:   2018-07-03 (Tue, 03 Jul 2018)

  Changed paths:
    M draft-ietf-quic-recovery.md
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  Permit 0-RTT after Retry and VN

After the discussion on #1507, I've been convinced that there is no real
value in preventing a client from attempting 0-RTT after a Retry.  And,
it would seem like Version Negotiation has essentially the same
properties, so excluding it would be inconsistent.

This allows this, explores the consequences for packet numbers (don't
reset them!), and updates the recovery text to include Version
Negotiation.

Closes #1507.



      **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.