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

martinduke <> Fri, 28 September 2018 00:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E98D312F295 for <>; Thu, 27 Sep 2018 17:37:11 -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=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 668ZzFWcykaT for <>; Thu, 27 Sep 2018 17:37:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CA54C126F72 for <>; Thu, 27 Sep 2018 17:37:00 -0700 (PDT)
Date: Thu, 27 Sep 2018 17:36:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1538095019; bh=0FkfhBnpbd8QsyVf27AxBCbmX1bfeSQlZlSYPs47dDQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BJbBUt5b6EMGRlEDR1tVGcrrSECRD0H+h+5d4MKOV2zeBf4W4GaTPsprI3jWUTl0U n1BxxhMtFOV19WHhA7XQCs3ljzJjNzbXDexan1CEwbymsZV6Qy6tJ3lBpA4dY3a2uV tckHKTxRmV89qluIAhWbIRZW4BenSXght7dr2fo4=
From: martinduke <>
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_5bad77ab76164_7b573fbca1ed45c017461e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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 00:37:12 -0000

> Mostly OK, but you might have already processed some frames when you hit the CONNECTION_CLOSE. We'd need to address that.

Yes, there are some unpleasant corner cases there.

> Send with the keys you know that your peer has. That is, if you have received X, send with X. You might already be sending with X+1, but it isn't always guaranteed that your peer has X+1. For instance, the server might be sending Handshake packets, but the client might not have processed all of the Initial yet.

This doesn't work with the second item. If I've received context X while having sent X+1, this rule would force me to send CONN_CLOSE in X. If X+1 arrives first, the receiver would ignore X.

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