Re: [quicwg/base-drafts] Use the same KDF regardless of TLS version (#2034)
Kazuho Oku <notifications@github.com> Wed, 21 November 2018 07:57 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 A8C92130EE9 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 23:57:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 z3X2ZKetrSbM for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 23:57:26 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9265D127332 for <quic-issues@ietf.org>; Tue, 20 Nov 2018 23:57:26 -0800 (PST)
Date: Tue, 20 Nov 2018 23:57:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542787045; bh=sRiI0FvR1DDEvwxA9gRvBBUWWoh3J3WNUVkEoD2RUHk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2RSszkmvSjGjZbnjGGaiTgEdLqWozI2GDCsw8v4m4qCwRdlKp/r4gbdxDaOo73EVM BqHV8OjY/eGR/kFajElZyCFhbwUrtWmex0P9RWfsX3MlvEHLrHIgZHEdr8lwXCr2Ce wtnvJgGi0HNxlxXDYJnFMIoiKtN1tV/25UfVxwOM=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8735296c8de6d10687a2ee583d3987ddda888b3792cf00000001180cd1e592a169ce16d3c410@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2034/c440570473@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2034@github.com>
References: <quicwg/base-drafts/pull/2034@github.com>
Subject: Re: [quicwg/base-drafts] Use the same KDF regardless of TLS version (#2034)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf50fe53068c_4fdd3fa44e0d45bc17559b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/X_XJ06CpgQo5K-Dqam9JTZiRo3Q>
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, 21 Nov 2018 07:57:29 -0000
> If it isn't, then we'll have interop failure. If it is, that will artificially hamper 1.4 deployment. The answer depends on what type of API the TLS stacks would provide. For example, it would not be an issue for a TLS stack that exposes a “method” that creates a AEAD context from a TLS connection. Anyways, if we are to use the same HKDF construction for TLS 1.4 and above, I do not see the reason for having the “tls13 ” prefix. Should we revert #1991 to reduce the number of changes? -- 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/2034#issuecomment-440570473
- [quicwg/base-drafts] Use the same KDF regardless … Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… janaiyengar
- Re: [quicwg/base-drafts] Use the same KDF regardl… Marten Seemann
- Re: [quicwg/base-drafts] Use the same KDF regardl… Alessandro Ghedini
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… ekr
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… ekr
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson