Mathematical Mesh: Platform Configuration
draft-hallambaker-mesh-platform-06
Network Working Group P. M. Hallam-Baker
Internet-Draft 27 July 2020
Intended status: Informational
Expires: 28 January 2021
Mathematical Mesh: Platform Configuration
draft-hallambaker-mesh-platform-06
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. This document
describes how Mesh profiles are stored for application access on
Windows, Linux and OSX platforms.
This document is also available online at
http://prismproof.org/Documents/draft-hallambaker-mesh-platform.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 28 January 2021.
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.
Hallam-Baker Expires 28 January 2021 [Page 1]
Internet-Draft Mathematical Mesh Platform Configuration July 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Related Specifications . . . . . . . . . . . . . . . . . 3
2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3
3. Mesh Content . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Directory Layout . . . . . . . . . . . . . . . . . . . . 3
3.1.1. CatalogHost . . . . . . . . . . . . . . . . . . . . . 3
3.1.2. CatalogDevice . . . . . . . . . . . . . . . . . . . . 4
3.1.3. CatalogApplication . . . . . . . . . . . . . . . . . 4
3.1.4. CatalogContact . . . . . . . . . . . . . . . . . . . 4
3.1.5. CatalogRecrypt . . . . . . . . . . . . . . . . . . . 4
3.2. Container Locking . . . . . . . . . . . . . . . . . . . . 4
4. Platform Specific Bindings . . . . . . . . . . . . . . . . . 5
4.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. OSX . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
8. Informative References . . . . . . . . . . . . . . . . . . . 5
1. Introduction
This document describes recommended platform specific configuration
for Mathematical Mesh applications. The use of common conventions
for storage of profiles and private keys allows mesh enabled
applications to interoperate on the same machine.
Protecting private key material from disclosure to other processes
presents complex and difficult technical challenges. Ensuring that a
key is properly erased from storage before memory is released relies
on a complex series of assumptions about memory management at the
compiler, operating system and the platform level.
For maximum security, the use of private key storage facilities
provided by the platform is preferred.
2. Definitions
This section presents the related specifications and standard, the
terms that are used as terms of art within the documents and the
terms used as requirements language.
Hallam-Baker Expires 28 January 2021 [Page 2]
Internet-Draft Mathematical Mesh Platform Configuration July 2020
2.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text