Re: [quicwg/base-drafts] Clarify what to do when ALPN negotiation fails (#2483)
Martin Thomson <notifications@github.com> Wed, 20 February 2019 16:53 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78DA312870E for <quic-issues@ietfa.amsl.com>; Wed, 20 Feb 2019 08:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7xUeGy06di8 for <quic-issues@ietfa.amsl.com>; Wed, 20 Feb 2019 08:53:54 -0800 (PST)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B19E31277D2 for <quic-issues@ietf.org>; Wed, 20 Feb 2019 08:53:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; 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 filter0591p1iad2.sendgrid.net with SMTP id filter0591p1iad2-10820-5C6D861F-3B 2019-02-20 16:53:51.757828831 +0000 UTC m=+167846.181376929
Received: from github-lowworker-e711880.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id SL458DFDQ8qLsOWy0Mrbrw for <quic-issues@ietf.org>; Wed, 20 Feb 2019 16:53:51.784 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e711880.cp1-iad.github.net (Postfix) with ESMTP id BC616440858 for <quic-issues@ietf.org>; Wed, 20 Feb 2019 08:53:51 -0800 (PST)
Date: Wed, 20 Feb 2019 16:53:51 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcc9fd9c5435defe3e3d0443f252412befac728a392cf000000011885481f92a169ce18955108@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2483/review/205877409@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2483@github.com>
References: <quicwg/base-drafts/pull/2483@github.com>
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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2ivqC7iFqFfeaHA/578blPm33sKHSmD618GQ y6Ky0Lhsc3lFLMI2VC+j2lgm631pNpE59+62lBhxQGXJSnFw/l6YjT85x9z2Hqp+VjYM6nxPlQ87Fj yc0hIyUPnKfNGOYWRfhdlNq2YclGjScsTGNHR1sZLXydnhy9trJEzmdJEUWkC/9WFYEKtGQ6tf/NFk E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/X8sqN2IW-rcCuJRh8-pnvoMj1BA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=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: https://github.com/quicwg/base-drafts/pull/2483#pullrequestreview-205877409
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- [quicwg/base-drafts] Clarify what to do when ALPN… Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Martin Thomson
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Martin Thomson
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Jana Iyengar
- Re: [quicwg/base-drafts] Clarify what to do when … Martin Thomson
- Re: [quicwg/base-drafts] Clarify what to do when … Jana Iyengar
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Alessandro Ghedini
- Re: [quicwg/base-drafts] Clarify what to do when … Martin Thomson