Re: [MLS] protections for MLS "handshake" messages

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Sat, 21 July 2018 02:58 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 770E2130E62 for <mls@ietfa.amsl.com>; Fri, 20 Jul 2018 19:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level:
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 Kmw1mxa1ujdE for <mls@ietfa.amsl.com>; Fri, 20 Jul 2018 19:58:37 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C21D7130DC5 for <mls@ietf.org>; Fri, 20 Jul 2018 19:58:37 -0700 (PDT)
Received: from fifthhorseman.net (unknown [IPv6:2001:470:1f07:60d:d8a1:1dff:fef1:ec8e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 70245F99A; Fri, 20 Jul 2018 22:58:35 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 2575320867; Fri, 20 Jul 2018 22:58:26 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Joseph Lorenzo Hall <joe@cdt.org>
Cc: mls@ietf.org
In-Reply-To: <CABtrr-XWoNyKq4BBrTF9pczHZoB6bJOsxvU=Xgq6x-m4Bdgbhw@mail.gmail.com>
References: <87fu0fxjhi.fsf@fifthhorseman.net> <CABtrr-XWoNyKq4BBrTF9pczHZoB6bJOsxvU=Xgq6x-m4Bdgbhw@mail.gmail.com>
Date: Fri, 20 Jul 2018 22:58:26 -0400
Message-ID: <87d0vhwazx.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/Qquj1VP9W-VVL5O4gbftdLWlFT8>
Subject: Re: [MLS] protections for MLS "handshake" messages
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Messaging Layer Security <mls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mls>, <mailto:mls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls/>
List-Post: <mailto:mls@ietf.org>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mls>, <mailto:mls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2018 02:58:40 -0000

On Thu 2018-07-19 13:39:16 -0400, Joseph Lorenzo Hall wrote:
> On Thu, Jul 19, 2018 at 12:45 PM Daniel Kahn Gillmor
> <dkg@fifthhorseman.net> wrote:
>>
>> In today's session, there seemed to be an open question that wasn't
>> explicitly addressed, so i wanted to raise it on the list.
>>
>> for lack of a better term, we're dividing MLS messages into
>> "application" messages and "handshake" messages.  (i think we need
>> a better term for "handshake", but i'll use it here for consistency with
>> the current discussion)
>
> What about "content" and "keying" messages as new names?

I'm maybe a little reluctant to use "content", because it seems too
generic, and too allusive to the elusive "content/metadata" boundary.
But i'd be fine with "application" and "keying" as the nomenclature.

But I'm more interested in what people think about protecting these
messages (or even the distinction between the two categories of message)
from the DS itself.  Is there a reason that we need to expose to the DS
that keying updates are happening?

     --dkg