Re: [quicwg/base-drafts] active_connection_id_limit is unknown for 0-RTT (#3423)

Mike Bishop <> Wed, 05 February 2020 21:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2012612083A for <>; Wed, 5 Feb 2020 13:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oRN0NuNaoFVy for <>; Wed, 5 Feb 2020 13:13:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9412812011A for <>; Wed, 5 Feb 2020 13:13:52 -0800 (PST)
Date: Wed, 05 Feb 2020 13:13:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580937231; bh=v1tq3ZNAWuiD4pSZun24CS+Oy04yTOtJ8Ztr93vV4oQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lAac4ltxHH//IRgGGM/ME1zJgNEgyU8W4PiwT0ftr+pV/ShAK7yGTkEVXnf3iOfnH YQF9qgWMpcNmvfTiQOsHsDAXdLBH4VZB8SsfrbwiL8cjhfoO2i5nRrhmJuuzCvrUGj CT1/6VWEJXW9AJEv66hxRg3u7VXKM61bELvn4+Ps=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3423/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] active_connection_id_limit is unknown for 0-RTT (#3423)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3b300f94815_76e03f88c7ecd9686322c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Feb 2020 21:13:54 -0000

Over supper, @marten-seemann wanted to know _why_ a client would include a new connection ID in its 0-RTT packets.  The answer is that the client's handshake CID has no associated SRT.  If the client wants the ability to send stateless resets, it might very well put NCID(N=1, RPT=1) in its 0-RTT flight.  The server will retire the handshake connection ID in 0.5-RTT and begin using the CID with an associated token.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: