idnits 2.17.1 draft-hallambaker-mesh-constrained-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Authors' Addresses Section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (2 November 2020) is 1271 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. M. Hallam-Baker 3 Internet-Draft 2 November 2020 4 Intended status: Informational 5 Expires: 6 May 2021 7 Mathematical Mesh 3.0 Part XIV: Considerations for Constrained Devices 8 draft-hallambaker-mesh-constrained-03 10 Abstract 12 The Mathematical Mesh 'The Mesh' is an infrastructure that 13 facilitates the exchange of configuration and credential data between 14 multiple user devices and provides end-to-end security. This 15 document describes the 17 [Note to Readers] 19 Discussion of this draft takes place on the MATHMESH mailing list 20 (mathmesh@ietf.org), which is archived at 21 https://mailarchive.ietf.org/arch/search/?email_list=mathmesh. 23 This document is also available online at 24 http://mathmesh.com/Documents/draft-hallambaker-mesh- 25 constrained.html. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on 6 May 2021. 44 Copyright Notice 46 Copyright (c) 2020 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 51 license-info) in effect on the date of publication of this document. 52 Please review these documents carefully, as they describe your rights 53 and restrictions with respect to this document. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 60 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 2 61 2.3. Related Specifications . . . . . . . . . . . . . . . . . 2 62 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3 63 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 65 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 66 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 67 7. Informative References . . . . . . . . . . . . . . . . . . . 3 69 1. Introduction 71 2. Definitions 73 This section presents the related specifications and standard, the 74 terms that are used as terms of art within the documents and the 75 terms used as requirements language. 77 2.1. Requirements Language 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in [RFC2119]. 83 2.2. Defined Terms 85 The terms of art used in this document are described in the _Mesh 86 Architecture Guide_ [draft-hallambaker-mesh-architecture]. 88 2.3. Related Specifications 90 The architecture of the Mathematical Mesh is described in the _Mesh 91 Architecture Guide_ [draft-hallambaker-mesh-architecture]. The Mesh 92 documentation set and related specifications are described in this 93 document. 95 2.4. Implementation Status 97 The implementation status of the reference code base is described in 98 the companion document [draft-hallambaker-mesh-developer]. 100 3. Security Considerations 102 The security considerations for use and implementation of Mesh 103 services and applications are described in the Mesh Security 104 Considerations guide [draft-hallambaker-mesh-security]. 106 4. IANA Considerations 108 All the IANA considerations for the Mesh documents are specified in 109 this document 111 5. Acknowledgements 113 A list of people who have contributed to the design of the Mesh is 114 presented in [draft-hallambaker-mesh-architecture]. 116 6. Normative References 118 [draft-hallambaker-mesh-architecture] 119 Hallam-Baker, P., "Mathematical Mesh 3.0 Part I: 120 Architecture Guide", Work in Progress, Internet-Draft, 121 draft-hallambaker-mesh-architecture-14, 27 July 2020, 122 . 125 [draft-hallambaker-mesh-security] 126 Hallam-Baker, P., "Mathematical Mesh 3.0 Part VII: 127 Security Considerations", Work in Progress, Internet- 128 Draft, draft-hallambaker-mesh-security-05, 27 July 2020, 129 . 132 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 133 Requirement Levels", BCP 14, RFC 2119, 134 DOI 10.17487/RFC2119, March 1997, 135 . 137 7. Informative References 139 [draft-hallambaker-mesh-developer] 140 Hallam-Baker, P., "Mathematical Mesh: Reference 141 Implementation", Work in Progress, Internet-Draft, draft- 142 hallambaker-mesh-developer-10, 27 July 2020, 143 .