IETF Logo Mail Archive

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

Kazuho Oku <notifications@github.com> Thu, 10 January 2019 02:07 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 11ADD13105F for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 18:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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: 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 gXNYa4vg3pDY for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 18:07:29 -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 9424812F18C for <quic-issues@ietf.org>; Wed, 9 Jan 2019 18:07:29 -0800 (PST)
Date: Wed, 09 Jan 2019 18:07:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547086048; bh=cZI4/BH+RkvCTEh13h6f0oijAhvSsR4r06ZxdCqZkmA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ik2nDqA0oNSo+ykNadPQfLm6sZYGRpobk+jI0Xt7VycAb1hdzEh/xnx+6srbSkNZP GlmijDYu1sGAueKgzxplOCXDZbGzkKraOzFCmiGvmJsVQJFcLfpKOsXwwRC2Ed2C2F 5bMj14wXLL0PqdS54JdE+xjgkvC104ZCJlrU4PR8=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab744b1431019430d323dcefa3b54645746cee06de92cf00000001184e6ae092a169ce17ada169@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/452943163@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2319@github.com>
References: <quicwg/base-drafts/issues/2319@github.com>
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_5c36a8e07eddd_3bd13f88882d45c439550"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Fl3zOGghtjEwEd5Cf_4l-kiPmlk>
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: Thu, 10 Jan 2019 02:07:31 -0000

@marten-seemann Thank you for elaborating. To me it sounds that they would look like one symptom to the reciever; i.e. an invalid PN in ACK.

I was wondering if there is a intent to use the error code for other symptoms, because it would imply that there are group of errors that might be categorized as a group (based on my understanding that we assign error codes to each feature or category).

Though I am not strongly opposed to having an error code for this case, I fear if having an error code for this opens can of worms (i.e. "we have error code for this, so why not have another error code for X"). Therefore am trying to see what the line we would be trying to hold is.

-- 
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#issuecomment-452943163

v2.31.3 | Report a Bug | By Email | System Status