Re: [quicwg/base-drafts] unrecoverable loss pattern leads to deadlock (#2863)

Nick Banks <notifications@github.com> Sun, 30 June 2019 14:33 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 C850C120105 for <quic-issues@ietfa.amsl.com>; Sun, 30 Jun 2019 07:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 0fklQEySlNVd for <quic-issues@ietfa.amsl.com>; Sun, 30 Jun 2019 07:33:24 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9505C1200F7 for <quic-issues@ietf.org>; Sun, 30 Jun 2019 07:33:24 -0700 (PDT)
Date: Sun, 30 Jun 2019 07:33:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561905203; bh=U/3MIGni9t2PGkO35apHulcx9Pry39kiz8L2yRxs5QE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rpS6/e4QUGhfmzeX+Phe7c1BVtsbTTwCw6o3WAAiYYOuK8wlDYrXhV6e2jmfgG7iy ayPMnRXBJpYKM24pk79I9qbhxHi6W7COPqsiFKywXAszKLZ4la4j0WGi/gph75KHqF f3Ro3YXxmiqB3vlpFtkPoPPZKa71eQ4Z68rIb59c=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYIXQ4252S6P3VGL353EX5LHEVBNHHBXDZPBM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2863/507041222@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2863@github.com>
References: <quicwg/base-drafts/issues/2863@github.com>
Subject: Re: [quicwg/base-drafts] unrecoverable loss pattern leads to deadlock (#2863)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d18c8331ffc1_61583ff2816cd96050943d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/9DDhWKJ-vaYylCleFG_XBPdxguc>
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: Sun, 30 Jun 2019 14:33:27 -0000

Sounds like receiving a 1-RTT packet on the client side might need to be another way to confirm the handshake.
________________________________
From: Marten Seemann <notifications@github.com>
Sent: Sunday, June 30, 2019 12:14:22 AM
To: quicwg/base-drafts
Cc: Subscribed
Subject: [quicwg/base-drafts] unrecoverable loss pattern leads to deadlock (#2863)


There's a loss pattern that QUIC cannot recover from:
Assume client and server perform a handshake up to the point just after the server received the ClientFinished message. No packet loss happens so far. Both peers have now completed (but not yet confirmed) the handshake.

Right after sending the ClientFinished, the client sends a 1-RTT packet (e.g. containing application data). This packet is lost. The server sends an acknowledgement for the ClientFinished (in a Handshake packet), and this packet is lost as well. Furthermore, the server also sends a 1-RTT packet (e.g. containing a session ticket). This packet is successfully received and acknowledged by the client.

At this point the endpoint are in the following state: Since it received an acknowledgement for a packet sent with 1-RTT keys, the server now confirmed the handshake, and drops the Handshake keys. On the other hand, the client is still waiting for an acknowledgement for the ClientFinished, and retransmits it. It will however never receive an acknowledgement, since the server dropped the keys already.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F2863%3Femail_source%3Dnotifications%26email_token%3DAE5U2BKJ5EZBLQM2MERB6GDP5A6K5A5CNFSM4H4LZFRKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4PF4FQ&data=02%7C01%7Cnibanks%40microsoft.com%7C4fd9053c4f2d4701c4a908d6fd19d0d8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636974684655932091&sdata=JRTX%2BF4zbnsara0XzyE3FdB6gjPCXhoFA27oz%2FckEiY%3D&reserved=0>amp;reserved=0>, or mute the thread<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE5U2BIOSYQ43BY5PIJUGXTP5A6K5ANCNFSM4H4LZFRA&data=02%7C01%7Cnibanks%40microsoft.com%7C4fd9053c4f2d4701c4a908d6fd19d0d8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636974684655942081&sdata=ZcvfuYM3iCAEt2nSyc7y4Y1SLix0n8AeLrJwyedW2KY%3D&reserved=0>amp;reserved=0>.


-- 
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/2863#issuecomment-507041222