Re: [quicwg/base-drafts] Should we allow ACK-only packets to be declared lost? (#3451)
Igor Lubashev <notifications@github.com> Sun, 01 March 2020 16:39 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 83A213A0888 for <quic-issues@ietfa.amsl.com>; Sun, 1 Mar 2020 08:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level:
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 E6Rh5UvclnWP for <quic-issues@ietfa.amsl.com>; Sun, 1 Mar 2020 08:39:34 -0800 (PST)
Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E09E13A0895 for <quic-issues@ietf.org>; Sun, 1 Mar 2020 08:39:33 -0800 (PST)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id 71B681210BC for <quic-issues@ietf.org>; Sun, 1 Mar 2020 08:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1583080773; bh=BS59fEuSsnsvUnzeTnYGMmlINCRvBLRCTwZvgMJUmLA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jsdYLfTZWW7Jj/pFHxHB2wc+LEErSs1GAv10homIVRcgjPgxkdjP0FHVZNk5hB202 h47Cth5SkcK/j+lkMZj3xY05ETu9FG+hn3ahyIsGfbfu5A3PKkbZn8+LhufSIr5f6M JLbxUWpUqtaFZoiWGdCCe9QnArUWlqHtr7sWDPpY=
Date: Sun, 01 Mar 2020 08:39:33 -0800
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYI2XKAJUYXLHBTURV4M7DELEVBNHHCDF6P4Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3451/593117062@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3451@github.com>
References: <quicwg/base-drafts/issues/3451@github.com>
Subject: Re: [quicwg/base-drafts] Should we allow ACK-only packets to be declared lost? (#3451)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e5be5452bf62_259a3ffc25ccd95c15594d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/FHH_spnqCj6KLuMptIaYDfotaWw>
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: Sun, 01 Mar 2020 16:39:37 -0000
Happy to discuss acknowledgement reliability, though I want to point out that the two issues are related. If it is decided that non-ACK-eliciting packets will be acknowledged eventually (except for special circumstances, such as connection termination or packet number space issues), then it informs the "considered lost" discussion. -- 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/3451#issuecomment-593117062
- [quicwg/base-drafts] Should we allow ACK-only pac… Martin Thomson
- Re: [quicwg/base-drafts] Should we allow ACK-only… Kazuho Oku
- Re: [quicwg/base-drafts] Should we allow ACK-only… Martin Thomson
- Re: [quicwg/base-drafts] Should we allow ACK-only… Kazuho Oku
- Re: [quicwg/base-drafts] Should we allow ACK-only… Martin Thomson
- Re: [quicwg/base-drafts] Should we allow ACK-only… Kazuho Oku
- Re: [quicwg/base-drafts] Should we allow ACK-only… Marten Seemann
- Re: [quicwg/base-drafts] Should we allow ACK-only… Martin Thomson
- Re: [quicwg/base-drafts] Should we allow ACK-only… Kazuho Oku
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett
- Re: [quicwg/base-drafts] Should we allow ACK-only… mirjak
- Re: [quicwg/base-drafts] Should we allow ACK-only… Martin Thomson
- Re: [quicwg/base-drafts] Should we allow ACK-only… Jana Iyengar
- Re: [quicwg/base-drafts] Should we allow ACK-only… Christian Huitema
- Re: [quicwg/base-drafts] Should we allow ACK-only… Igor Lubashev
- Re: [quicwg/base-drafts] Should we allow ACK-only… MikkelFJ
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett
- Re: [quicwg/base-drafts] Should we allow ACK-only… Igor Lubashev
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett
- Re: [quicwg/base-drafts] Should we allow ACK-only… Igor Lubashev
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett
- Re: [quicwg/base-drafts] Should we allow ACK-only… ianswett