idnits 2.17.1 draft-hallambaker-mesh-constrained-01.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 (October 23, 2019) is 1640 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 150 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 October 23, 2019 4 Intended status: Informational 5 Expires: April 25, 2020 7 Mathematical Mesh 3.0 Part IX: Considerations for Constrained Devices 8 draft-hallambaker-mesh-constrained-01 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-constrained.html 25 [1] . 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 April 25, 2020. 44 Copyright Notice 46 Copyright (c) 2019 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 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 64 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 2 65 2.3. Related Specifications . . . . . . . . . . . . . . . . . 3 66 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3 67 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 68 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 69 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 72 6.2. Informative References . . . . . . . . . . . . . . . . . 4 73 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 76 1. Introduction 78 2. Definitions 80 This section presents the related specifications and standard, the 81 terms that are used as terms of art within the documents and the 82 terms used as requirements language. 84 2.1. Requirements Language 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in [RFC2119] . 90 2.2. Defined Terms 92 The terms of art used in this document are described in the Mesh 93 Architecture Guide [draft-hallambaker-mesh-architecture] . 95 2.3. Related Specifications 97 The architecture of the Mathematical Mesh is described in the Mesh 98 Architecture Guide [draft-hallambaker-mesh-architecture] . The Mesh 99 documentation set and related specifications are described in this 100 document. 102 2.4. Implementation Status 104 The implementation status of the reference code base is described in 105 the companion document [draft-hallambaker-mesh-developer] . 107 3. Security Considerations 109 The security considerations for use and implementation of Mesh 110 services and applications are described in the Mesh Security 111 Considerations guide [draft-hallambaker-mesh-security] . 113 4. IANA Considerations 115 All the IANA considerations for the Mesh documents are specified in 116 this document 118 5. Acknowledgements 120 A list of people who have contributed to the design of the Mesh is 121 presented in [draft-hallambaker-mesh-architecture] . 123 6. References 125 6.1. Normative References 127 [draft-hallambaker-mesh-architecture] 128 Hallam-Baker, P., "Mathematical Mesh 3.0 Part I: 129 Architecture Guide", draft-hallambaker-mesh- 130 architecture-10 (work in progress), August 2019. 132 [draft-hallambaker-mesh-security] 133 Hallam-Baker, P., "Mathematical Mesh Part VII: Security 134 Considerations", draft-hallambaker-mesh-security-01 (work 135 in progress), July 2019. 137 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 138 Requirement Levels", BCP 14, RFC 2119, 139 DOI 10.17487/RFC2119, March 1997. 141 6.2. Informative References 143 [draft-hallambaker-mesh-developer] 144 Hallam-Baker, P., "Mathematical Mesh: Reference 145 Implementation", draft-hallambaker-mesh-developer-08 (work 146 in progress), April 2019. 148 6.3. URIs 150 [1] http://mathmesh.com/Documents/draft-hallambaker-mesh- 151 constrained.html 153 Author's Address 155 Phillip Hallam-Baker 157 Email: phill@hallambaker.com