IETF Logo Mail Archive

[quicwg/base-drafts] Exhausting a supply of connection IDs (#1276)

Martin Thomson <notifications@github.com> Mon, 09 April 2018 10:01 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 BAFD8124207 for <quic-issues@ietfa.amsl.com>; Mon, 9 Apr 2018 03:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level:
X-Spam-Status: No, score=-5.392 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 J4CippVFWbN8 for <quic-issues@ietfa.amsl.com>; Mon, 9 Apr 2018 03:01:39 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA6D0126CF6 for <quic-issues@ietf.org>; Mon, 9 Apr 2018 03:01:38 -0700 (PDT)
Date: Mon, 09 Apr 2018 03:01:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1523268098; bh=p6/o/+j9LbwmaGPCgWjkbIFh/wekxA+DJhR4MzJyr3A=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XryRLViF4XbqynMEdqc7jjygGuxL5/kEHBm6+iglYb1TUnp6iaX0iAqZxWgtgPv5c eYQV0ze+7eFh/mr1dxVV3fKdKvtElK8SWDx78hE4rIuguLVWl2Q+3bQrjKbcDO2I9M 7uzRc7Gpt5kCW8Vxr4FWTKC+fD2cA8oHP3WApzZM=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe2fcd2fca59d0607411c52e9730e434e28d1d4ac92cf0000000116e2fc0192a169ce129fe454@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1276@github.com>
Subject: [quicwg/base-drafts] Exhausting a supply of connection IDs (#1276)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5acb3a01f2d7d_e512ad19ba58ed4748fb"; 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/_yYNULpjGLk65InNbI0L_KdBvjI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 09 Apr 2018 10:01:42 -0000

What - if anything - do we want to say about connection migration in the face of a server that provides too few (including 0) connection IDs?  It's a fairly simple trade-off that we can explain.  I suspect that different clients will adopt different policies though.

And, should we provide a means to request more?

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

v2.23.0 | Report a Bug | By Email