IETF Logo Mail Archive

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

Kazuho Oku <notifications@github.com> Sat, 23 March 2019 08:46 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 B264812796C for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 01:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 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_28=1.404, 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 Npxmdr2-Pa13 for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 01:46:49 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F3AA127985 for <quic-issues@ietf.org>; Sat, 23 Mar 2019 01:46:48 -0700 (PDT)
Date: Sat, 23 Mar 2019 01:46:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553330807; bh=6DyNN9mmdglWxJXXQ83A/MdPk4ah6AvL7US9rRO9wUI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j6/+G2cRzOsnVn3RHdBic7B3Tofl6g9vQS21eVVN+Ev4lLREW8xoX+EEZuGRy5TpH hy/lSIQ7Ph7lzb+YDmlvNK1cFOQ29MManvGnXdh0e3uINBFQJPi1nosHSJMucIusUh byWIRj7TuLV33qA4mb6Ixz9sGgx4hEGQt5b+w4cE=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4bce4afe5d8aff39eb8acd55e25ba944bb73ce8992cf0000000118adb47792a169ce1943f1d8@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/475852470@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_5c95f27736a06_5d873fc3258d45b414013e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/FY3f8W78pstfgcsKrpOK_RMw_1c>
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: Sat, 23 Mar 2019 08:46:51 -0000

I agree with the principle of throwing Initial keys ASAP. Another strategy that can be employed by the server to avoid the issue is send CONNECTION_CLOSE in Initial packets, but continue waiting for Handshake packets until it discards the connection. When it receives a Handshake packet (that successfully authenticates), it sends a CONNECTION_CLOSE frame in Handshake packet. The approach works because a client is required to send an empty Handshake packet even if there's no data to be sent.

-- 
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-475852470

v2.23.0 | Report a Bug | By Email