Re: [quicwg/base-drafts] MAX_KEY_UPDATES frame (yet another proposal to solve the key retirement problem) (#2504)

Kazuho Oku <notifications@github.com> Wed, 08 May 2019 06:52 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 20A7E120006 for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 23:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.918
X-Spam-Level:
X-Spam-Status: No, score=-6.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 6I6cKFPdlqvz for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 23:52:42 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E5AC12014A for <quic-issues@ietf.org>; Tue, 7 May 2019 23:52:42 -0700 (PDT)
Date: Tue, 07 May 2019 23:52:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557298361; bh=UhtF+hhjYw3d+mOvMHVywu/yverOyqV+E8G9bA9GnSY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VEyuTZwe59ZYf5HXbe5dZ3uxDesFEBfOUm8AmTOAWbOhmts7XYq1W8AqrhA1Ddclv rRV1lwwDPbKecgZet2wt5MTO5kVBdwEkFjdHpzSG85Mr03bARchwKBp8wE8ngbXuwa FnDGuPDaFnTqqRaGAB3A++O6q2uYvG1Hwaazm3nk=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2Y5UZWZ3HEBIQP7PN236XTTEVBNHHBR44N5M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2504/c490370529@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2504@github.com>
References: <quicwg/base-drafts/pull/2504@github.com>
Subject: Re: [quicwg/base-drafts] MAX_KEY_UPDATES frame (yet another proposal to solve the key retirement problem) (#2504)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd27cb932970_8603fb1fe0cd95c3914ab"; 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/BEr4sESqZFOGimSFcHrzXxV4feI>
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: Wed, 08 May 2019 06:52:44 -0000

@martinthomson I'm personally fine with that, assuming that we are allowed to close alternative proposals when the person that opened the PR prefers something other that has not yet gained consensus.

-- 
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/pull/2504#issuecomment-490370529