[quicwg/base-drafts] Lost client Initial is never retransmitted (#3056)

Benjamin Saunders <notifications@github.com> Sat, 21 September 2019 03:26 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 B2F3C12004A for <quic-issues@ietfa.amsl.com>; Fri, 20 Sep 2019 20:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_IMAGE_ONLY_28=1.404, 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 18ijlfp7EwOb for <quic-issues@ietfa.amsl.com>; Fri, 20 Sep 2019 20:26:29 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A64012004F for <quic-issues@ietf.org>; Fri, 20 Sep 2019 20:26:29 -0700 (PDT)
Date: Fri, 20 Sep 2019 20:26:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1569036388; bh=OXIl2ImAc3KxS6+XQClUCJtTBLmzw9dHG7WA4rnTdz4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=2VRJjn9HwD/11WMge7s0VxHHY4lDKh5T4rOKxbesX1ebNLu21vdzH3WE4mtts1g6U RkorO3zdq1H+r3Yr/owRB2r/hGgSJbQVQPrVI40Gpqx3e/x2O4OB/ttid0q8/FtTUA 6z5aQNlPQ7Xq6805PT0FFL7XywPxxaesGJkjRplI=
From: Benjamin Saunders <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK46HE4V3IGWKDQCFH53SLMPJEVBNHHB3GNALI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3056@github.com>
Subject: [quicwg/base-drafts] Lost client Initial is never retransmitted (#3056)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8598642625e_5eb93fd33aecd9644409d"; 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/akgAo5hFxSar3aGJ0M71wnU1jug>
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: Sat, 21 Sep 2019 03:26:31 -0000

As of https://github.com/quicwg/base-drafts/pull/2806, if the client's Initial is lost, there is no required behavior that leads to it being retransmitted. Because the client has received no ACKs, no `loss_time` is set, and no loss is detected, leading to the client only sending probe packets, which are not required to bear any particular data ("A probe packet **MAY** carry retransmitted unacknowledged data") so long as they are ACK-eliciting. The server, having no established connection state, cannot do anything with these packets. 

Quinn probes are currently a single PING frame (plus padding, when appropriate) for simplicity, so implementing the new logic immediately broke our tests. If recovery logic now requires probe packets to bear specific data to function correctly in certain circumstances, this should be specified explicitly.

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