Re: [quicwg/base-drafts] simultaneous key update can lead to deadlock (#2214)
Kazuho Oku <notifications@github.com> Thu, 20 December 2018 11:30 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 93BD2130DF7 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 03:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 RJnBVUgXO4Gg for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 03:30:04 -0800 (PST)
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 4670F131055 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 03:30:02 -0800 (PST)
Date: Thu, 20 Dec 2018 03:30:01 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545305401; bh=ddHNg5Ol3yyHxz6D8NAvS25ewVVVi4YpOvofZ3UZem8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hfN+a/es4KHvi3oDSzbDlXqu6ljexgwxVhSo3tsmmsH1lB3HpkO+HEk55wrXx+4pr LJNWNzX7tKGyT7j2Udis916ICrPpAQS6Pg0R3j+Qy2OiusRsWWzEfQAmEndZ5n+oGO z97jwVRwdSLUo5+MxzICG5AtyiFA5L/R7N7I6qek=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab60d974ea9228a7c4fb819d5dcdf2ac9208a992e692cf0000000118333f3992a169ce176cb14d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2214/448965316@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2214@github.com>
References: <quicwg/base-drafts/issues/2214@github.com>
Subject: Re: [quicwg/base-drafts] simultaneous key update can lead to deadlock (#2214)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1b7d39653e4_23033f85b34d45b81456bc"; 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/dgOihltXjxa1K6Z5Uyp7IDm2aNg>
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: Thu, 20 Dec 2018 11:30:06 -0000
FWIW, I had assumed that we agreed that an endpoint is required to have two generation counters, one for the send key and the other for the receive key, and to update it's send key either when it wants to, or when the receive key's generation counter becomes greater than that of the send key. However, I do not see that specified, and I agree that we have an issue. -- 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/2214#issuecomment-448965316
- [quicwg/base-drafts] simultaneous key update can … Marten Seemann
- Re: [quicwg/base-drafts] simultaneous key update … Kazuho Oku
- Re: [quicwg/base-drafts] simultaneous key update … Martin Thomson
- Re: [quicwg/base-drafts] simultaneous key update … Marten Seemann
- Re: [quicwg/base-drafts] simultaneous key update … Martin Thomson
- Re: [quicwg/base-drafts] simultaneous key update … Martin Thomson