Re: [quicwg/base-drafts] Discard 0-RTT packet state when rejected (#2300)
Martin Thomson <notifications@github.com> Mon, 07 January 2019 00:11 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 C845A1310BE for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 16:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 rKJaGfZUzU5Q for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 16:11:15 -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 D9651131025 for <quic-issues@ietf.org>; Sun, 6 Jan 2019 16:11:14 -0800 (PST)
Date: Sun, 06 Jan 2019 16:11:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546819874; bh=wz6nO3KSAbnjlqizjQ72QSvVh5EuPgnt5hVYzfTRM3E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RjYiuPrFwTjuRbFqaFSX4/dINUqNqpeXxpQCMFSlJ3997+bgBvXhJBS8yALqRv2AI h9YZTbay41TivheIXi2aktDuFxBKpBQgDC4ZkRC0huOjH/yl+pT9JldpO76+qFv3m5 xlsI1rju+0pXz8sIE3CSH9I6baZHN/0vObmLwI3I=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abeee14842073a2f3a30e52145b21cb022fed6971592cf00000001184a5b2292a169ce179f005f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2300/review/189651688@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2300@github.com>
References: <quicwg/base-drafts/pull/2300@github.com>
Subject: Re: [quicwg/base-drafts] Discard 0-RTT packet state when rejected (#2300)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3299227d04_681e3fa9d7ad45c4752312"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/wF2qQlQaMk3R8yqFBOqWVZ57kdo>
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, 07 Jan 2019 00:11:17 -0000
martinthomson commented on this pull request. Good changes, some editorial feedback though. > @@ -1001,12 +1001,21 @@ after idle periods, such as those proposed for TCP in {{?RFC7661}}. ## Discarding Packet Number Space State -When keys for an packet number space are discarded, any packets sent with those -keys are removed from the count of bytes in flight. No loss events will occur -any in-flight packets from that space, as a result of discarding loss recovery -state (see {{discard-initial}}). Note that it is expected that keys are -discarded after those packets would be declared lost, but Initial secrets are -destroyed earlier. +When keys for an packet number space are discarded, any in-flight packets +sent with those keys are removed from the count of bytes in flight. Loss +recovery state is also discarded, so no loss events will occur for any +in-flight packets from that space(see {{discard-initial}}). Note that it is +expected that keys are discarded after those packets would be declared lost, +but Initial secrets are destroyed earlier. + +## Discarding 0-RTT packet state I wouldn't bother with the section heading here. > @@ -1001,12 +1001,21 @@ after idle periods, such as those proposed for TCP in {{?RFC7661}}. ## Discarding Packet Number Space State -When keys for an packet number space are discarded, any packets sent with those -keys are removed from the count of bytes in flight. No loss events will occur -any in-flight packets from that space, as a result of discarding loss recovery -state (see {{discard-initial}}). Note that it is expected that keys are -discarded after those packets would be declared lost, but Initial secrets are -destroyed earlier. +When keys for an packet number space are discarded, any in-flight packets +sent with those keys are removed from the count of bytes in flight. Loss +recovery state is also discarded, so no loss events will occur for any +in-flight packets from that space(see {{discard-initial}}). Note that it is ```suggestion in-flight packets from that space (see {{discard-initial}}). Note that it is ``` (Oh good, GitHub fixed the leading space problem.) > -When keys for an packet number space are discarded, any packets sent with those -keys are removed from the count of bytes in flight. No loss events will occur -any in-flight packets from that space, as a result of discarding loss recovery -state (see {{discard-initial}}). Note that it is expected that keys are -discarded after those packets would be declared lost, but Initial secrets are -destroyed earlier. +When keys for an packet number space are discarded, any in-flight packets +sent with those keys are removed from the count of bytes in flight. Loss +recovery state is also discarded, so no loss events will occur for any +in-flight packets from that space(see {{discard-initial}}). Note that it is +expected that keys are discarded after those packets would be declared lost, +but Initial secrets are destroyed earlier. + +## Discarding 0-RTT packet state + +When 0-RTT is rejected, all in-flight 0-RTT packets still are removed from ```suggestion When 0-RTT is rejected, all in-flight 0-RTT packets are removed from ``` > -any in-flight packets from that space, as a result of discarding loss recovery -state (see {{discard-initial}}). Note that it is expected that keys are -discarded after those packets would be declared lost, but Initial secrets are -destroyed earlier. +When keys for an packet number space are discarded, any in-flight packets +sent with those keys are removed from the count of bytes in flight. Loss +recovery state is also discarded, so no loss events will occur for any +in-flight packets from that space(see {{discard-initial}}). Note that it is +expected that keys are discarded after those packets would be declared lost, +but Initial secrets are destroyed earlier. + +## Discarding 0-RTT packet state + +When 0-RTT is rejected, all in-flight 0-RTT packets still are removed from +the count of bytes in flight. Loss recovery state is also discarded, so no +loss events will occur for any in-flight 0-RTT packets. If a server does not The sentence starting "Loss recovery state" is duplicative of the previous section/paragraph, so can go. > -destroyed earlier. +When keys for an packet number space are discarded, any in-flight packets +sent with those keys are removed from the count of bytes in flight. Loss +recovery state is also discarded, so no loss events will occur for any +in-flight packets from that space(see {{discard-initial}}). Note that it is +expected that keys are discarded after those packets would be declared lost, +but Initial secrets are destroyed earlier. + +## Discarding 0-RTT packet state + +When 0-RTT is rejected, all in-flight 0-RTT packets still are removed from +the count of bytes in flight. Loss recovery state is also discarded, so no +loss events will occur for any in-flight 0-RTT packets. If a server does not +buffer out-of-order packets and accepts 0-RTT, there is a chance of declaring +0-RTT packets lost that were actually discarded by the server, but this is +expected to be infrequent. The out-of-order sentence probably needs to be its own paragraph - because it's talking about accepting 0-RTT (as opposed to rejecting it). Not sure how that affects the flow of the section though. -- 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/2300#pullrequestreview-189651688
- [quicwg/base-drafts] Discard 0-RTT packet state w… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Martin Thomson
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Martin Thomson
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Kazuho Oku
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Martin Thomson
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Kazuho Oku
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… Martin Thomson
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… MikkelFJ
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett
- Re: [quicwg/base-drafts] Discard 0-RTT packet sta… ianswett