IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Wed, 27 February 2019 20:46 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 AA40013112B for <quic-issues@ietfa.amsl.com>; Wed, 27 Feb 2019 12:46:35 -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 kyVH-xmVbnet for <quic-issues@ietfa.amsl.com>; Wed, 27 Feb 2019 12:46:34 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 1C044130E77 for <quic-issues@ietf.org>; Wed, 27 Feb 2019 12:46:33 -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=OV3Bd4/D3W1V26RGU9ihsoLbSWE=; b=f+76/M6d4HkRy/lB L0JcX0nWAQBveU5+MHMldNgZwi/I+jYbtWvEvz50icRwapLK2bHxFtNCNh3ui0Dy wD0gW9ciW0bi+u4+65zpQgM/xZIQAYmIqfEbe1TNJqmwaUjqbY2YnjaRq5MISQ3k CySQhr4BKkXCucA2hq9yEXiG7j4=
Received: by filter0118p1iad2.sendgrid.net with SMTP id filter0118p1iad2-22084-5C76F728-2F 2019-02-27 20:46:32.66988128 +0000 UTC m=+501887.294161321
Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0030p1iad2.sendgrid.net (SG) with ESMTP id n9FiwBW1SAKvBcugYKqRXQ for <quic-issues@ietf.org>; Wed, 27 Feb 2019 20:46:32.698 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id A8D39AE0305 for <quic-issues@ietf.org>; Wed, 27 Feb 2019 12:46:32 -0800 (PST)
Date: Wed, 27 Feb 2019 20:46:32 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7894e2beb5812e9bf7b2424c8b239ea36ab6b8de92cf00000001188eb92892a169ce18955108@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/c468023545@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_5c76f728a764b_7f43fba7c8d45c03964a1"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0qMgkPFdDRkKP0V88OVU9+h/wGptzybEt/cf nEFzxFcM6mamzuEh1HU9d0jbeTGMd2jt2PkCHXmGL8uxY0IUo13yNWx7UB0YUsHdGwBdige6UaD3hA 9xaMXE6TqJ7Sg/IMYfZ0qOXT9/w1hEpALPXR/rZ0mZxkaq3AKlpJJXlnNXLTtMvN5uOHotjoYoA76P c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/QhAFNrSxmeQWM8eSCJvG9eOg7hY>
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, 27 Feb 2019 20:46:36 -0000

Unfortunately yes.  This is a design change so it will need an issue as well.

I like it and we should do it, but can you add the error code we would use in CONNECTION_CLOSE to the text?

-- 
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-468023545

v2.23.0 | Report a Bug | By Email