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

Martin Thomson <> Wed, 27 May 2020 05:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4E02E3A07E5 for <>; Tue, 26 May 2020 22:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 OwX7-6N-o8I7 for <>; Tue, 26 May 2020 22:55:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B0EA23A07E3 for <>; Tue, 26 May 2020 22:55:38 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BC0BF1C0AE0 for <>; Tue, 26 May 2020 22:55:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590558936; bh=EM0SlehbhuiVWP3pkiIq6Q+Fv1fdgjhbS7RYlPWGb0E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Jq+iEspNRcLGwbcwnLCwbhBpUw3UaUSWpkxDkFUheOeouovtIyjsRSZ+q+iqTvzy8 CADsfBguqb3v4pkssML7acujMa7WMBmBO30whyS2iD2jP2GpBXhiHgw05bKt5V23Q5 V5V4sHOC8j02xb3JdY1x+95IBYT08iK+Oy9FlgnE=
Date: Tue, 26 May 2020 22:55:36 -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_5ece00d8abdc3_785f3ff8362cd96879944b"; 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 05:55:40 -0000

@martinthomson commented on this pull request.

-* absence of the original_destination_connection_id transport parameter from
-  the server,
+An endpoint MUST treat the following as a connection error of type
 * absence of the retry_source_connection_id transport parameter from the server
   after receiving a Retry packet,

I think that the existing rules we basically permit either.  Is there some way you would prefer to phrase this?

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