IETF Logo Mail Archive

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

Alessandro Ghedini <notifications@github.com> Wed, 20 February 2019 17:29 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 1A62A130E27 for <quic-issues@ietfa.amsl.com>; Wed, 20 Feb 2019 09:29:42 -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 N2j-YfjAJPgS for <quic-issues@ietfa.amsl.com>; Wed, 20 Feb 2019 09:29:40 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 6AE3A130DC9 for <quic-issues@ietf.org>; Wed, 20 Feb 2019 09:29:40 -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=L1g7/891wQQgLbVXPHCXsG2sCGQ=; b=V2ZRfHDYqjYHLxef xEM6pF9Z/7q4b9vO4DbhhxIJZD1RagHoZKWHDw+UxkWPMI61eStsCpkSqiawSDOq tQxdjp3wynnsFnWIuOU0Cj6erDXoelXdpumI34IsPJ/yvT6al73EQ7vGVdKe934k b+3Z9JdxGkpQhtiqM0HlUHUSFEI=
Received: by filter0534p1iad2.sendgrid.net with SMTP id filter0534p1iad2-429-5C6D8E81-20 2019-02-20 17:29:37.221722929 +0000 UTC m=+1285216.157097055
Received: from github-lowworker-97d0962.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0025p1iad2.sendgrid.net (SG) with ESMTP id pe49Yv3nRXKOVqO0EZabbw for <quic-issues@ietf.org>; Wed, 20 Feb 2019 17:29:37.219 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-97d0962.cp1-iad.github.net (Postfix) with ESMTP id 3038A8075E for <quic-issues@ietf.org>; Wed, 20 Feb 2019 09:29:37 -0800 (PST)
Date: Wed, 20 Feb 2019 17:29:37 +0000
From: Alessandro Ghedini <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc4c18ffe1cb1ef12b59b1fce8d7ff55e31e6869492cf000000011885508192a169ce18955108@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/c465677177@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_5c6d8e812e34e_b043fb2a50d45c0277544"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ghedo
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0q5Yrqt1VE8BJ0VjU46/LQTEv0Dzu7oXez2w Jb3V8+McRvnkcLVnNAfIsbyTkvaqHz4qZTbZ1nA2CjdLBBHoxq4kCLgcsjcBOtfqbEJ39JjtZvpI7H v354GBViyGvo3AutarA+gCtpvvi7UQ4/Z0y8bT33h7ba05rieY/mmdRfEqmEzOcd3PRrOxK2ley7Sp 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/MPz-07KETKyXvEc7Wf-ncIZZ_W0>
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 17:29:42 -0000

Yeah I was thinking about that. I wonder if it would make sense for the client to simply send PROTOCOL_VIOLATION instead of a TLS alert.

-- 
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#issuecomment-465677177

v2.23.0 | Report a Bug | By Email