Mathematical Mesh Reference July 2020
Hallam-Baker Expires January 28, 2021 [Page]
Workgroup:
Network Working Group
Stream:
Internet-Draft
Intended status:
Informational
Published:
ISSN:
2070-1721
Expires
Authors:
Phillip Hallam-Baker

Mathematical Mesh 3.0 Part IX: Considerations for Constrained Devices

draft-hallambaker-mesh-constrained-02

Abstract

The Mathematical Mesh ‘The Mesh’ is an infrastructure that facilitates the exchange of configuration and credential data between multiple user devices and provides end-to-end security. This document describes the

[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-constrained.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 http://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 January 28, 2021

Table of Contents

1. Introduction

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.

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 [RFC2119].

2.2. Defined Terms

The terms of art used in this document are described in the Mesh Architecture Guide [draft-hallambaker-mesh-architecture].

2.4. Implementation Status

The implementation status of the reference code base is described in the companion document [draft-hallambaker-mesh-developer].

3. Security Considerations

The security considerations for use and implementation of Mesh services and applications are described in the Mesh Security Considerations guide [draft-hallambaker-mesh-security].

4. IANA Considerations

All the IANA considerations for the Mesh documents are specified in this document

5. Acknowledgements

A list of people who have contributed to the design of the Mesh is presented in [draft-hallambaker-mesh-architecture].

References

Normative References

[RFC2119]
S. Bradner "Key words for use in RFCs to Indicate Requirement Levels" BCP 14 RFC 2119 DOI 10.17487/RFC2119
[draft-hallambaker-mesh-architecture]
Phillip Hallam-Baker "Mathematical Mesh 3.0 Part I: Architecture Guide" Internet-Draft draft-hallambaker-mesh-architecture-13 <http://www.ietf.org/internet-drafts/draft-hallambaker-mesh-architecture-13.txt>
[draft-hallambaker-mesh-security]
Phillip Hallam-Baker "Mathematical Mesh 3.0 Part VII: Security Considerations" Internet-Draft draft-hallambaker-mesh-security-04 <http://www.ietf.org/internet-drafts/draft-hallambaker-mesh-security-04.txt>

Informative References

[draft-hallambaker-mesh-developer]
Phillip Hallam-Baker "Mathematical Mesh: Reference Implementation" Internet-Draft draft-hallambaker-mesh-developer-09 <http://www.ietf.org/internet-drafts/draft-hallambaker-mesh-developer-09.txt>

Author's Address


Phillip Hallam-Baker
Email:
Prepared: Rendered: