Re: [saag] The Mathematical Mesh

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 25 April 2019 22:14 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B3E120343; Thu, 25 Apr 2019 15:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no 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 FMU2Fau5Y55J; Thu, 25 Apr 2019 15:14:49 -0700 (PDT)
Received: from mail-ot1-f45.google.com (mail-ot1-f45.google.com [209.85.210.45]) (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 CAF4D1200F8; Thu, 25 Apr 2019 15:14:49 -0700 (PDT)
Received: by mail-ot1-f45.google.com with SMTP id u17so982108otj.1; Thu, 25 Apr 2019 15:14:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SbupJ67oYGL4CrkcEAz7h1s2KKC5mw30lm7T6hYyzzo=; b=YvNpCxlVN2eM4/ciiZtAcEZWuJ+1yJE7aGz/HvAgvKAYF51j2HslOPyMOMOGuFHImr TgQT4t1vDDurnkY/7lRJFKWNqLQNADJg6vmiK2JQtRHuPCtYDifZRejyguDeZuwCdiLt OwZqDTWFjlEQVMn2mJqSGW6AlV9U3nW94naqRwfL0iK5E6WUJNxYW8sz10rFBuY2O5BT VUQ1wXV1dOCiUbA1yDBQ77Xd9IqZLBewiDmShwB8OjW385z0FQvyD0NveppGm3xLeWti XK7DW/nYqfL6E4tLRVRvAGlbTAJF1ChJLqozVwYRrQoDjyVFns3Aq3lf5K+/X+e6Amn7 9TJg==
X-Gm-Message-State: APjAAAUpMaYywbAus2M2TrQP2hqHXhkkuHCUmyMHJPVr215n16zG73BQ G1sU9+AlsBc95uUeHslYDlhJ0bjLVtlMrOR/fq0=
X-Google-Smtp-Source: APXvYqzC0hkyYXkFo48KFe/UTSDz7iSpvc47eyzoYaxZdRBku7vOl2GvYTrKE7mT7B2KTxdfIZ1yu/2pUeC+Q4HZ4Zw=
X-Received: by 2002:a9d:6543:: with SMTP id q3mr3986649otl.370.1556230488933; Thu, 25 Apr 2019 15:14:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwiF3iGiRO5reW4KCgf8vp=Kv=+4pD+_rGOcxEsD1Hxk4g@mail.gmail.com> <20190425161404.GS3137@localhost> <CAMm+LwgxdhusDWrHDs8SSGbjptPiRYPM30p9H=BFrpCbbRHdPQ@mail.gmail.com> <20190425214233.GX3137@localhost>
In-Reply-To: <20190425214233.GX3137@localhost>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 25 Apr 2019 18:14:37 -0400
Message-ID: <CAMm+LwjY=ckyhAqVej81wCChnR0jhmE5H0VBunxp31KfQCQ7uQ@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: secdispatch@ietf.org, IETF SAAG <saag@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007b4af405876225b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/uq3VkDa1Re9IrswBVwYWCjSUXP0>
Subject: Re: [saag] The Mathematical Mesh
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2019 22:14:51 -0000

On Thu, Apr 25, 2019 at 5:42 PM Nico Williams <nico@cryptonector.com> wrote:

> On Thu, Apr 25, 2019 at 05:12:00PM -0400, Phillip Hallam-Baker wrote:
> > On Thu, Apr 25, 2019 at 12:14 PM Nico Williams <nico@cryptonector.com>
> > wrote:
> >
> > Just to be clear: It is a similar approach to blockchain. The encoding
> used
> > is entirely separate.
>
> Understood.  The point is that you end up with a cryptographic
> append-only log.
>

Yep.




> > The reason I was able to simplify the Mesh code was that I realized that
> > all my application protocols could be implemented as instances of
> > synchronizing containers between devices.
>
> Nice.
>
> > > Count on me as a reviewer,
> >
> > Thanks, that is greatly appreciated. The status of the current drafts is
> > that the text is more or less complete, there are some missing images and
> > multiple missing examples.
>
> Is that a request for review sooner than later?


The current status is that the UDF and DARE drafts are essentially done. I
do not expect to make major changes to those drafts in response to my work.
I will of course expect to make changes due to the review cycle so if you
are interested in reviewing, those are the drafts to look at.

The next one I expect to be ready is the algorithms draft (8). This is
pretty complete except that I have moved in work from elsewhere which needs
attention and examples. Those will be the next examples generated by the
code.

If you want to see the scope of the work and how it hangs together, the
architecture guide has the text but not the pictures or conversations.




>