IETF Logo Mail Archive

Re: [quicwg/base-drafts] Should retiring all CIDs be an error? (#2101)

janaiyengar <notifications@github.com> Thu, 13 December 2018 03: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 36C8C124D68 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 19:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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] 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 e25GzTXOPmH1 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 19:08:33 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84A9812008A for <quic-issues@ietf.org>; Wed, 12 Dec 2018 19:08:33 -0800 (PST)
Date: Wed, 12 Dec 2018 19:08:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544670512; bh=9wx/bXBiTvK4t8Pa+2QA6c8IS78PQu2BlJU9Cjiz1OY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pZGCE6+3isXqLfX/UGzvKmye2MduVty8Gncw6MUmeSnMJISW0DqGGBvp81d5/wu1/ 9t8iVvemk2g2Dep0n1d/mTDSpUTlRwv9g2KR+ls2AFE6r233liDr6lF5JqQfeHYpaY VSQ3pciyc/9tCHBaZSTLfVt09KjaRSV8Alj+enw0=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf6aeec0fad133d6b5bb067ff426f3a2bf47f536692cf0000000118298f3092a169ce171ddb1f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2101/446827065@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2101@github.com>
References: <quicwg/base-drafts/issues/2101@github.com>
Subject: Re: [quicwg/base-drafts] Should retiring all CIDs be an error? (#2101)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c11cd3063a3e_152e3f9c162d45b433147f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/DLZfkG3wZ-fG7EadV3OQpWoson4>
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, 13 Dec 2018 03:08:35 -0000

I'm with @martinthomson on this one. There are many ways in which an endpoint can shoot itself in the foot, and this is one more.  I'll note that the onus here really is on the peer issuing CIDs.  Retiring is fine if it's the only one that the peer has issued, and it needs to be retired because of a change in the peer's address for example. A peer that doesn't issue new ones ahead of time is responsible.

That said, an endpoint that retires CIDs willy-nilly is simply hurting itself. I wouldn't be opposed to having something in the applicability draft, along with text for when something should be retired.

-- 
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/2101#issuecomment-446827065

v2.23.0 | Report a Bug | By Email