Re: [quicwg/base-drafts] How to reject a connection attempt (#3690)

Kazuho Oku <> Mon, 25 May 2020 17:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0D20C3A0E93 for <>; Mon, 25 May 2020 10:51:30 -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 PPTwbX5fZCSe for <>; Mon, 25 May 2020 10:51:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0D6BF3A0E8F for <>; Mon, 25 May 2020 10:51:24 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F2D54960790 for <>; Mon, 25 May 2020 10:51:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590429082; bh=BqI/HGFPPqB3qFNzmRkZ0oKojjiBKX9Yah1mViZSQS4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PpD+Wx41pRroa3JtgUmOpzcTdHAfPEC53jcQzYJoH6AeA31tfCPsuA9j+V7ueTy5F da8vHxHmx3It7lgCzowC7/3wA9kBsPjw+iMucefbatifc9ID/hIRHjIHat4FVI6e9F 3RyMc9e4fjziygxx405yuvmlAJ54XJUYQ4cnUC7I=
Date: Mon, 25 May 2020 10:51:22 -0700
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3690/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] How to reject a connection attempt (#3690)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ecc059ae3a7c_429a3fd5f52cd96c707742"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Mon, 25 May 2020 17:51:30 -0000

@ianswett I think that is a fine thing to do as long as Chrome is happy-eyeballing with TLS-over-TCP.

But as a specification, it is my understanding that happy-eyeballing is not a prerequisite. I'd assume that we'd want applications that use QUIC only to be as ignorant against unauthenticated signals as those using TLS-over-TCP is.

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