IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Thu, 07 March 2019 01:41 UTC

Return-Path: <noreply@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 14A141312C4 for <quic-issues@ietfa.amsl.com>; Wed, 6 Mar 2019 17:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.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_HI=-5, SPF_PASS=-0.001] autolearn=ham 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 IpINMK2vuA5o for <quic-issues@ietfa.amsl.com>; Wed, 6 Mar 2019 17:41:26 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 894E71312BB for <quic-issues@ietf.org>; Wed, 6 Mar 2019 17:41:26 -0800 (PST)
Date: Wed, 06 Mar 2019 17:41:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1551922885; bh=1qX9aTLFh3bo3R1KM76Mprj/KoT0rUwStguJU32dMbo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LPTO2VuL8aVwtZHk84HTuyNz2EM5/HUUyJRecvHkzp5KXl7RpcZKaxtrA3u9SyXhj P17TVyyoLQUXBzBNvQkkrAI/y0V1yZl2GiNZ9i3uyT3cb3OXjji5kgfr49qWfeZcOE 7CVt0MbvIcJcVpDP7Otp2w0eeE7AIyYTgaPaiP/I=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6ba146992fac41decbbfb5ce480e8b8802e7a3ce92cf00000001189838c592a169ce18d8ac2b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2495/470348543@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2495@github.com>
References: <quicwg/base-drafts/issues/2495@github.com>
Subject: Re: [quicwg/base-drafts] Clarify what to do when ALPN negotiation fails (#2495)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c8076c5acf21_9b73f80940d45b84187e1"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Ei6nLxUu-efYVWF5DzDNPxzoV5A>
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: Thu, 07 Mar 2019 01:41:28 -0000

Yes, I think that would be fine.  I don't think that we would be able to guarantee that the alert goes out before sending ClientFinished either.  It's certainly possible, but I can see how it might be tricky.

-- 
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/issues/2495#issuecomment-470348543

v2.23.0 | Report a Bug | By Email