[quicwg/base-drafts] introduce an error code for loss recovery-related errors (#2319)
Marten Seemann <notifications@github.com> Wed, 09 January 2019 08:10 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 A23F8130D7A for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 00:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level:
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: 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 wfMIXCwTUgrG for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 00:10:32 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED8CB128766 for <quic-issues@ietf.org>; Wed, 9 Jan 2019 00:10:31 -0800 (PST)
Date: Wed, 09 Jan 2019 00:10:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547021430; bh=YZ61qVa8x2AFff5/UIhJXdn7tsPDDpE0ccMUCIYW9AM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=eEfWeKGmRrIE6xUsUi0fPj7YGx1x8d0PUoaUbycjd7HquFm4as9K01ZIrn4WWtJfu T5DP7g7iK5GGeMVa/6iJNrb2ZONzm/Nfhi+ZjaDDgrgJikVI3/lYnlXKqx2r7gO170 yB19O3k9kvfF9QI9l1m6ygHMgLx5Q6sKJXJfM8gc=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4f6bae1a017f6f466a297d12e2942fc7b229523992cf00000001184d6e7692a169ce17ada169@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2319@github.com>
Subject: [quicwg/base-drafts] introduce an error code for loss recovery-related errors (#2319)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c35ac76988fb_61d13f9e264d45b470332a"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jjmNrHCOH3XMg8FBihOS6Njf3wM>
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: Wed, 09 Jan 2019 08:10:34 -0000
As discussed in https://github.com/quicwg/base-drafts/pull/2302#discussion_r245545039, I'd like to advocate for introducing a new error code for loss recovery-related errors, e.g. when an unsent packet (in a respective packet number space) is acknowledged. In general, we have transport error codes to describe the area where an error occurred. For example, we have a STREAM_STATE_ERROR, which is used when the peer sends frames for the wrong stream type or unopened stream types. And we have a FLOW_CONTROL_ERROR, for, obviously, flow-control related errors. Generating ACKs for multiple packet number spaces is not a trivial thing to do, and it would be of great help for debugging to have a more specific error here than the catch-all PROTOCOL_VIOLATION. -- 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/2319
- [quicwg/base-drafts] introduce an error code for … Marten Seemann
- Re: [quicwg/base-drafts] introduce an error code … MikkelFJ
- Re: [quicwg/base-drafts] introduce an error code … Marten Seemann
- Re: [quicwg/base-drafts] introduce an error code … MikkelFJ
- Re: [quicwg/base-drafts] introduce an error code … MikkelFJ
- Re: [quicwg/base-drafts] introduce an error code … ianswett
- Re: [quicwg/base-drafts] introduce an error code … MikkelFJ
- Re: [quicwg/base-drafts] introduce an error code … MikkelFJ
- Re: [quicwg/base-drafts] introduce an error code … Kazuho Oku
- Re: [quicwg/base-drafts] introduce an error code … Marten Seemann
- Re: [quicwg/base-drafts] introduce an error code … Kazuho Oku
- Re: [quicwg/base-drafts] introduce an error code … Kazuho Oku
- Re: [quicwg/base-drafts] introduce an error code … ianswett
- Re: [quicwg/base-drafts] Error code for acknowled… Christian Huitema
- Re: [quicwg/base-drafts] Error code for acknowled… Mark Nottingham
- Re: [quicwg/base-drafts] Error code for acknowled… Mark Nottingham