Re: [quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)
MikkelFJ <notifications@github.com> Tue, 25 September 2018 06:01 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 E1729131127 for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 23:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, URIBL_BLOCKED=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 3B-ut_I4vsPE for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 23:01:09 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCA5613107E for <quic-issues@ietf.org>; Mon, 24 Sep 2018 23:01:08 -0700 (PDT)
Date: Mon, 24 Sep 2018 23:01:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537855267; bh=bvGZr73DluR3PsFxMLFuUvNB9hpu8wFZAMEQ/dUOx84=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zb04SZaErubl23DlIH2GE/kaGQH4Ud8U9SUAvZzUI4u2z5c8hf5orQsyvmQTFUa9u +vDV6SFGqig2zFMcBA5ab3GLIUuFcJfA6v7n550n9LTSFLGUkTpFBInF/YJWkcBtfc N2EMUvcOO0iid1kgJlC6APzT2Rg3k1MQBKX0sYKM=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3f91150e81d0c25fea22d5ac05c2e2a249243c3a92cf0000000117c1912392a169ce15a89a06@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1795/424217202@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1795@github.com>
References: <quicwg/base-drafts/issues/1795@github.com>
Subject: Re: [quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba9cf23a7998_5ac23f8e740d45c0748836"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/ZlCPEXLkxskJZuHq-rU-RBeFeFo>
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: Tue, 25 Sep 2018 06:01:11 -0000
I'm slightly worried that some ill-advised an endpoint might spam the other endpoint with endless IDs that are being naively stored by the peer instead of retired causing a targeted or involuntary DoS attack. Even if the peer retires the IDs timely, it might not have credits to get rid of them. Of course, defense is to shut down bad behavior, but perhaps it should be considered in an advisory algorithm. -- 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/1795#issuecomment-424217202
- [quicwg/base-drafts] Define a safe algorithm for … Martin Thomson
- Re: [quicwg/base-drafts] Define a safe algorithm … Kazuho Oku
- Re: [quicwg/base-drafts] Define a safe algorithm … MikkelFJ
- Re: [quicwg/base-drafts] Define a safe algorithm … Martin Thomson
- Re: [quicwg/base-drafts] Define a safe algorithm … MikkelFJ
- Re: [quicwg/base-drafts] Define a safe algorithm … Mark Nottingham
- Re: [quicwg/base-drafts] Define a safe algorithm … Martin Thomson