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

Kazuho Oku <> Wed, 09 January 2019 10:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7720E128766 for <>; Wed, 9 Jan 2019 02:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Status: No, score=-8.064 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_32=0.001, 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 IFU7GvJ4SiyD for <>; Wed, 9 Jan 2019 02:18:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B26C212008A for <>; Wed, 9 Jan 2019 02:18:30 -0800 (PST)
Date: Wed, 09 Jan 2019 02:18:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547029109; bh=xIsyH6Z7oU/f38EQvMw3ZGh9UfIPU41lplMLo0iq1h4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MfecADExr99JCO9085GbdfBiI2iJ9UIWg5KsQj5Mb/XGhaHyckaD6BZgPussN6/ia QpJU2tFz8D1JuF5cy5yVYLONpPVGswMIJ5oq0N7z9yFdKt4H+Opzvih5zWJLhCs0GJ MpDp+ES8waSqIsiAr0nwwkb8hdrXZ8SVbnm8aPC8=
From: Kazuho Oku <>
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_5c35ca759a241_2e1f3f85cd4d45bc74255"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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 10:18:33 -0000

> introduce an error code for loss recovery-related errors

I like the way you frame the issue. It is my understanding that we have so far assigned an error code for features rather than every one of the specific errors. Calling it "loss recovery-related errors" certainly follows that practice.

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?

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