Re: [quicwg/base-drafts] Clarify what to do when ALPN negotiation fails (#2483)

Martin Thomson <> Wed, 20 February 2019 16:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 78DA312870E for <>; Wed, 20 Feb 2019 08:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Status: No, score=-1.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q7xUeGy06di8 for <>; Wed, 20 Feb 2019 08:53:54 -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 B19E31277D2 for <>; Wed, 20 Feb 2019 08:53:53 -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=FcBpcey0xm32K3YpQ8lu+lgYrYI=; b=cge9FFJWqWggYgVf jfA8SYFJV4fpBf9b5qnc6grPZvk0w4J0ZFK1p1SLBZYICJwyKUC+3qASLmvuPFtD iXcN6catp6CUj9hsgqIznacHbvWW/BE3U55GRFYPj2vE2e2FWexUGCWbpmQFSTcx +Oh0coG3F54jgSUp/TTR+tDIK/Y=
Received: by with SMTP id filter0591p1iad2-10820-5C6D861F-3B 2019-02-20 16:53:51.757828831 +0000 UTC m=+167846.181376929
Received: from (unknown []) by (SG) with ESMTP id SL458DFDQ8qLsOWy0Mrbrw for <>; Wed, 20 Feb 2019 16:53:51.784 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id BC616440858 for <>; Wed, 20 Feb 2019 08:53:51 -0800 (PST)
Date: Wed, 20 Feb 2019 16:53:51 +0000
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2483/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify what to do when ALPN negotiation fails (#2483)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6d861fbaa58_58ee3ff29ccd45b4322471"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2ivqC7iFqFfeaHA/578blPm33sKHSmD618GQ y6Ky0Lhsc3lFLMI2VC+j2lgm631pNpE59+62lBhxQGXJSnFw/l6YjT85x9z2Hqp+VjYM6nxPlQ87Fj yc0hIyUPnKfNGOYWRfhdlNq2YclGjScsTGNHR1sZLXydnhy9trJEzmdJEUWkC/9WFYEKtGQ6tf/NFk E=
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, 20 Feb 2019 16:53:56 -0000

martinthomson commented on this pull request.

RFC 7301 only specifies that the server use this alert.  A server can always pretend not to support the extension.  A client that sends no_application_protocol in that case might still be valid, but it's not defined behaviour in 7301.  I think that you need to reword this slightly to allow for that.

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