[Mathmesh] Lets get started

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 13 August 2019 16:10 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: mathmesh@ietfa.amsl.com
Delivered-To: mathmesh@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 068501200FA for <mathmesh@ietfa.amsl.com>; Tue, 13 Aug 2019 09:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id K0h791slNSbe for <mathmesh@ietfa.amsl.com>; Tue, 13 Aug 2019 09:10:09 -0700 (PDT)
Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com []) (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 44D6B12020A for <mathmesh@ietf.org>; Tue, 13 Aug 2019 09:10:09 -0700 (PDT)
Received: by mail-ot1-f42.google.com with SMTP id m24so21571310otp.12 for <mathmesh@ietf.org>; Tue, 13 Aug 2019 09:10:09 -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:from:date:message-id:subject:to; bh=AGT/aIA0iEOObLbMjnIgM9TYcBZEwiCJ4RHjC8uI7YU=; b=dUwoX/BTQqtWjdVjFk1dn4dvAccIljFEhrlS2s+ZPFuWgN+p3LzwNA/m3fhwmPaH9O W+/LQVpH0jJYRsgNJ+C6/9HUX8XoY3zsB1XnMVwoaCjCGD1Cs2qtW7KEBMatR34ZcBli J3S4BaqNEXxBJ36w7sfe9v1I9LR4GaaPGiOHkCMeXxz1m2GAKfqJ+a2FIdqlr1nxdm+u SEOrYGVCSM8Fa7FaxfEIlgCxXsekBfFqYSRZFa8nCZ2/NWX1Yk/1VYXIVWKG6DKVbhmz VKVimmq3Cc3JDeJV9kPrfoLZXwhOeSEsEZ6S130WBeUzT7h3SV0v55aRPWq/vWmbSsLB GtBQ==
X-Gm-Message-State: APjAAAUMfzjCFYMnpzlWU+IudYuz+lYwrRHBMceaMx2AslXYSX+J5diE at3d+XTSl+fry4iIcvXve39EBDMVRazOuKOBjVvlN0HM
X-Google-Smtp-Source: APXvYqy6D7wIfrO6Ixdwt4z0r/W+5dvwJ+Kh9YeT8egsmcAXhXkdfnLd9I4RPU9HXLOKiAHkrMMOHilxX4QbDBux82A=
X-Received: by 2002:a9d:c22:: with SMTP id 31mr37240320otr.48.1565712608193; Tue, 13 Aug 2019 09:10:08 -0700 (PDT)
MIME-Version: 1.0
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 13 Aug 2019 12:09:31 -0400
Message-ID: <CAMm+Lwiz4O5uwz1hcgjq5w1M34K6VaDW9XzBUSrfumQ5ks1Efw@mail.gmail.com>
To: mathmesh@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d4f33c059001dfa8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mathmesh/SaNUcqEHLQSJhLMuQwZo8rA_yV8>
Subject: [Mathmesh] Lets get started
X-BeenThere: mathmesh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <mathmesh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mathmesh>, <mailto:mathmesh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mathmesh/>
List-Post: <mailto:mathmesh@ietf.org>
List-Help: <mailto:mathmesh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mathmesh>, <mailto:mathmesh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2019 16:10:11 -0000

I have just submitted a new set of the first five drafts in the series.

As far as the text goes, Parts I, II and III are pretty much complete and
consistent and the other two are works in progress which I hope to get into
a consistent state by the end of next week.

The drafts are written in anticipation of the HTML based RFC format and use
diagrams and mathematical notations for clarity. I strongly recommend
reading the HTML versions which are posted on the project Web site until
the IETF tools are brought up to date.

I. Architecture
an overview of the Mesh as a system and the relationship between its
constituent parts.
Uniform Data Fingerprint
the UDF format used to represent cryptographic nonces, keys and content
digests in the Mesh and the use of Encrypted Authenticated Resource
Locators (EARLs) and Strong Internet Names (SINs) that build on the UDF
Data at Rest Encryption
the cryptographic message and append-only sequence formats used in Mesh
applications and the Mesh Service protocol.
Schema Reference
the syntax and semantics of Mesh Profiles, Container Entries and Mesh
Messages and their use in Mesh Applications.
Protocol Reference
the Mesh Service Protocol.
The Mesh is at this point two things:

1) It is a tool designed to serve a specific, limited set of purposes.
2) It is a toolkit that can be used to address multiple purposes.

As far as IETF adoption goes, we could choose to adopt none, part or all as
WG items. However there are some constraints. Since part 5 depends on part
4, 4 on 3, and 3 on 2, it is not possible to choose to do part 4 without
also doing 3 and 2.

One of my greatest disappointments on the Web was that by the time Tim
assembled to team at CERN to fix HTTP, the exponent had already kicked in
and we were prisoners of the user base. So I have been holding off
deployment until at least I was happy with the way the system worked
together. This is now the third major redesign.

We will have to have some users before we can be sure we have a useful
spec. And having users does not mean we can't make breaking changes but we
will at least have to give them an upgrade path. So if anyone has a big
idea that is going to cause breaking changes, if they propose it now, there
will be no need for an upgrade plan which will make it simpler.

Since UDF is the simplest of the proposals and the others depend on it, I
suggest we start by looking at that first.