IETF Logo Mail Archive

Re: [quicwg/base-drafts] Where does the "quic " HKDF label apply? (#1971)

Kazuho Oku <notifications@github.com> Wed, 07 November 2018 02:25 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 3000A127332 for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 18:25:12 -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 EFW3LaVgNsY7 for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 18:25:11 -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 C43AA126CB6 for <quic-issues@ietf.org>; Tue, 6 Nov 2018 18:25:10 -0800 (PST)
Date: Tue, 06 Nov 2018 18:25:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541557508; bh=Pb2VBRs3fxN0FY5fJJjtWRKEnph7t8wlA9PAfRlhc7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tBuPoyjwmxYw7BteYVUh9GI5Wl5I4k/852va2Y6TS1N0bh5CK/4L0aRsbPUGWhefJ GyJ8cS1sRwkeYhTSGOmMhbnLCo+WqHOytb6QeD1zv+RMVDXyiqfUo5DfxaYo2ifOd6 CdTysV1PcPQi8McreEU/PAdxl6oI/1hRZBnxlCCg=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab719bb7655e60ed5f1d7d7e2997a91d5a07bce0de92cf0000000117fa0f0492a169ce16837aaf@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1971/436481268@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1971@github.com>
References: <quicwg/base-drafts/issues/1971@github.com>
Subject: Re: [quicwg/base-drafts] Where does the "quic " HKDF label apply? (#1971)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be24d04d8976_1b643fe0cced45bc7046c"; 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/VP1l5M6TkHDKpopVqJpeCaevuZQ>
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, 07 Nov 2018 02:25:12 -0000

:+1:

My understanding is that there is no prefix separation between TLS and DTLS, and therefore that we do not need that in QUIC.

It also lessens the friction we would have when moving to TLS 1.4, because the prefix can just change in the TLS stack.

-- 
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/1971#issuecomment-436481268

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