Re: [quicwg/base-drafts] Be more explicit about key derivation (#1568)

Kazuho Oku <notifications@github.com> Sun, 15 July 2018 14:42 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 7F274130DE4 for <quic-issues@ietfa.amsl.com>; Sun, 15 Jul 2018 07:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 GxQlfP636Qsu for <quic-issues@ietfa.amsl.com>; Sun, 15 Jul 2018 07:42:26 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0589B130F2D for <quic-issues@ietf.org>; Sun, 15 Jul 2018 07:42:26 -0700 (PDT)
Date: Sun, 15 Jul 2018 07:42:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531665745; bh=cS+6t1v4yYAFuuLIkCXBjTh3L1VAplNcla/VjJMdsWI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OoNsoBriESC8oZYg8u0n3aS6UeRK+1KwCf0p9yOgGtVu1AMg8e2Zqta3DH08XsCQp 54ARdaHyVd0/5xQv18mJfIiusdJwXj1wt1j6vkR9DFOUJtqP5Q2jqpw7J86OtU/97j dEFK7NGyeHNKqI4unwZLDZtyTbXvFirXwedXq4YU=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab60292685b49ab06d60e2406dffec9ffe3154acc092cf0000000117631f5192a169ce14582fb8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1568/405096563@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1568@github.com>
References: <quicwg/base-drafts/issues/1568@github.com>
Subject: Re: [quicwg/base-drafts] Be more explicit about key derivation (#1568)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4b5d5141a3a_1b342b0a0ea80f50188746"; 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/YkISOUF4Sw3IWZOqzZh_oy9bm2g>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 14:42:43 -0000

> Traffic secrets are generated by TLS, using "tls13 ", the only one that we have to worry about is the initial secrets, which QUIC derives.

My understanding is that (at least for the interop) we have agreed to use "quic " for traffic secrets as well.

-- 
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/1568#issuecomment-405096563