IETF Logo Mail Archive

Re: [quicwg/base-drafts] Tls restore compat (#1256)

Kazuho Oku <notifications@github.com> Wed, 04 April 2018 11:55 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 48DD6126CC7 for <quic-issues@ietfa.amsl.com>; Wed, 4 Apr 2018 04:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 hZPRldMaRnas for <quic-issues@ietfa.amsl.com>; Wed, 4 Apr 2018 04:55:00 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B371124217 for <quic-issues@ietf.org>; Wed, 4 Apr 2018 04:55:00 -0700 (PDT)
Date: Wed, 04 Apr 2018 04:54:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1522842899; bh=zGdV1yNyxCGx/+opGpoadqzbxq8JrWyXJaEc9k1CI3M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yV5Q7H6GijBSHNxSfHIz8W36qgCLUyisbb+IZH143avGUsI2PFK32tgipHJuaoXKa 91URswErFFkFxGa30rc8vm9dYCMxqLOVNlYTb3jVl1xu7yPst7GcU6dnWWeTKc+GuJ QJBVP1Q2J1gjBQ2sSKxjOJUj+x989+8l2jS1vhBE=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abaddd22176baadf8df52823b702a6aab022ce602492cf0000000116dc7f1392a169ce127c064f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1256/c378574118@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1256@github.com>
References: <quicwg/base-drafts/pull/1256@github.com>
Subject: Re: [quicwg/base-drafts] Tls restore compat (#1256)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ac4bd1377742_24f23fdb79576f2c110617"; 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/NbwBR_AUfHzYevSA_JKFAra4PeM>
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, 04 Apr 2018 11:55:02 -0000

@martinthomson 
> For mine, a more principled AEAD API would take two labels: one for the key and one for the label, and avoid baking in the specific details of the TLS HKDF info structure. A hacky API change could distinguish between a NULL hash and an empty hash.
> 
> In summation, I'd prefer not to have to explain to future users of QUIC that this isn't a null terminator on the string, but a product of a design decision made before QUIC even really existed.

Thank you for your comments. While I understand and have sympathy to your arguments, I wonder if there's a strong reason to divert from the structure defined in TLS 1.3 considering the fact that the quic-tls draft depends on TLS 1.3.

-- 
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/1256#issuecomment-378574118

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