IETF Logo Mail Archive

Re: [quicwg/base-drafts] Forced connection ID retirement (#3420)

Kazuho Oku <notifications@github.com> Wed, 05 February 2020 13:08 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 A8F0212080A for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 05:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 G5M9ChFPG4PQ for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 05:08:58 -0800 (PST)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 047AD120811 for <quic-issues@ietf.org>; Wed, 5 Feb 2020 05:08:56 -0800 (PST)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [10.52.16.66]) by smtp.github.com (Postfix) with ESMTP id D3FC2A054E for <quic-issues@ietf.org>; Wed, 5 Feb 2020 05:08:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580908134; bh=F+DtaU9wsYA2d2PFdR+L9iHkduwNbmBcNR+9MgOyr0Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gfi4Ha+o746blQxzqd7qnOaykskJy1rQQjOHaKRYaevvt1OeciysVQwT9dleMHsEr sd5bmt6M0S7mX8vC138KNsoO4j+gCMVnjTcrDGnk2JQaSTKC5Sa6ckd3FUMtC7iQ/1 1pZYlqFdzGmM79ao+ePiJHFmU93QwY8/R/CA//kM=
Date: Wed, 05 Feb 2020 05:08:54 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY5SB6MBNRK7F4FDSF4I7YONEVBNHHCCZOS7A@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3420/582399060@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3420@github.com>
References: <quicwg/base-drafts/issues/3420@github.com>
Subject: Re: [quicwg/base-drafts] Forced connection ID retirement (#3420)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3abe66c5552_6d763f8bf14cd968353427"; 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/IkFLdgOISEgEwzdwk5CYooIY0ps>
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, 05 Feb 2020 13:09:00 -0000

@martinthomson 
> More to the point, this design assumes things about the nature of connection IDs and routing infrastructure that imply a coupling between path and endpoint state.

I'm not sure if I follow what you state here.

Much like a TLS server having a master key that encrypts TLS session tickets, a server might have a master key that is used for encrypting all the CIDs, and it rotates that key periodically. In such a design (which I'd assume to be pretty normal), there is nothing related to paths.

-- 
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/3420#issuecomment-582399060

v2.23.0 | Report a Bug | By Email