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

ianswett <> Fri, 28 September 2018 01:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 356AE130DCA for <>; Thu, 27 Sep 2018 18:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Status: No, score=-8.456 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] 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 hX5YXbtwnLRf for <>; Thu, 27 Sep 2018 18:24:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8F095126F72 for <>; Thu, 27 Sep 2018 18:24:56 -0700 (PDT)
Date: Thu, 27 Sep 2018 18:24:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1538097895; bh=Dkz0HD0kBJ6/DLsXI1iG1yHu9uIwGP6v3Api7AuAfhY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ug+vR7KD8HPktSiy0+gYmWuJ4YT4tF+hnQvuQtd9dbm1+4EyTqsKhbiozfGa3ah+j KfzSUc8p/Dnr0cd/0gp+aIuqUUzhar21Q9715qx+oq+6SZLqyMeOv3J6aH/xLGqmqz JGhPAITp9RlCqIxhzcatFjYiTPXoElcZr4ISXzrs=
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_5bad82e7bb3aa_29e73faee78d45c040894c"; 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: Fri, 28 Sep 2018 01:24:58 -0000

If the Initial arrives with frame types that aren't valid in the Initial, you're going to have to decide how to handle it.  This could easily happen after you receive a valid frame.  But even if the STREAM frame is the only thing in the invalid Initial, it's effect would be to close the connection, correct?

By reading your 3 items, it seems like at some point we should mostly ignore Initial packets, but send an ACK?

I think the sender text is fairly straightforward, but we have 3 options I'm aware of on the receiver side:
1) Require implicit ACKs.
2) Instruct the receiver to ACK Initial encryption after receiving Handshake, but not process them.
3) Decide we don't care about injection attacks.

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