Re: [quicwg/base-drafts] use TRANSPORT_PARAMETER_ERROR when authenticating connection IDs (#3691)

Martin Thomson <> Wed, 27 May 2020 03:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CED9E3A0DB9 for <>; Tue, 26 May 2020 20:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Status: No, score=-1.483 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 c-rRo-0nI4Ys for <>; Tue, 26 May 2020 20:42:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7B2FC3A0DB8 for <>; Tue, 26 May 2020 20:42:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D9F6B6E0768 for <>; Tue, 26 May 2020 20:42:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590550934; bh=pwGcV8C2iXiuih5/4D1EBCX636kvqHJUAQWfg4RSn0Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FToy9wY42OIYGep2GvTAey6wOTsCPfUTNTYOuTOGVlta9Gl1MnIzxSoyJwZRzftX7 tCClA2Mm4+Gs2LyessAkxwXLGbCnAfJz2nHvxcZGGfAvrzqOmloSbmOdH0CJ/lfhh5 7potDPF2jaDtx/BNZlyT+coYKJoYGrn/atrMRvac=
Date: Tue, 26 May 2020 20:42:14 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3691/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] use TRANSPORT_PARAMETER_ERROR when authenticating connection IDs (#3691)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ecde196cb97d_78733ff8362cd968262318"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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, 27 May 2020 03:42:17 -0000

@martinthomson commented on this pull request.

>  carrying attacker-chosen connection IDs during the handshake. An endpoint MUST
-treat any of the following as a connection error of type PROTOCOL_VIOLATION:
+treat any of the following as a connection error of type

A list is good here, but these aren't all equal.  In particular, the behaviour that is conditioned on whether a Retry was sent is not consistent with your principle.  I would argue that those are also PROTOCOL_VIOLATION cases.

If you agree, then you can move those two into the next list (which currently only has one item).  That leaves two items in this list and I think that can be turned back into prose.

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