From nobody Thu Feb 27 17:56:18 2020 Return-Path: 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 159E73A0BE6 for ; Thu, 27 Feb 2020 17:56:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.1 X-Spam-Level: X-Spam-Status: No, score=-3.1 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_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 u91iB4IfCP1Y for ; Thu, 27 Feb 2020 17:56:16 -0800 (PST) Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF78C3A0BE3 for ; Thu, 27 Feb 2020 17:56:15 -0800 (PST) Received: from github-lowworker-943b171.ac4-iad.github.net (github-lowworker-943b171.ac4-iad.github.net [10.52.22.59]) by smtp.github.com (Postfix) with ESMTP id D7FB4282817 for ; Thu, 27 Feb 2020 17:56:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582854974; bh=cTQAMfpyjhOArG6sKWfujo5rsoTZrsc1G46jq5p1qmM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F2hFmDku+Bl+qzAJD5RmDRAw2EMd+2xaSzFgqheU5aBlUb2MwH3RfXprFAqGi5NyS u9+y2XRLUDx6Q3Aa93/fRgNGurcrh3gC79rCa9MEZ/aAhwNnOJ8GT/I6yVzy8KVOuJ VD3S0WoWmSQAy2C21hIvY8FAvRFEsQLAHfXtVC6U= Date: Thu, 27 Feb 2020 17:56:14 -0800 From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify which packet losses may be ignored (#3450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e58733ec82c2_6cca3f8910ccd96c193157"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2020 01:56:17 -0000 ----==_mimepart_5e58733ec82c2_6cca3f8910ccd96c193157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -690,12 +690,14 @@ losses or increases in the ECN-CE counter. ## Ignoring Loss of Undecryptable Packets -During the handshake, some packet protection keys might not be -available when a packet arrives. In particular, Handshake and 0-RTT packets -cannot be processed until the Initial packets arrive, and 1-RTT packets -cannot be processed until the handshake completes. Endpoints MAY -ignore the loss of Handshake, 0-RTT, and 1-RTT packets that might arrive before -the peer has packet protection keys to process those packets. +During the handshake, some packet protection keys might not be available when +a packet arrives and the receiver can choose to drop the packet. In particular, +Handshake and 0-RTT packets cannot be processed until the Initial packets +arrive and 1-RTT packets cannot be processed until the handshake completes. +Endpoints MAY ignore the loss of Handshake, 0-RTT, and 1-RTT packets that might +have arrived before the peer has packet protection keys to process those +packets. Endpoints MUST NOT ignore the loss of packets that were sent after +the earliest acknowledged packet in a given packet number space. #3415 makes that extra clear I think. -- 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/3450#discussion_r385471040 ----==_mimepart_5e58733ec82c2_6cca3f8910ccd96c193157 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -690,12 +690,14 @@ losses or increases in the ECN-CE counter.
 
 ## Ignoring Loss of Undecryptable Packets	
 
-During the handshake, some packet protection keys might not be	
-available when a packet arrives. In particular, Handshake and 0-RTT packets	
-cannot be processed until the Initial packets arrive, and 1-RTT packets	
-cannot be processed until the handshake completes.  Endpoints MAY	
-ignore the loss of Handshake, 0-RTT, and 1-RTT packets that might arrive before	
-the peer has packet protection keys to process those packets.	
+During the handshake, some packet protection keys might not be available when
+a packet arrives and the receiver can choose to drop the packet. In particular,
+Handshake and 0-RTT packets cannot be processed until the Initial packets
+arrive and 1-RTT packets cannot be processed until the handshake completes.
+Endpoints MAY ignore the loss of Handshake, 0-RTT, and 1-RTT packets that might
+have arrived before the peer has packet protection keys to process those
+packets. Endpoints MUST NOT ignore the loss of packets that were sent after
+the earliest acknowledged packet in a given packet number space.

#3415 makes that extra clear I think.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

----==_mimepart_5e58733ec82c2_6cca3f8910ccd96c193157--