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

Mike Bishop <notifications@github.com> Wed, 05 February 2020 15:03 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 A8D601200EB for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 07:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
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: 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 vrG7N-y4AncZ for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 07:03:55 -0800 (PST)
Received: from out-17.smtp.github.com (out-17.smtp.github.com [192.30.252.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85DA1200DB for <quic-issues@ietf.org>; Wed, 5 Feb 2020 07:03:54 -0800 (PST)
Received: from github-lowworker-292e294.va3-iad.github.net (github-lowworker-292e294.va3-iad.github.net [10.48.102.70]) by smtp.github.com (Postfix) with ESMTP id 1F4566E12E2 for <quic-issues@ietf.org>; Wed, 5 Feb 2020 07:03:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6JW3RQF3ABKLRIVWF4JAF5VEVBNHHCCZUP7U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3423/582449851@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3423@github.com>
References: <quicwg/base-drafts/issues/3423@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FlW2NhLkxh0wYdxkBbuh1JEOIco>
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: 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:
https://github.com/quicwg/base-drafts/issues/3423#issuecomment-582449851