IETF Logo Mail Archive

Re: [quicwg/base-drafts] Signaling TLS handshake failure (#272)

ianswett <notifications@github.com> Thu, 09 February 2017 02:56 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 977DB1296B8 for <quic-issues@ietfa.amsl.com>; Wed, 8 Feb 2017 18:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.482
X-Spam-Level:
X-Spam-Status: No, score=-7.482 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001, URIBL_BLOCKED=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 z9GhWx48ib02 for <quic-issues@ietfa.amsl.com>; Wed, 8 Feb 2017 18:56:53 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A136129546 for <quic-issues@ietf.org>; Wed, 8 Feb 2017 18:56:53 -0800 (PST)
Date: Wed, 08 Feb 2017 18:56:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1486609012; bh=8ZSHqiwlXdMGxZPcRBl2s6kIOYufkYBG4UKLScFZz6c=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Kr4Y1uQoFpO+P48Wkr3rWHGT9uVIsGHyZnsw7vcFNyW8LYZ4taGE6Yu/xl+hGGRh4 1zNL80dN6iDR0AuG7/c2YnBMemPhajNyRwIyxr9H6vWVsnDbwNK+cLq3pLIF2DJeCO mijG0sVqQdbCLrU9lr2ZAK7iWObTiR6NVEljR63o=
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/272/278532788@github.com>
In-Reply-To: <quicwg/base-drafts/issues/272@github.com>
References: <quicwg/base-drafts/issues/272@github.com>
Subject: Re: [quicwg/base-drafts] Signaling TLS handshake failure (#272)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_589bda745a8d0_dfb3fc2e906f130101880"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/CKQGfgiQcenHPY08C4XTmVmdxzo>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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, 09 Feb 2017 02:56:54 -0000

I may be missing it, but when I skimmed and searched in the transport draft, I couldn't find anywhere it said what frame types may be sent without encryption.

I'm happy to have both TLS alerts and connection closes if they're useful.  Ryan reminded me there have been some cases when unencrypted connection close errors were able to provide valuable insight to debug an issue.

-- 
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/272#issuecomment-278532788

v2.36.0 | Report a Bug | By Email | System Status