Mathematical Mesh 3.0 Part I: Architecture Guide
draft-hallambaker-mesh-architecture-12
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-01-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
html
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group P. M. Hallam-Baker
Internet-Draft 16 January 2020
Intended status: Informational
Expires: 19 July 2020
Mathematical Mesh 3.0 Part I: Architecture Guide
draft-hallambaker-mesh-architecture-12
Abstract
The Mathematical Mesh 'The Mesh' is an end-to-end secure
infrastructure that makes computers easier to use by making them more
secure. The Mesh provides a set of protocol and cryptographic
building blocks that enable encrypted data stored in the cloud to be
accessed, managed and exchanged between users with the same or better
ease of use than traditional approaches which leave the data
vulnerable to attack.
This document provides an overview of the Mesh data structures,
protocols and examples of its use.
[Note to Readers]
Discussion of this draft takes place on the MATHMESH mailing list
(mathmesh@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/search/?email_list=mathmesh.
This document is also available online at
http://mathmesh.com/Documents/draft-hallambaker-mesh-
architecture.html.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 19 July 2020.
Hallam-Baker Expires 19 July 2020 [Page 1]
Internet-Draft Mesh Architecture 3.0 January 2020
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Related Specifications . . . . . . . . . . . . . . . . . 6
2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 6
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 6
2.4. Implementation Status . . . . . . . . . . . . . . . . . . 6
3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. A Personal PKI . . . . . . . . . . . . . . . . . . . . . 9
3.1.1. Device Management . . . . . . . . . . . . . . . . . . 9
3.1.2. Exchange of trusted credentials. . . . . . . . . . . 10
3.1.3. Application configuration management . . . . . . . . 10
3.1.4. The Mesh as platform . . . . . . . . . . . . . . . . 11
3.2. Mesh Architecture . . . . . . . . . . . . . . . . . . . . 11
3.2.1. Mesh Device Management . . . . . . . . . . . . . . . 12
3.2.2. Mesh Account . . . . . . . . . . . . . . . . . . . . 13
3.2.3. Mesh Service . . . . . . . . . . . . . . . . . . . . 15
3.2.4. Mesh Messaging . . . . . . . . . . . . . . . . . . . 15
3.3. Using the Mesh with Applications . . . . . . . . . . . . 16
3.3.1. Contact Exchange . . . . . . . . . . . . . . . . . . 17
3.3.2. Confirmation Protocol . . . . . . . . . . . . . . . . 17
3.3.3. Future Applications . . . . . . . . . . . . . . . . . 17
4. Mesh Cryptography . . . . . . . . . . . . . . . . . . . . . . 18
4.1. Best Practice by Default . . . . . . . . . . . . . . . . 19
4.2. Multi-Level Security . . . . . . . . . . . . . . . . . . 19
4.3. Multi-Key Decryption . . . . . . . . . . . . . . . . . . 19
4.4. Multi-Party Key Generation . . . . . . . . . . . . . . . 20
4.5. Data At Rest Encryption . . . . . . . . . . . . . . . . . 20
4.5.1. DARE Envelope . . . . . . . . . . . . . . . . . . . . 21
4.5.2. Dare Container . . . . . . . . . . . . . . . . . . . 21
4.6. Uniform Data Fingerprints. . . . . . . . . . . . . . . . 22
4.6.1. Friendly Names . . . . . . . . . . . . . . . . . . . 22
4.6.2. Encrypted Authenticated Resource Locators . . . . . . 23
4.6.3. Secure Internet Names . . . . . . . . . . . . . . . . 24
Show full document text