IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clients cannot abandon Initial packets while server can still send initial close (#2541)

ianswett <notifications@github.com> Sun, 24 March 2019 01:03 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 0967B130EDE for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 18:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 W7l9BmDoooC0 for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 18:03:24 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D43B130EFB for <quic-issues@ietf.org>; Sat, 23 Mar 2019 18:03:24 -0700 (PDT)
Date: Sat, 23 Mar 2019 18:03:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553389403; bh=2PvPUNbUZ+5eMWYPNyditbfpmA99qimLy1b5Rcyf+4w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NwLDSf/RJTIJFx/Qqa1I+JLG3USO/XLd8n+mmDO23ux1PiUGYTrpjebU+RhBZhZoB t1Pnf8gnUJ37bJmPrHp+RlWy9Dgv6qjao4DXSptfP1JKeqhmq3n1JE14fIIFtjxQ5i molZ8iyoZyos89b3ZeXX0fGPcG79tnOSu4zHkn34=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5f3a4e03672d1e8cd989cf7fec1a0aa9e3a146bb92cf0000000118ae995b92a169ce1943f1d8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2541/475918359@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2541@github.com>
References: <quicwg/base-drafts/issues/2541@github.com>
Subject: Re: [quicwg/base-drafts] Clients cannot abandon Initial packets while server can still send initial close (#2541)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c96d75b1b836_23073fe5b68d45c47112f7"; 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/eHPl7fzUBrIjS-3mLhI0ievMHRE>
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: Sun, 24 Mar 2019 01:03:26 -0000

My understanding is that the KEYS_READY/RETIRE_KEYS/etc(#2214) change is going to change the key discarding dynamics enough that this issue may not longer be a problem?

In particular, I'd expect the client to send RETIRE_KEYS when it first has Handshake keys and the server to send it when it receives a Handshake packet from the client.  That would delay dropping the Initial keys just enough that I believe there should no longer be a confusion about what the highest encryption level the peer will process?

-- 
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/2541#issuecomment-475918359

v2.23.0 | Report a Bug | By Email