idnits 2.17.1 draft-hallambaker-mesh-services-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 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 (27 July 2020) is 1367 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 Venture Cryptography. 4 Intended status: Informational 27 July 2020 5 Expires: 28 January 2021 7 Mathematical Mesh 3.0 Part XI: Cryptographic Services 8 draft-hallambaker-mesh-services-00 10 Abstract 12 https://mailarchive.ietf.org/arch/browse/mathmesh/ 13 (http://whatever)Discussion of this draft should take place on the 14 MathMesh mailing list (mathmesh@ietf.org), which is archived at . 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on 28 January 2021. 33 Copyright Notice 35 Copyright (c) 2020 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 47 1.1. Time Service . . . . . . . . . . . . . . . . . . . . . . 2 48 1.2. Notary Service . . . . . . . . . . . . . . . . . . . . . 2 49 1.2.1. Create Entry . . . . . . . . . . . . . . . . . . . . 2 50 1.2.2. Validate Entry . . . . . . . . . . . . . . . . . . . 2 51 1.3. Decryption Service . . . . . . . . . . . . . . . . . . . 2 52 1.4. Discovery Service . . . . . . . . . . . . . . . . . . . . 2 53 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 55 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 3 56 2.3. Related Specifications . . . . . . . . . . . . . . . . . 3 57 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3 58 3. Notary Service . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Broker Service . . . . . . . . . . . . . . . . . . . . . . . 3 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 62 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 63 8. Normative References . . . . . . . . . . . . . . . . . . . . 3 64 9. Informative References . . . . . . . . . . . . . . . . . . . 3 66 1. Introduction 68 1.1. Time Service 70 1.2. Notary Service 72 1.2.1. Create Entry 74 1.2.2. Validate Entry 76 1.3. Decryption Service 78 1.4. Discovery Service 80 2. Definitions 82 This section presents the related specifications and standard, the 83 terms that are used as terms of art within the documents and the 84 terms used as requirements language. 86 2.1. Requirements Language 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in [RFC2119]. 92 2.2. Defined Terms 94 2.3. Related Specifications 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. Notary Service 103 4. Broker Service 105 5. Security Considerations 107 6. IANA Considerations 109 This document requires no IANA actions. 111 7. Acknowledgements 113 8. Normative References 115 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 116 Requirement Levels", BCP 14, RFC 2119, 117 DOI 10.17487/RFC2119, March 1997, 118 . 120 9. Informative References 122 [draft-hallambaker-mesh-developer] 123 Hallam-Baker, P., "Mathematical Mesh: Reference 124 Implementation", Work in Progress, Internet-Draft, draft- 125 hallambaker-mesh-developer-09, 23 October 2019, 126 .