Re: [quicwg/base-drafts] Explain extraordinary conditions that lead to sending a Handshake packet (#2598)
Benjamin Saunders <notifications@github.com> Tue, 24 September 2019 02:50 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 E96EF120086 for <quic-issues@ietfa.amsl.com>; Mon, 23 Sep 2019 19:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_24=1.618, 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
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 uFgrdlMQI9qR for <quic-issues@ietfa.amsl.com>; Mon, 23 Sep 2019 19:50:40 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36312120046 for <quic-issues@ietf.org>; Mon, 23 Sep 2019 19:50:40 -0700 (PDT)
Received: from github-lowworker-292e294.va3-iad.github.net (github-lowworker-292e294.va3-iad.github.net [10.48.102.70]) by smtp.github.com (Postfix) with ESMTP id 9ED5E6E0768 for <quic-issues@ietf.org>; Mon, 23 Sep 2019 19:50:39 -0700 (PDT)
Date: Mon, 23 Sep 2019 19:50:39 -0700
From: Benjamin Saunders <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6BKKQXIMYXMVUZYIV3S3CQ7EVBNHHBTM7YNU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2598/534365367@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2598@github.com>
References: <quicwg/base-drafts/issues/2598@github.com>
Subject: Re: [quicwg/base-drafts] Explain extraordinary conditions that lead to sending a Handshake packet (#2598)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d89847f8eef1_55133fdf448cd96813297d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: Ralith
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/pdaiZMRMcmHFUymCVg5jYR7qHmE>
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: Tue, 24 Sep 2019 02:50:42 -0000
I think the logic in the recovery draft misses some of these cases entirely. The rule in draft 23 is: > the client MUST set the probe timer if the client has not received an acknowledgement for one of its Handshake or 1-RTT packets. but in your example case there is not necessarily any unacknowledged data to transmit in a probe, and a `PING` is forbidden at Handshake level, leaving no reasonable options to compose an ACK-eliciting packet. -- 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/2598#issuecomment-534365367
- [quicwg/base-drafts] Explain extraordinary condit… Martin Thomson
- Re: [quicwg/base-drafts] Explain extraordinary co… Benjamin Saunders
- Re: [quicwg/base-drafts] Explain extraordinary co… Martin Thomson