IETF Logo Mail Archive

[quicwg/base-drafts] Connection ID Garbage Collection (#1729)

Christian Huitema <notifications@github.com> Sun, 09 September 2018 16:57 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 3808112DD85 for <quic-issues@ietfa.amsl.com>; Sun, 9 Sep 2018 09:57:52 -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 CjhANFpaps5W for <quic-issues@ietfa.amsl.com>; Sun, 9 Sep 2018 09:57:50 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3934B1200D7 for <quic-issues@ietf.org>; Sun, 9 Sep 2018 09:57:49 -0700 (PDT)
Date: Sun, 09 Sep 2018 09:57:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536512268; bh=LxVBY53MDdC1u5AVU8cCOUF/BZF4OKjbBBLNp3iIS2M=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=gc8Yrr2YknvtwCUpYs4gcYKSnZbcRDpI18C+qwS/co/Ai10Mv9JjUxy6AInDOAtLw 3kH92BMP4yf54/eEJbeZnUCtGSX328aiOfUQb6P4cZSmN3Ybu/jRoEE6LuznLPqn+8 t+UG17cJmMbHX60kW8jcLsatvQK7kNsQMlyhzRbk=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab48917e19949d71c270107887911e78c7055f765e92cf0000000117ad130c92a169ce155ca63e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1729@github.com>
Subject: [quicwg/base-drafts] Connection ID Garbage Collection (#1729)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b95510c9a062_127e3fbecc6d45b4144725d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/p8wn_vR-W6EmjXBVSApr2IYPOYs>
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: Sun, 09 Sep 2018 16:57:52 -0000

Nodes use the NEW CONNECTION ID frames to provide peers with lists of connection Ids that can be assigned to new paths during migration. If everything goes well, the probing for the new path succeeds, and the peer receives packet bearing the previously communicated connection ID. But things don't always go well. In some cases, the probes will fail. The node that announced the probed connection ID will not now that it has been "consumed". The node will only be able to free the associated resource at the end of the connection. It will not know that the peer needs new connection ID to replace the one that was previously consumed, and the peer will not be able to undertake another migration.

Should we add some signalling to deal with the problem? Maybe a "CONSUMED CONNECTION ID" frame?

-- 
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/1729

v2.23.0 | Report a Bug | By Email