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 03CBE126B7F
 for <quic-issues@ietfa.amsl.com>; Tue, 28 Nov 2017 22:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level: 
X-Spam-Status: No, score=-0.402 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_24=1.618, HTML_MESSAGE=0.001,
 RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 olJkpfLKKH56 for <quic-issues@ietfa.amsl.com>;
 Tue, 28 Nov 2017 22:16:31 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201])
 (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 04478126B7E
 for <quic-issues@ietf.org>; Tue, 28 Nov 2017 22:16:30 -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=7hxhVkuVA3subhX5pP74g6wvGVk=; b=DUO4sEsqpzHt0Wua
 vCaWrEh8DoTltOGR4UaZujtE3EqZTFl2n7JDTz7Fu8Bbx5ikoxMUW7KzXEGStf4e
 7HbgWTfYbetIeN1rS4BhcfvS/iF/ycTC6yZ74mGdjYrohLPlkKkz0Pd0OPrEOkzI
 z8Qg2lDOjHNdnlyamDj3WGBW4e4=
Received: by filter0073p1iad2.sendgrid.net with SMTP id
 filter0073p1iad2-25804-5A1E50BD-10
 2017-11-29 06:16:29.558751258 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net
 (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17])
 by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id yWXJlSrlSTOGYRbPeVnsLw
 for <quic-issues@ietf.org>; Wed, 29 Nov 2017 06:16:29.543 +0000 (UTC)
Date: Wed, 29 Nov 2017 06:16:29 +0000 (UTC)
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab5033cce37612f3c79f6cf1f36d8cea5564e9c28c92cf00000001163612bd92a169ce0df5bf15@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/608/347764022@github.com>
In-Reply-To: <quicwg/base-drafts/issues/608@github.com>
References: <quicwg/base-drafts/issues/608@github.com>
Subject: Re: [quicwg/base-drafts] Handshake errors (#608)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5a1e50bd6cb6c_55fa3fc020534f38886b5";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
tracking: 
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3kxhhyv9Ojk3WR6m0A1/bJCohUjIfTsS/Nnj
 QLh+WW41SPlp1NV1c6e6Na1zsWpljVUie1b63wUBJtssNFQ/zU7Z2CoziGWjzQHh58I118uPX+zuBU
 aRLU7JpccIkQ0FP0eLhCvRCdZPoTjB2qtM6xt/SUp+1neXqLeAGszJpE+J/hT9fGqxxAjKZK1ESaHC
 Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LKXZEXFU5gsrcwWzfRSg7MAFgqg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 29 Nov 2017 06:16:32 -0000

----==_mimepart_5a1e50bd6cb6c_55fa3fc020534f38886b5
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

When implementing this, I'm sending CONNECTION_CLOSE in a plaintext packet if the TLS handshake has not finished yet. I ran into a case where the cert validation failed, however I wasn't really able to indicate this with a reasonable error code. Should we have an error code for TLS_ERROR or HANDSHAKE_ERROR

-- 
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/608#issuecomment-347764022
----==_mimepart_5a1e50bd6cb6c_55fa3fc020534f38886b5
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>When implementing this, I'm sending CONNECTION_CLOSE in a plaintext pack=
et if the TLS handshake has not finished yet. I ran into a case where the c=
ert validation failed, however I wasn't really able to indicate this with a=
 reasonable error code. Should we have an error code for TLS_ERROR or HANDS=
HAKE_ERROR</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/issues/608#issuecomment-347764022">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkqzpJxo0CEFrNtgC=
DxKAUnESWg9Qoks5s7Pa9gaJpZM4NytAA">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkqwVbwwJwd-tWOX-F0=
MgORFmZumoBks5s7Pa9gaJpZM4NytAA.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/issu=
es/608#issuecomment-347764022"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></meta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name=
":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates=
":{"snippets":[{"icon":"PERSON","message":"@siyengar in #608: When implemen=
ting this, I'm sending CONNECTION_CLOSE in a plaintext packet if the TLS ha=
ndshake has not finished yet. I ran into a case where the cert validation f=
ailed, however I wasn't really able to indicate this with a reasonable erro=
r code. Should we have an error code for TLS_ERROR or HANDSHAKE_ERROR"}],"a=
ction":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/is=
sues/608#issuecomment-347764022"}}}</script>=

----==_mimepart_5a1e50bd6cb6c_55fa3fc020534f38886b5--

