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

MikkelFJ <> Wed, 09 January 2019 09:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B119A130DC7 for <>; Wed, 9 Jan 2019 01:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, 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 t8sAhA6zYZBf for <>; Wed, 9 Jan 2019 01:58:44 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E2C21130DC1 for <>; Wed, 9 Jan 2019 01:58:43 -0800 (PST)
Date: Wed, 09 Jan 2019 01:58:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547027922; bh=iaZlXqE81OQmrs7nmD7t3Kny50APIr/8wexguliOsa0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WStTkDj6Z6fsy6NDRRWx4Y5GBnWrkadKfM5PMLiNUm+YuC+qMfQP0bY2Du15QCrr9 EbMKUnaqyIdhpClPZcR3Zw+yJ8cO8idcvFpFqCU2z1dy0DRwvHe+ypjGQYMM7Tlqii IusvNGY6nPqsUsItsSZJOewSYq/IRiEzuhtd5gTc=
From: MikkelFJ <>
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_5c35c5d285301_516d3f803a6d45bc12457f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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 09:58:46 -0000

Actually, optimistic ACK's could also be defended against by ignoring the invalid ACK's and silently downgrading the connection to min CWND. That would provide even less feedback to an attacker. But of course an error is needed for debugging. Not sure I would recommend this - but it is an option.

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