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

Mike Bishop <> Wed, 05 February 2020 15:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A8D601200EB for <>; Wed, 5 Feb 2020 07:03:57 -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 vrG7N-y4AncZ for <>; Wed, 5 Feb 2020 07:03:55 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E85DA1200DB for <>; Wed, 5 Feb 2020 07:03:54 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1F4566E12E2 for <>; Wed, 5 Feb 2020 07:03:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580915034; bh=LYwyhfuIrs2i8BMgjNF2LJjguNYrCXpXfK7h0Nd714A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vyTVgmHxiF6XSxhn+nMXXs8VHLHX/B45q6K0D3P85qVIdVfXQNAjqovGXdOnqv9T5 IR/bIqc3O3J7OpNMQUqGCW7kvflz5Ck85ZmhXaHPyIPmi0Oe8u2Ou/BqA++8AZaGy9 HJxt6h4MknDumkrzt1epcri3cBlwBeGcQS/aDOFo=
Date: Wed, 05 Feb 2020 07:03:54 -0800
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_5e3ad95a102b4_645f3fcbf08cd95c154955"; 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 15:03:58 -0000

Post-discussion and having re-read, I believe the current text covers this for NEW_CONNECTION_ID:

- The client has already issued one CID during the handshake, which might be zero-length
- Sending NEW_CONNECTION_ID is forbidden if you are using zero-length CIDs; receipt of one is a protocol violation
- The default value of `active_connection_id` applies until the server's value is received, which is two if the client is using non-zero-length CIDs
- Exceeding the limit is a protocol violation

It also covers it for RETIRE_CONNECTION_ID:
- The client has exactly one CID for the server during 0-RTT
- It is a protocol violation for RETIRE_CONNECTION_ID to retire the CID used by the containing packet

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