Re: [quicwg/base-drafts] Handling un-ackable packets (#751)

ekr <notifications@github.com> Tue, 29 August 2017 00:42 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 6CA64124207 for <quic-issues@ietfa.amsl.com>; Mon, 28 Aug 2017 17:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.401
X-Spam-Level:
X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 z_fne3Vla6Pt for <quic-issues@ietfa.amsl.com>; Mon, 28 Aug 2017 17:42:12 -0700 (PDT)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D212913238E for <quic-issues@ietf.org>; Mon, 28 Aug 2017 17:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=oDIzMphAHRtSjTuLqSpvUgzj3gY=; b=lNMZVG07nUTLiqpM O327kFpoRXFhshKtsN+Vz3w6tbZVmeD48M6I5sIRy8QXHf9S5L9rYXul6JLj64Xb 0CX95w5KtrIGjAIMgaTYNrZrja+849z9SOwnU57vylFE7excHxuEAsTvJrUQgf6r FlJTm8KNZ5quPTfv4Ugo83doHGg=
Received: by filter0230p1las1.sendgrid.net with SMTP id filter0230p1las1-13271-59A4B862-33 2017-08-29 00:42:10.730462274 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id -sR5jRDgRWaf51N-Fq488A for <quic-issues@ietf.org>; Tue, 29 Aug 2017 00:42:10.665 +0000 (UTC)
Date: Tue, 29 Aug 2017 00:42:10 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4c2eaa8c0c80ec93d43064572843389ddecaea5f92cf0000000115bc7a6292a169ce0f1ba30a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/751/325521474@github.com>
In-Reply-To: <quicwg/base-drafts/issues/751@github.com>
References: <quicwg/base-drafts/issues/751@github.com>
Subject: Re: [quicwg/base-drafts] Handling un-ackable packets (#751)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59a4b8628c9b2_1dbd3f984f9efc389650"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak10tGXIyy4YbRMprtx2NJDxH74N3EIUrsTREk yoJaY0bDG95CsXLqZITMVI2Pi4mn5gnm7j78D60jvBWoaQt3cF3su9PayOrhhQz+W2XxWvEqZQsgGn qnkT9Q3vdStNJQdk+UehQ/X1iUBfmlQ9mmhrx8wmBOj+rjaBiUURSAqxdQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/U-Rh0phF7DS0P93vESy1RHqjbak>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 29 Aug 2017 00:42:13 -0000

Well, it's relatively fine to hold this 0-RTT data b/c you can't decrypt it anyway (modulo potential DoS issues).

The solution I would propose here is that when we update the ACK frame, we allow an empty ACK, and then that can be used for fast retransmission



-- 
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/751#issuecomment-325521474