Mathematical Mesh: Architecture
draft-hallambaker-mesh-architecture-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Phillip Hallam-Baker 
Last updated 2018-08-27 (latest revision 2017-09-18)
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) 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. Hallam-Baker
Internet-Draft                                         Comodo Group Inc.
Intended status: Informational                           August 27, 2018
Expires: February 28, 2019

                    Mathematical Mesh: Architecture
                 draft-hallambaker-mesh-architecture-05

Abstract

   The Mathematical Mesh ?The Mesh? is an end-to-end secure
   infrastructure that facilitates the exchange of configuration and
   credential data between multiple user devices.  The architecture of
   the Mesh and examples of typical applications are described.

   This document is also available online at
   http://mathmesh.com/Documents/draft-hallambaker-mesh-
   architecture.html [1] .

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 February 28, 2019.

Copyright Notice

   Copyright (c) 2018 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.  Code Components extracted from this document must

Hallam-Baker            Expires February 28, 2019               [Page 1]
Internet-Draft       Mathematical Mesh Architecture          August 2018

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Mesh Profiles . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Mesh Services . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Document Roadmap  . . . . . . . . . . . . . . . . . . . .   5
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Related Specifications  . . . . . . . . . . . . . . . . .   6
     2.2.  Defined Terms . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Requirements Language . . . . . . . . . . . . . . . . . .   6
     2.4.  Implementation Status . . . . . . . . . . . . . . . . . .   7
   3.  Mesh Services . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Portal Service  . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Catalog Services  . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  Persistence Model . . . . . . . . . . . . . . . . . .   9
       3.2.2.  Retrieval Model . . . . . . . . . . . . . . . . . . .  10
     3.3.  Inbound Services  . . . . . . . . . . . . . . . . . . . .  10
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Use Case  . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.2.  What Makes PKI Hard . . . . . . . . . . . . . . . . . . .  14
     4.3.  The Devil is in the Deployment  . . . . . . . . . . . . .  15
     4.4.  Why change is possible  . . . . . . . . . . . . . . . . .  16
   5.  Architectural Principles  . . . . . . . . . . . . . . . . . .  17
     5.1.  User Centered Design  . . . . . . . . . . . . . . . . . .  17
     5.2.  User Centered Trust.  . . . . . . . . . . . . . . . . . .  17
     5.3.  A Credential Designed for Persistence . . . . . . . . . .  19
     5.4.  Eliminate unnecessary options . . . . . . . . . . . . . .  19
     5.5.  Strong Public Key Identifiers . . . . . . . . . . . . . .  19
   6.  Mesh Profiles . . . . . . . . . . . . . . . . . . . . . . . .  20
     6.1.  Master and Personal Profiles  . . . . . . . . . . . . . .  21
     6.2.  Device Profiles . . . . . . . . . . . . . . . . . . . . .  22
     6.3.  Application Profiles  . . . . . . . . . . . . . . . . . .  23
     6.4.  Verifying Profiles  . . . . . . . . . . . . . . . . . . .  23
     6.5.  Key Escrow and Recovery . . . . . . . . . . . . . . . . .  24
       6.5.1.  Offline Escrow  . . . . . . . . . . . . . . . . . . .  25
       6.5.2.  Online Escrow . . . . . . . . . . . . . . . . . . . .  25
   7.  The CryptoMesh  . . . . . . . . . . . . . . . . . . . . . . .  26
     7.1.  Federated Portals . . . . . . . . . . . . . . . . . . . .  26
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  27
Show full document text