Re: [quicwg/base-drafts] introduce an error code for loss recovery-related errors (#2319)

Marten Seemann <> Wed, 09 January 2019 13:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 338671228B7 for <>; Wed, 9 Jan 2019 05:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.653
X-Spam-Status: No, score=-10.653 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-4.553, 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rd2jcuJCOy3X for <>; Wed, 9 Jan 2019 05:20:31 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3145712426E for <>; Wed, 9 Jan 2019 05:20:30 -0800 (PST)
Date: Wed, 09 Jan 2019 05:20:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547040028; bh=e+oTDBgpLbhpTJUKa2bw6jgvWbVhOZznQmV6Nlahen0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gogycBmvqvnGgsANN8zCfhLqh49V+eTlPWin8nlh7szRAD92JnYkV+60p699LZ1CA a/TjUIInp8prv9dW2Mb8QCgzx7Gkyt3xXyk1HmREO8Y/hSlv5sqT836Elj8lQMgjsu zidULcBVaMqs46IQjc8ac+kpUybhRNqR78+X4lTo=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2319/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] introduce an error code for loss recovery-related errors (#2319)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c35f51c9fbf5_1a203fa80fcd45b4186355"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Jan 2019 13:20:34 -0000

> The question is if there is a group of errors that fall into the category. Do you have something other than ACK containing an invalid packet number in mind?

I can think of three different cases why an ACK would contain an invalid packet number:

- the obvious case: you ack a too high packet number, which wasn't sent yet
- you ack in the wrong packet number space. This will most likely look like you acked a packet that the peer didn't send (in that packet number space)
- I assume that most implementations will sooner or later implement skipping of packet numbers as a mitigation of the optimistic ack attack. This error would occur when you ack a packet number that was intentionally skipped.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: