Re: [quicwg/base-drafts] Connection ID Length changes (#2473)

martinduke <> Fri, 15 February 2019 22:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6727112E036 for <>; Fri, 15 Feb 2019 14:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 XZ50c9fGK38U for <>; Fri, 15 Feb 2019 14:44:06 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52C94131122 for <>; Fri, 15 Feb 2019 14:44:06 -0800 (PST)
Date: Fri, 15 Feb 2019 14:44:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1550270645; bh=Mav9xyqfu8kYpe8AheiH3MxQ05OOZ0baXVgxxleaaHI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y7IGdnFrotrvGsLJ/+Zfb0YR9zhu6hKjUbGmM1QVsrAWAL1rKP+6Qxc+/d2cbAFCD 4jJXDu1v7aZr6wNsHncjue95uBZqV5K+F1w1pAlydsyBlapD0qFUKhHRX/DJhogFyP kLx8TnJfvMVrnGKSsNsHC3qxZXbJA+Px54/jzDlM=
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2473/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Connection ID Length changes (#2473)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6740b5409e8_79593f90258d45c414681b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: Fri, 15 Feb 2019 22:44:09 -0000


> a server can have no more than one connection that uses a zero-length CID, assuming that the CID might be used for a new path (that's the intent of delivering a CID in a NCID frame).

Why not? ZLCID connections are separated by 4-tuple. One of the clients proposes a new CID. Then something comes in a new address with the CID previously proposed. It seems fairly simple to distinguish the two.

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