Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495)

Mike Bishop <notifications@github.com> Fri, 29 June 2018 17:23 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 521F6130DDD for <quic-issues@ietfa.amsl.com>; Fri, 29 Jun 2018 10:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 vuuCDvVvhDee for <quic-issues@ietfa.amsl.com>; Fri, 29 Jun 2018 10:23:33 -0700 (PDT)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AA88130DCC for <quic-issues@ietf.org>; Fri, 29 Jun 2018 10:23:33 -0700 (PDT)
Date: Fri, 29 Jun 2018 10:23:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530293012; bh=Uyv8kMiUME455MtBZEkFo+oQZQzr3CO2OiaF5Lv4sos=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mUvdeM0DFYivFVX0TN3Kew3oZKnH2D8bD32jWxhnEx+8IIwN44n92qzpHvpCK5J67 WsjNS6F2vouv0hposZCPagCp5TITDG70I8nZERGFgMeypJK31didF6Xv8KAtNTAYh3 oQi2MykW6Ie+NPJmuWPWmLdzLoo6dzT5sA+rklk0=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abaa0975983f8759e32cd2613ac47aad8e1b6e9a8692cf00000001174e2d1492a169ce1412cb45@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1495/401420026@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1495@github.com>
References: <quicwg/base-drafts/issues/1495@github.com>
Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b366b142d038_13d53fdc118a0f8465852"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/qgIhbVXS-dmJgdaQ3XQFziTK1vs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 29 Jun 2018 17:23:40 -0000

One more scenario is load balancer key rotation.  We've already sketched the possible scheme where the CID includes a key phase indicator and the CID itself is some encrypted payload.  At whatever point the key identifier wraps (every key change, if it's a single bit), you need to bulk purge all CIDs issued under the soon-to-be-removed key.

Probably largely irrelevant for short-lived connections, but long-lived connections could easily run afoul of this.

-- 
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/1495#issuecomment-401420026