Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)

Igor Lubashev <> Thu, 28 February 2019 18:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6F58E1289FA for <>; Thu, 28 Feb 2019 10:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Status: No, score=-3 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_NONE=-0.0001, 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 t0sygje2lkVR for <>; Thu, 28 Feb 2019 10:59:25 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3BF471200ED for <>; Thu, 28 Feb 2019 10:59:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=epQOV+QaW1vhXq24G9GmsL8hO5U=; b=hW5Jb5+dSXNwzn0e 5Rj4p39IObv4gkUwSdRJ+tnBbDQUzoo2TnTo7quOuXlVmsYuMHbouSqNzC0t0v/Z jUlZXHyRrsT6wep2oSpmGlpX2Df5sbT2Zo/UeL2Jlfy2pCDe5eNiz78vrHMIGSmO IFcWzkGiUIq1ubGE/zDRtl4kz7k=
Received: by with SMTP id filter1435p1mdw1-30257-5C782F8B-54 2019-02-28 18:59:23.86755089 +0000 UTC m=+583291.385407717
Received: from (unknown []) by (SG) with ESMTP id 8rzMMnFJQOGXx96C40lDhA for <>; Thu, 28 Feb 2019 18:59:23.764 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id B74152C0608 for <>; Thu, 28 Feb 2019 10:59:23 -0800 (PST)
Date: Thu, 28 Feb 2019 18:59:23 +0000
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2026/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c782f8bb54d0_69ea3f9d03ed45c41537a8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0YgsZNOZMpbKjOqYjeTehXtpRyAkrL2fBMa0 DPdevCnurJ2zrMVDFKqnA1ewusV5dw9Cn4c/5PHKoODPX+WI7hEQKlUKDUuaO2pvLSXMlzvUl/UmHg o226k7ShP3jBP6XDEGe66UbxWdIh8ncwLcMk2KWJUIw+umpGnDi5tutyAItPi3CjI6b8CzLpf0JBq4 o=
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: Thu, 28 Feb 2019 18:59:27 -0000

I think the point @MikeBishop is making is a sensible one.  The explicit text that Mike has quoted is implying that servers SHOULD use Client-chosen CID for routing.  After all, this purpose is explicitly stated, without any caveats, right there in the spec.

I would rather see that quoted text removed altogether.  It is enough to state that "_A client SHOULD select an initial Destination Connection ID length long enough to satisfy the minimum size requirements for every QUIC version it supports_". This is accurate and not misleading.

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