[MLS] Tree hashes - ready to land?

Richard Barnes <rlb@ipv.sx> Fri, 19 April 2019 19:18 UTC

Return-Path: <rlb@ipv.sx>
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 BB143120006 for <mls@ietfa.amsl.com>; Fri, 19 Apr 2019 12:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 vFjb9oTAE37f for <mls@ietfa.amsl.com>; Fri, 19 Apr 2019 12:18:23 -0700 (PDT)
Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86781200F5 for <mls@ietf.org>; Fri, 19 Apr 2019 12:18:23 -0700 (PDT)
Received: by mail-oi1-x22e.google.com with SMTP id v84so4632351oif.4 for <mls@ietf.org>; Fri, 19 Apr 2019 12:18:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=9kqk1oEpTbEGvHaKAcIr1suKE86FUIuw/wmNB776CxM=; b=nxMVKQyobbCGRdpkFfHas+XVYw01w4ki0VuLrtfPo7JgjF2h3slMS0BBcDOxIwXEfT bDsXHqN5D+TJbld6VwW96JvhqYAYYiRhtPS5IsMxtaRLgoh5BsZ3KbsZbtpMCDJgy/j8 /CJsHgoTKd2Uq+UzILM3UQbDD/ngaJD46nIvDs0GU/mfcVv+QjpOxuFf5wiJfdZ+0bpv IQCu0EWdFx4FovJrGf6VzjEOgDaWS6aFamEwoAUqidLsHMV0xWTGyMqvWZAohIJWW/ca lSxOXsf4m+4zbUyldjekWfvQotd4Mf8CtNbBsVVBrNHGwsuEIPCB4yOv7JyQsJ4OkE+o e9LQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9kqk1oEpTbEGvHaKAcIr1suKE86FUIuw/wmNB776CxM=; b=flSmrg4XDsm3tFUfTVeCCxqHZe7/aeDQwGuCn6Xqny8scU80ds6VqvI34ifD+6XDGT sTJCIWsYe74bsbfnmzU3yPXKQRuBqVkPXHYEkQmvOZjOC7D9wk/Sbc09xEN84M9Jd0e1 TCAYVOSWSUqIHMsZDZXWuo0v41JrG3hXtKqlVvyFKZJI0Muox8PARNnsM3rBFjqShyIQ ab5KA/dfUY75bKtzv5hnPFX6s65XvWBzh/SLTB4X4vAAbB+G6YG4tjeyfGFGuYcCnnhm jlnIfRrfRVLQo1/hdtj5FiX8I9nxiM6hYQhdRoZ9+dlqi0ipldZv4eXFXlCwrrw4S/Y6 pqPw==
X-Gm-Message-State: APjAAAXe4C5RQvbzDrU8wzBpP9OB+9lZekZS7xSEzcWj5QibqYn0Lghv JwoqjW0pLxJrcoGr5Al+Pca+VjdVPoPwkRHC/D6wV7SnR0Prag==
X-Google-Smtp-Source: APXvYqzV64WAEerB/+z7D/2a1kSFLZS5IthR/CEtUX53e7AwjbIBbDSNHFLaCJS4j58g6qxCnf9sbNketxzDziUBRCI=
X-Received: by 2002:aca:544b:: with SMTP id i72mr2676668oib.51.1555701502485; Fri, 19 Apr 2019 12:18:22 -0700 (PDT)
MIME-Version: 1.0
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 19 Apr 2019 15:18:03 -0400
Message-ID: <CAL02cgR44HM3XUQT+OxWtyd5FpoqfvHu7mr5Akksz+tGXrOrDA@mail.gmail.com>
To: Messaging Layer Security WG <mls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006ebab70586e6fb04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/vpL38aBK7CZLernysZpaUuiVvrQ>
Subject: [MLS] Tree hashes - ready to land?
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 19 Apr 2019 19:18:26 -0000

Hey all,

I've been working on implementing the tree-hashing scheme we discussed in
Prague.  I just  updated the PR with what I think is a pretty
ready-to-merge change set:

https://github.com/mlswg/mls-protocol/pull/134

Please send comments there in the next few days.  Otherwise, we authors
will make a decision on our own :)

Thanks,
--Richard