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

ianswett <notifications@github.com> Tue, 11 June 2019 02:28 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 29DA4120041 for <quic-issues@ietfa.amsl.com>; Mon, 10 Jun 2019 19:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Level:
X-Spam-Status: No, score=-6.391 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_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, 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 8V3mu0NWJhwy for <quic-issues@ietfa.amsl.com>; Mon, 10 Jun 2019 19:28:36 -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 16223120026 for <quic-issues@ietf.org>; Mon, 10 Jun 2019 19:28:36 -0700 (PDT)
Date: Mon, 10 Jun 2019 19:28:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560220114; bh=5hhs/h8nxJxmk7HehyMMEWqmTDND46OMNpPUOURm5OA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SJjNZmA9xS1awmXMgcF0LBFRjLIlZrFDn4zPkw5kh/XA1Wl2HsXzjg0DkVoESILaf oxvYGRVJCVVwcsx87Y0J6zd36gjlh0ZhGYvMamymkcAc2+JCZ0UKudC2YjJe8o0hsN kF/ekw4eQFENaiTxUNf7Qwi0X8QhOCN+sPdbIaOQ=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4ZGYFJLRBA73MVWMN3BRCFFEVBNHHBUAUCHA@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/500662343@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_5cff11d262f1b_76693fc302acd960103985"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/uRaPtq7zuynDRQylB3NYn05Ft4o>
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, 11 Jun 2019 02:28:38 -0000

I'm fine with the "please retire" semantics, but wanted to point out an existing case in the QUIC specs we say you must retire something in a similar circumstance.  I hate timers, so I suspect my implementation will do that even if the spec doesn't require it, because I believe it's more straightforward to implement.

If you supply a CID with sequence number X and I've specified that I'm only going to store Y sequence numbers via active_connection_id_limit, can you assume the peer is unlikely/unwilling to use CIDs with sequence number < X-Y(modulo reordering).  That would be true for my implementation, but possibly it's also related to the 3RTO issue?

-- 
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-500662343