IETF Logo Mail Archive

Re: [quicwg/base-drafts] Why must we not use post-handshake client auth? (#2294)

David Schinazi <notifications@github.com> Wed, 23 January 2019 17:06 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 7EBDC130EA8 for <quic-issues@ietfa.amsl.com>; Wed, 23 Jan 2019 09:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 s7LP-5hB8ePm for <quic-issues@ietfa.amsl.com>; Wed, 23 Jan 2019 09:06:11 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E485D12D84C for <quic-issues@ietf.org>; Wed, 23 Jan 2019 09:06:10 -0800 (PST)
Date: Wed, 23 Jan 2019 09:06:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548263169; bh=9Znuyv5W9Bl4e+xudKhJ7yKPE5b4Qhs9TCtJF1apZ0Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ORzn/Etnj9TS37Ig9Z2X3V26FjuiGCwEQEU82poo0E8+aWwM2J3Ux+UQIoTCWZPBq E0ogOdqE7CFYsnoYSgIeC23XZAA3R56qgO+adBEnCtnfMM/3kDYGvc8YsYIV2oyXvl J4yff4Tq6BGlJnmvSpD2CrkVsM5+9DJaXu8dkG/Q=
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbb72fa3e196c6706321ab5f9d587cc3889d60ffe92cf000000011860610192a169ce179b352f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2294/456884593@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2294@github.com>
References: <quicwg/base-drafts/issues/2294@github.com>
Subject: Re: [quicwg/base-drafts] Why must we not use post-handshake client auth? (#2294)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c489f01ad947_45643fc1466d45c4303510"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/wawx5zv1cc7gT7tJTeJgvTkSTHc>
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, 23 Jan 2019 17:06:13 -0000

@martinthomson please don't close issues without any discussion. I've opened #2367 because I would like to see this resolved.

-- 
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/2294#issuecomment-456884593

v2.23.0 | Report a Bug | By Email