IETF Logo Mail Archive

Re: Unrecoverable loss pattern

Christian Huitema <huitema@huitema.net> Fri, 02 March 2018 00:25 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E77A512EAF6 for <quic@ietfa.amsl.com>; Thu, 1 Mar 2018 16:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 zA67ndDR7GcK for <quic@ietfa.amsl.com>; Thu, 1 Mar 2018 16:25:52 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D4EB126FDC for <quic@ietf.org>; Thu, 1 Mar 2018 16:25:52 -0800 (PST)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx62.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1erYWE-0001Xs-4n for quic@ietf.org; Fri, 02 Mar 2018 01:25:50 +0100
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1erYW7-0006YZ-Ft for quic@ietf.org; Thu, 01 Mar 2018 19:25:47 -0500
Received: (qmail 32744 invoked from network); 2 Mar 2018 00:25:41 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.241]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 2 Mar 2018 00:25:41 -0000
To: quic@ietf.org
References: <CAOYVs2q1QSpvZjPRfbJmKhhQ6eApwLSSFSbbOBt2J-PAeqVELQ@mail.gmail.com> <CABkgnnWuXJb2_BcfU4N=ODwy5JDZKBBd6TyhFmXLbPgVrvCoEA@mail.gmail.com> <CAOYVs2q0q6YrFfipd7UEENoz2ht2Mr0fPqnvy5pJRz-bPxCJpw@mail.gmail.com> <059bc7c6-a8cb-c46b-c971-333b9051c222@huitema.net> <CAOYVs2ogy77tjE+e9_mj6YNYcsDP0iduUKsE-_JnMrOeo4jVbQ@mail.gmail.com> <CABkgnnVLdKiaEDdGKjLXB9wNZ8vxvV_ZyJQnLAR4VxsjUDvjyg@mail.gmail.com> <f62726b4-564a-4e45-726b-63705753ddf2@huitema.net> <CABkgnnU78mE55N9KHx2FqR6AvthyM86-+zG-VknQ3tfpeKh=Gw@mail.gmail.com> <9d646ca7-2c95-62fd-206f-10ec6ce4cd5d@huitema.net> <CAKcm_gOb_ZYD3bWZVq5y0O50jwnh98xME7p_tgY-TCNSZRkGfg@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <2046409d-b591-288f-2468-dbe59ee60318@huitema.net>
Date: Thu, 01 Mar 2018 16:25:40 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAKcm_gOb_ZYD3bWZVq5y0O50jwnh98xME7p_tgY-TCNSZRkGfg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: Unrecoverable loss pattern
X-Originating-IP: 168.144.250.245
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.32)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5m3yuskDW2f3fI51XVvpJ9p602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVi4pI7YV/Ba0JGZXYj0HWeuM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBCnY1T4UEFfy74vbELeG6IB/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjSYb8Ll5Ew7esaVIVXxqL4mdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3upW940lL8kAcN44/h+EKQY5T+fsIz86TG72Lx5ZI1p INh8UHPssUrY3MbbkBcNcJNmVNo8JSOlGFxq//8KTKzWD4heQHulQ78UyVYAqkOPExpBOi7IfT+J o+6tsQI5W/ewkYi/XXej6UeAUN96sXI71lsFqhWb3P21BZ9jlHPbPFwq1OWq5AgT2u0X1EqIKkvi eXvu854nt7H/RUKCbI+vOB6kNh2xMmXEi/DfgKmivsH4ZDUjV1XMPsTVKIkc4eRc9aUV1oY4fX3W 5eOCNA395VKQZZ28EUZBFBO/fNvHxyElgNeKRbf/ovInfUvaco3uymSkQySlRRw9754xJI2lDrnz sG5f+caI1dL5Ye/k8PTgs5pdKJpNpy9rpzw+UwWR2z7Rjs3BT1o4+6YSC6IfVgW9/bktU41htiJ8 fk7NkCSgONC3rqaXJrYXVXXByjf4baeCkx0hN8MDgAhE+CBnCUTZMc2PfI2VFTu1YYhfjg==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WPXlMkNscvReNrHQgvlVVjDA-TA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 00:25:54 -0000

On 3/1/2018 11:13 AM, Ian Swett wrote:

> The one byte frame could be an explicit signal to move on, but we
> still need a way to stop re-transmitting the Finished.  Does that
> frame serve as an acknowledgement of the Finished as well?  Doesn't
> the receipt of encrypted packets also serve as an acknowledgement of
> the Finished?  In either case, we're discussing an implicit ack of sorts.

My idea was that it is only sent after receiving the Finished message.
"I have received the Finished Message, I am done with the handshake, you
can consider that all handshake packets are implicitly acknowledged."

Of course, there is a downside to that. Servers who are eager to start
sooner might send that *before* they receive the Finished message. But
then, they could also guess the packet number that will be used to send
the finished message and forge an ACK. Unless we are willing to make the
numbers jump at this point, or something like that.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email