Re: [quicwg/base-drafts] What packet information to track and send (#1939)

ianswett <notifications@github.com> Sat, 03 November 2018 02:25 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 7C61A130E17 for <quic-issues@ietfa.amsl.com>; Fri, 2 Nov 2018 19:25:06 -0700 (PDT)
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 WDXqLX0KwTIQ for <quic-issues@ietfa.amsl.com>; Fri, 2 Nov 2018 19:25:04 -0700 (PDT)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBE81130E13 for <quic-issues@ietf.org>; Fri, 2 Nov 2018 19:25:04 -0700 (PDT)
Date: Fri, 02 Nov 2018 19:25:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541211904; bh=Q8xxgIxFwWbGET7eDSMBLmTXqgzX8RjEf4N4E9JTrik=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XOSGA6ms2YJpNBi1ej+PlgwqBXihq6r+46BNFeFojpqLGxI2c3I1hcqol0WH8/rDn jGMEwuNGcSOd92t3pXiJ7GATk3jIkMEgmtNXVDjBYalyF+jKDZYQ/llJWPPuMSXvqZ My+88RF6QPu+F6rkOMB4FMgZ+5UQxVTNon7XXY44=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb2f4788c18b53ff9a05b462fde5b523c9da289a492cf0000000117f4c90092a169ce1665d8f7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1939/review/171313530@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1939@github.com>
References: <quicwg/base-drafts/pull/1939@github.com>
Subject: Re: [quicwg/base-drafts] What packet information to track and send (#1939)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bdd07002b047_366a3f8e9dad45c42275e3"; 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/hvac70uDgVOXQ6SGdnem333tnCA>
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: Sat, 03 Nov 2018 02:25:06 -0000

ianswett commented on this pull request.



> @@ -509,6 +509,57 @@ frames containing them could be lost. In this case, the loss recovery algorithm
 may cause spurious retransmits, but the sender will continue making forward
 progress.
 
+## Tracking Sent Packets {#tracking-sent-packets}
+
+QUIC stores information about every packet sent. It's expected implementations
+will index this per-packet information by packet number and store the
+per-packet fields detailed below for loss recovery and congestion control.
+Additionally, implementations MUST ensure that any retransmittable frames
+being transmitted are tracked in case of loss.
+

Hmm, I am actually trying to say something different here, which is that you need to track frames like Stream frames, so if they're lost, you can decide whether to retransmit the data/etc.

-- 
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/pull/1939#discussion_r230542585