Re: [quicwg/base-drafts] Retire My Own CID (#2645)

Martin Thomson <notifications@github.com> Thu, 23 May 2019 10:12 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 0E94C120094 for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 03:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level:
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 7UYn_qcYgMeN for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 03:12:15 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 607D6120075 for <quic-issues@ietf.org>; Thu, 23 May 2019 03:12:15 -0700 (PDT)
Date: Thu, 23 May 2019 03:12:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558606334; bh=I2WlYqDEdNsJPMxEVUF7oBCX/FiA5MHbaugkH5MU19s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TPIJ4zsxx3/7chfUZXvvn2epa5WmvEeRNbqU0A9DUGRjWPPv6PC+fcI4W1f268uti nXhY1k0KyKcVrOmTatN0ia6SmlVZisYhKuqSTluhTjSx+P9JtzTG7qjtzPyWY9Duz5 EOeO5CpYTr6/n/cQFBPwlRy7UL2QVVDsgyLHbl7w=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYMJN5TWTHMLNQMX5F26OSH5EVBNHHBUAUCHA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2645/495157258@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2645@github.com>
References: <quicwg/base-drafts/issues/2645@github.com>
Subject: Re: [quicwg/base-drafts] Retire My Own CID (#2645)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce671fe77d62_75a63f82454cd96412896"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/7rIk9FXrEFsmXPd0L6OrEd6vY3o>
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, 23 May 2019 10:12:17 -0000

There is never any guarantee that the connection ID will be replaced.  Coupling them just complicates the design.

The idea that you can provide replacements without blowing the limit is strange.  You are still providing extra connection IDs.

For the case that @nibanks cares about, the low water mark is probably fine because you will want to send the retirement before filling up the active connection ID set.  I think that it is enough to provide a retirement signal and then wait for the peer to retire old ones and replace them on a regular cadence.  Worst case, that means that you have to wait a round trip; but that's not going to be a problem for the RSS scenario Nick described.

-- 
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/2645#issuecomment-495157258