IETF Logo Mail Archive

Re: [quicwg/base-drafts] Does rejecting 0-RTT data prohibit ACKing 0-RTT data? (#2840)

ianswett <notifications@github.com> Mon, 24 June 2019 23:00 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 AA82512021D for <quic-issues@ietfa.amsl.com>; Mon, 24 Jun 2019 16:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.455
X-Spam-Level:
X-Spam-Status: No, score=-6.455 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 jHASHs7GtSMH for <quic-issues@ietfa.amsl.com>; Mon, 24 Jun 2019 16:00:52 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EEA312006D for <quic-issues@ietf.org>; Mon, 24 Jun 2019 16:00:52 -0700 (PDT)
Date: Mon, 24 Jun 2019 16:00:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561417251; bh=06ieqK2a9SVksdf9M/54aL6iclHiWFBAm/wungkHNXQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nRuG38ERHn4kl1lJBZmUmAFpzNDNhje5f5dbKfOsFvQrMMZlOQGgJ11PlHRq0NKYR NWu8K2l3/ycwDokwKUqVgCSGNuYi9yAqAkCiO8hhUlQaIVrh8LoEkedQvOWOYyUUzj iQO8jyJPeAtefqSiltp931x4KcY2Kb+KvH7T/yUk=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4RBF5IMM2DFYHQVY53D2EKHEVBNHHBW3H6CY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2840/505212604@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2840@github.com>
References: <quicwg/base-drafts/issues/2840@github.com>
Subject: Re: [quicwg/base-drafts] Does rejecting 0-RTT data prohibit ACKing 0-RTT data? (#2840)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d11562374c85_225f3fb50f4cd96c286325"; 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/4ZkHyNO2aQXPnL46P9fsCmHGpDk>
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, 24 Jun 2019 23:00:55 -0000

Throughout transport, there is the idea that you MUST not acknowledge packets you can't fully process, so this should be against the spec.  But it may be worth noting explicitly, probably in transport.

-- 
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/2840#issuecomment-505212604

v2.40.4 | Report a Bug | By Email | System Status