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

Nick Banks <notifications@github.com> Thu, 23 May 2019 08:48 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 D1014120196 for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 01:48:31 -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 S4AcGHmWORpz for <quic-issues@ietfa.amsl.com>; Thu, 23 May 2019 01:48:30 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 008AC120019 for <quic-issues@ietf.org>; Thu, 23 May 2019 01:48:29 -0700 (PDT)
Date: Thu, 23 May 2019 01:48:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558601308; bh=Z+0c9Fv++JkTkA57/UoqfxOuaKqHYW4JGwxl21BWG50=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bQv/PgTgjnT2SaRxrf8bX2ch2H1DNCn4FKFMH1lz/8hLUZcaau4dV4bK5p++H9y3E DxMzK1ARINJqiv7o85Zqww0Prp4vghb67ZpxwteyZe9b1cxC1n9orvZu2/pKUjBTLh h9XT1I665fQ/h2kcLTbWtRQyabE2IkIKMUhjmS4M=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4GXJNEQMRNALXDRFF26OINZEVBNHHBUAUCHA@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/495126302@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_5ce65e5cd97f0_76003fc2dc2cd95c1715c4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/bZfLtLIDagvw6707ujcab769shE>
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 08:48:40 -0000

After talking to a few folks, I'm now leaning towards the following solution:

Update NEW_CONN_ID frame to have two frame types (or we can add a new, separate frame) where the second frame type indicates the presence of an additional field: `RetireSequenceNumber` (we can bike shed the name). This new field indicates the sequence number of a CID that is being replaced by this new CID (which has a new sequence number too).

The sender sends this frame for any/all outstanding, non-retired CIDs that is needs to replace. The receiver is expected to quickly, if not immediately respond with a RETIRE_CONN_ID for all the CIDs that the sender is replacing. Once the NEW_CONN_ID frame is ACKed the sender may drop all the retired CIDs from it's routing table after some time (3 RTT?) even if the peer hasn't retired them; OR it can send a HTTP goaway.

One note on the CID flow control: Even if the maximum number of CIDs have been given to the peer, an endpoint is allowed to retire one or all of them with this NEW_CONN_ID frame, and the peer is expected to accept these new CIDs; since they are replacing the old ones.

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