idnits 2.17.1 draft-hallambaker-mesh-constrained-00.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 abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (April 4, 2019) is 1839 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 143 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hallam-Baker 3 Internet-Draft April 4, 2019 4 Intended status: Informational 5 Expires: October 6, 2019 7 Mathematical Mesh Part IX: Considerations for use on Constrained Devices 8 draft-hallambaker-mesh-constrained-00 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 This document is also available online at 18 http://mathmesh.com/Documents/draft-hallambaker-mesh-constrained.html 19 [1] . 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on October 6, 2019. 38 Copyright Notice 40 Copyright (c) 2019 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 58 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 2 59 2.3. Related Specifications . . . . . . . . . . . . . . . . . 2 60 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3 61 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 62 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 63 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 66 6.2. Informative References . . . . . . . . . . . . . . . . . 3 67 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 70 1. Introduction 72 2. Definitions 74 This section presents the related specifications and standard, the 75 terms that are used as terms of art within the documents and the 76 terms used as requirements language. 78 2.1. Requirements Language 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [RFC2119] . 84 2.2. Defined Terms 86 The terms of art used in this document are described in the Mesh 87 Architecture Guide [draft-hallambaker-mesh-architecture] . 89 2.3. Related Specifications 91 The architecture of the Mathematical Mesh is described in the Mesh 92 Architecture Guide [draft-hallambaker-mesh-architecture] . The Mesh 93 documentation set and related specifications are described in this 94 document. 96 2.4. Implementation Status 98 The implementation status of the reference code base is described in 99 the companion document [draft-hallambaker-mesh-developer] . 101 3. Security Considerations 103 The security considerations for use and implementation of Mesh 104 services and applications are described in the Mesh Security 105 Considerations guide [draft-hallambaker-mesh-security] . 107 4. IANA Considerations 109 All the IANA considerations for the Mesh documents are specified in 110 this document 112 5. Acknowledgements 114 Thanks are due to Viktor Dukhovni, Damian Weber and an anonymous 115 member of the cryptography@metzdowd.com list for assisting in the 116 compilation of the table of prime values. 118 6. References 120 6.1. Normative References 122 [draft-hallambaker-mesh-security] 123 "[Reference Not Found!]". 125 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 126 Requirement Levels", BCP 14, RFC 2119, 127 DOI 10.17487/RFC2119, March 1997. 129 6.2. Informative References 131 [draft-hallambaker-mesh-architecture] 132 Hallam-Baker, P., "Mathematical Mesh Part I: Architecture 133 Guide", draft-hallambaker-mesh-architecture-06 (work in 134 progress), August 2018. 136 [draft-hallambaker-mesh-developer] 137 Hallam-Baker, P., "Mathematical Mesh: Reference 138 Implementation", draft-hallambaker-mesh-developer-07 (work 139 in progress), April 2018. 141 6.3. URIs 143 [1] http://mathmesh.com/Documents/draft-hallambaker-mesh- 144 constrained.html 146 Author's Address 148 Phillip Hallam-Baker 150 Email: phill@hallambaker.com