Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468)

Kazuho Oku <notifications@github.com> Fri, 22 June 2018 03:03 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 BDAC4130DD2 for <quic-issues@ietfa.amsl.com>; Thu, 21 Jun 2018 20:03:32 -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 6j0TXmlKYbuh for <quic-issues@ietfa.amsl.com>; Thu, 21 Jun 2018 20:03:31 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EACF5130DD1 for <quic-issues@ietf.org>; Thu, 21 Jun 2018 20:03:30 -0700 (PDT)
Date: Thu, 21 Jun 2018 20:03:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529636609; bh=rGeykfvNYU1myz+GxSjELjTIDzl7JJ4GDnrSm+0brI0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XD7ls8tUK7pZNqzpSZ6YfoaPWqMwl+Yjfcxkrtk6iXCKh52zsYnALwHgi1UxrqtDs yo3ZLVdiB5gju5BTDzbZ3eCFJaAcA9jDZZoWXC7ucaAokqilZL5bSo49cXOZpOab+D yqVO/+irfpvdV6oNML0VL/R36O1Hy2O573Xa8ra0=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2176bb3b99a864e173c73c798172d85bedb0bc8b92cf000000011744290192a169ce13f33b45@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1468/399306505@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1468@github.com>
References: <quicwg/base-drafts/issues/1468@github.com>
Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c6701e4865_39802aded2056f50207646"; 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/9dNscS876jo5wdzQkZ8XMBO5mkI>
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, 22 Jun 2018 03:03:33 -0000

Am I correct in assuming that we would have a sequence number in this proposed approach?

I think that we need it, otherwise an eternal ping-pong might happen. Of course we can prevent eternal ping-pong from happening by having a `is_pong` flag. But I would assume that it would be more straightforward (and descriptive) to have a sequence number.

-- 
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/1468#issuecomment-399306505