idnits 2.17.1 draft-hallambaker-mesh-ceremonies-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 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 (9 March 2020) is 1499 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 ThresholdSecrets.com 4 Intended status: Informational 9 March 2020 5 Expires: 10 September 2020 7 Mathematical Mesh 3.0 Part XIII: Mesh Ceremonies 8 draft-hallambaker-mesh-ceremonies-01 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 10 September 2020. 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 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2 48 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 49 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 2 50 2.3. Related Specifications . . . . . . . . . . . . . . . . . 2 51 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3 52 3. Device Onboarding Ceremonies . . . . . . . . . . . . . . . . 3 53 3.1. Networked Desktop to Desktop (Fingerprint 54 Verification) . . . . . . . . . . . . . . . . . . . . . . 3 55 3.2. Networked Mobile to Desktop (Dynamic QR Code) . . . . . . 3 56 3.3. Pre-Networked Mobile to Mobile (Dynamic QR Code) . . . . 3 57 3.4. Pre-Networked Headless Device to Mobile (Static QR 58 Code) . . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3.5. Mobile proxy to Desktop . . . . . . . . . . . . . . . . . 3 60 4. Contact Establishment Ceremonies . . . . . . . . . . . . . . 3 61 4.1. In Person . . . . . . . . . . . . . . . . . . . . . . . . 3 62 4.2. Remote . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4.3. Registration . . . . . . . . . . . . . . . . . . . . . . 3 64 4.4. Trusted Third Party Endorsement . . . . . . . . . . . . . 3 65 5. Authentication Ceremonies . . . . . . . . . . . . . . . . . . 3 66 5.1. Second Factor Authentication . . . . . . . . . . . . . . 3 67 5.2. Confirmation . . . . . . . . . . . . . . . . . . . . . . 3 68 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 70 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 71 9. Normative References . . . . . . . . . . . . . . . . . . . . 3 72 10. Informative References . . . . . . . . . . . . . . . . . . . 4 74 1. Introduction 76 2. Definitions 78 This section presents the related specifications and standard, the 79 terms that are used as terms of art within the documents and the 80 terms used as requirements language. 82 2.1. Requirements Language 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC2119]. 88 2.2. Defined Terms 90 2.3. Related Specifications 91 2.4. Implementation Status 93 The implementation status of the reference code base is described in 94 the companion document [draft-hallambaker-mesh-developer]. 96 3. Device Onboarding Ceremonies 98 3.1. Networked Desktop to Desktop (Fingerprint Verification) 100 3.2. Networked Mobile to Desktop (Dynamic QR Code) 102 3.3. Pre-Networked Mobile to Mobile (Dynamic QR Code) 104 3.4. Pre-Networked Headless Device to Mobile (Static QR Code) 106 3.5. Mobile proxy to Desktop 108 4. Contact Establishment Ceremonies 110 4.1. In Person 112 4.2. Remote 114 4.3. Registration 116 4.4. Trusted Third Party Endorsement 118 5. Authentication Ceremonies 120 5.1. Second Factor Authentication 122 5.2. Confirmation 124 6. Security Considerations 126 7. IANA Considerations 128 This document requires no IANA actions. 130 8. Acknowledgements 132 9. Normative References 134 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 135 Requirement Levels", BCP 14, RFC 2119, 136 DOI 10.17487/RFC2119, March 1997, 137 . 139 10. Informative References 141 [draft-hallambaker-mesh-developer] 142 Hallam-Baker, P., "Mathematical Mesh: Reference 143 Implementation", Work in Progress, Internet-Draft, draft- 144 hallambaker-mesh-developer-09, 23 October 2019, 145 .