Re: [quicwg/base-drafts] bytes_in_flight update issue (#2009)

ianswett <notifications@github.com> Tue, 20 November 2018 18:24 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 57ED5130DCF for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 10:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 Kz_u4arzRKm4 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 10:24:54 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B9941277BB for <quic-issues@ietf.org>; Tue, 20 Nov 2018 10:24:54 -0800 (PST)
Date: Tue, 20 Nov 2018 10:24:53 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542738293; bh=1oJBNraiKdczrnFSPAqVpi7vSVtXfAUzTdFet8REDTE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JPZDBw+rBUm5aaIuK8sOruwDIFS0/qOgiE0rN4lNOJqxHJkTgJEpmS6yDXUnD1YVV C2V9IU5efvkOn8wDlrOFCkrbhlX84Mqqt/zUHh/9rlWmhtdI+B4ISBEtiTmEjn6WLg SPvwb1GxplyqFG12gHaS7s07Cqr6R8U+nSVjH420=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab014069bcf03bcb0bf1c9087fa130e20cc4aae99692cf00000001180c137592a169ce16b845fa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2009/440380559@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2009@github.com>
References: <quicwg/base-drafts/issues/2009@github.com>
Subject: Re: [quicwg/base-drafts] bytes_in_flight update issue (#2009)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf4517546c64_649d3fdfaacd45b48019"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/I_hqNCwxxY9sT76GK5Irqi2LbPs>
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: Tue, 20 Nov 2018 18:24:56 -0000

Yes, just as in TCP, the timer is not used to retransmit any data determined lost by fast retransmit.

In the "Loss Detection" section it says:
"If a packet is lost, the QUIC transport needs to recover from that loss, such as by retransmitting the data, sending an updated frame, or abandoning the frame. For more information, see Section 13.2 of {{QUIC-TRANSPORT}}."

Is there some additional text you'd like?

-- 
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/2009#issuecomment-440380559