Re: [quicwg/base-drafts] Add Advice and Rules for CONN_CLOSE in Initial and Handshake (#1786)

ianswett <> Thu, 27 September 2018 20:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3911F130F2F for <>; Thu, 27 Sep 2018 13:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.455
X-Spam-Status: No, score=-8.455 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DH54PgRmoMgz for <>; Thu, 27 Sep 2018 13:20:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 70AD3130F1C for <>; Thu, 27 Sep 2018 13:20:09 -0700 (PDT)
Date: Thu, 27 Sep 2018 13:20:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1538079608; bh=zZUA0FvcNXq6SGmD2xuGc+yAKUnZEAJL0rBCAwOb1Yo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VPtPM8ZzhmoL9DiTbKtmJoRrDZFhCiVPPF31DHPNvwV9dMatbdlcLhhwGUmcT2lAc B59ytSLxgBSyDjVzBHrZT6tAl6FBDsqz3HMIlyndr6ahuK6JDkI/pqD/jIhF5XozJR I7Z18WU+Bp2XUajefzG2seYMs3pDyhWyJpbZEgFs=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1786/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Add Advice and Rules for CONN_CLOSE in Initial and Handshake (#1786)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bad3b789378a_6cdc3fa7390d45c4203087"; 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
Archived-At: <>
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: Thu, 27 Sep 2018 20:20:11 -0000

I think this comes down to whether we require support implicit ACK of Initial packets.  If we do, we can close some of these holes.  If we don't, I can't see how to close these holes, since you need to keep ACKing the peer's Initial packets because you can't guarantee they have received previous ACKs and there's no other way to ACK those packets.

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