IETF Logo Mail Archive

[quicwg/base-drafts] Clarify In-flight (#2200)

ianswett <notifications@github.com> Mon, 17 December 2018 16:47 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 D8C36130EBA for <quic-issues@ietfa.amsl.com>; Mon, 17 Dec 2018 08:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level:
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 dK06eUS_toiA for <quic-issues@ietfa.amsl.com>; Mon, 17 Dec 2018 08:47:25 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2499A127332 for <quic-issues@ietf.org>; Mon, 17 Dec 2018 08:47:25 -0800 (PST)
Date: Mon, 17 Dec 2018 08:47:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545065244; bh=Zp+GZX0WmHNkvtCl827BN2UxEYYmrVzNBPTRN5Eknhg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bmtgHJUY3VhVp3Zs80cbr8Vehha7eyorwPurj1LtbOU5vdXmHACrAS76kP22z2o7v EAWkl/C2ln/M4IAmi+kBrLb3WLyqzEs0yNSQgEXWhN1G2KMzwfb3culHlA2euNH7KO /1id7LPZD8fw0va1NoJqJJmzVXGClG784AWU+71w=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7c5ff894a20f01fa75f4c95af1b1a068a9d50fbb92cf00000001182f951c92a169ce175a6070@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2200@github.com>
Subject: [quicwg/base-drafts] Clarify In-flight (#2200)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c17d31c2abc8_1ce83f86cccd45b41841c8"; 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/MbzvzvOfOS_ypEnZmlhbiCjRpIk>
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: Mon, 17 Dec 2018 16:47:27 -0000

I'm not sure this is necessary, but I've had at least 2 people be unsure about whether a packet is still in flight if all the stream data in it is cancelled, so maybe it's worth stating this explicitly?
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/2200

-- Commit Summary --

  * Clarify In-flight

-- File Changes --

    M draft-ietf-quic-recovery.md (3)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/2200.patch
https://github.com/quicwg/base-drafts/pull/2200.diff

-- 
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/2200

v2.23.0 | Report a Bug | By Email