Network Working Group P. Hallam-Baker Internet-Draft Comodo Group Inc. Intended status: Informational September 18, 2017 Expires: March 22, 2018 Mathematical Mesh: Reference draft-hallambaker-mesh-reference-06 Abstract The Mathematical Mesh ?The Mesh? is an end-to-end secure infrastructure that facilitates the exchange of configuration and credential data between multiple user devices. The core protocols of the Mesh are described with examples of common use cases and reference data. This document is also available online at http://prismproof.org/Documents/draft-hallambaker-mesh-reference.html [1] . Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on March 22, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect Hallam-Baker Expires March 22, 2018 [Page 1] Internet-Draft Mathematical Mesh Reference September 2017 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Related Specifications . . . . . . . . . . . . . . . . . 5 2.4. Implementation Status . . . . . . . . . . . . . . . . . . 5 3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Creating a new portal account . . . . . . . . . . . . . . 5 3.1.1. Checking Account Identifier for uniqueness . . . . . 5 3.2. Creating a new user profile . . . . . . . . . . . . . . . 6 3.2.1. Publishing a new user profile . . . . . . . . . . . . 13 3.3. Connecting a device profile to a user profile . . . . . . 15 3.3.1. Profile Authentication . . . . . . . . . . . . . . . 17 3.3.2. Connection request . . . . . . . . . . . . . . . . . 20 3.3.3. Administrator Polls Pending Connections . . . . . . . 21 3.3.4. Administrator updates and publishes the personal profile. . . . . . . . . . . . . . . . . . . . . . . 23 3.3.5. Administrator posts completion request. . . . . . . . 24 3.3.6. Connecting device polls for status update. . . . . . 25 3.4. Adding an application profile to a user profile . . . . . 26 3.5. Creating a recovery profile . . . . . . . . . . . . . . . 27 3.6. Recovering a profile . . . . . . . . . . . . . . . . . . 28 4. Shared Classes . . . . . . . . . . . . . . . . . . . . . . . 28 4.1. Cryptographic Data Classes . . . . . . . . . . . . . . . 28 4.1.1. Structure: PublicKey . . . . . . . . . . . . . . . . 28 4.1.2. Structure: SignedData . . . . . . . . . . . . . . . . 29 4.1.3. Structure: EncryptedData . . . . . . . . . . . . . . 29 4.2. Common Application Classes . . . . . . . . . . . . . . . 29 4.2.1. Structure: Connection . . . . . . . . . . . . . . . . 29 5. Mesh Profile Objects . . . . . . . . . . . . . . . . . . . . 30 5.1. Base Profile Objects . . . . . . . . . . . . . . . . . . 30 5.1.1. Structure: Entry . . . . . . . . . . . . . . . . . . 30 5.1.2. Structure: SignedProfile . . . . . . . . . . . . . . 30 5.1.3. Structure: Advice . . . . . . . . . . . . . . . . . . 31 5.1.4. Structure: PortalAdvice . . . . . . . . . . . . . . . 31 5.1.5. Structure: Profile . . . . . . . . . . . . . . . . . 31 5.2. Device Profile Classes . . . . . . . . . . . . . . . . . 32 5.2.1. Structure: SignedDeviceProfile . . . . . . . . . . . 32 5.2.2. Structure: DeviceProfile . . . . . . . . . . . . . . 32 5.2.3. Structure: DevicePrivateProfile . . . . . . . . . . . 32 5.3. Master Profile Objects . . . . . . . . . . . . . . . . . 33 Hallam-Baker Expires March 22, 2018 [Page 2] Internet-Draft Mathematical Mesh Reference September 2017 5.3.1. Structure: SignedMasterProfile . . . . . . . . . . . 33 5.3.2. Structure: MasterProfile . . . . . . . . . . . . . . 33 5.4. Personal Profile Objects . . . . . . . . . . . . . . . . 33 5.4.1. Structure: SignedPersonalProfile . . . . . . . . . . 33 5.4.2. Structure: PersonalProfile . . . . . . . . . . . . . 34 5.4.3. Structure: ApplicationProfileEntry . . . . . . . . . 34 5.5. Application Profile Objects . . . . . . . . . . . . . . . 35 5.5.1. Structure: SignedApplicationProfile . . . . . . . . . 35 5.5.2. Structure: ApplicationProfile . . . . . . . . . . . . 35 5.5.3. Structure: ApplicationProfilePrivate . . . . . . . . 35 5.5.4. Structure: ApplicationDevicePublic . . . . . . . . . 35 5.5.5. Structure: ApplicationDevicePrivate . . . . . . . . . 35 5.6. Key Escrow Objects . . . . . . . . . . . . . . . . . . . 36 5.6.1. Structure: EscrowEntry . . . . . . . . . . . . . . . 36 5.6.2. Structure: OfflineEscrowEntry . . . . . . . . . . . . 36 5.6.3. Structure: OnlineEscrowEntry . . . . . . . . . . . . 36 5.6.4. Structure: EscrowedKeySet . . . . . . . . . . . . . . 36 6. Portal Connection . . . . . . . . . . . . . . . . . . . . . . 36 6.1. Connection Request and Response Structures . . . . . . . 36 6.1.1. Structure: ConnectionRequest . . . . . . . . . . . . 36 6.1.2. Structure: SignedConnectionRequest . . . . . . . . . 37 6.1.3. Structure: ConnectionResult . . . . . . . . . . . . . 37 6.1.4. Structure: SignedConnectionResult . . . . . . . . . . 37 7. Mesh Portal Service Reference . . . . . . . . . . . . . . . . 37 7.1. Request Messages . . . . . . . . . . . . . . . . . . . . 38 7.1.1. Message: MeshRequest . . . . . . . . . . . . . . . . 38 7.2. Response Messages . . . . . . . . . . . . . . . . . . . . 38 7.2.1. Message: MeshResponse . . . . . . . . . . . . . . . . 38 7.3. Imported Objects . . . . . . . . . . . . . . . . . . . . 38 7.4. Common Structures . . . . . . . . . . . . . . . . . . . . 38 7.4.1. Structure: KeyValue . . . . . . . . . . . . . . . . . 38 7.4.2. Structure: SearchConstraints . . . . . . . . . . . . 39 7.5. Transaction: Hello . . . . . . . . . . . . . . . . . . . 39 7.6. Transaction: ValidateAccount . . . . . . . . . . . . . . 40 7.6.1. Message: ValidateRequest . . . . . . . . . . . . . . 40 7.6.2. Message: ValidateResponse . . . . . . . . . . . . . . 40 7.7. Transaction: CreateAccount . . . . . . . . . . . . . . . 41 7.7.1. Message: CreateRequest . . . . . . . . . . . . . . . 41 7.7.2. Message: CreateResponse . . . . . . . . . . . . . . . 42 7.8. Transaction: DeleteAccount . . . . . . . . . . . . . . . 42 7.8.1. Message: DeleteRequest . . . . . . . . . . . . . . . 42 7.8.2. Message: DeleteResponse . . . . . . . . . . . . . . . 42 7.9. Transaction: Get . . . . . . . . . . . . . . . . . . . . 42 7.9.1. Message: GetRequest . . . . . . . . . . . . . . . . . 43 7.9.2. Message: GetResponse . . . . . . . . . . . . . . . . 43 7.10. Transaction: Publish . . . . . . . . . . . . . . . . . . 44 7.10.1. Message: PublishRequest . . . . . . . . . . . . . . 44 7.10.2. Message: PublishResponse . . . . . . . . . . . . . . 44 Hallam-Baker Expires March 22, 2018 [Page 3] Internet-Draft Mathematical Mesh Reference September 2017 7.11. Transaction: Status . . . . . . . . . . . . . . . . . . . 44 7.11.1. Message: StatusRequest . . . . . . . . . . . . . . . 44 7.11.2. Message: StatusResponse . . . . . . . . . . . . . . 45 7.12. Transaction: ConnectStart . . . . . . . . . . . . . . . . 45 7.12.1. Message: ConnectStartRequest . . . . . . . . . . . . 45 7.12.2. Message: ConnectStartResponse . . . . . . . . . . . 46 7.13. Transaction: ConnectStatus . . . . . . . . . . . . . . . 46 7.13.1. Message: ConnectStatusRequest . . . . . . . . . . . 46 7.13.2. Message: ConnectStatusResponse . . . . . . . . . . . 46 7.14. Transaction: ConnectPending . . . . . . . . . . . . . . . 46 7.14.1. Message: ConnectPendingRequest . . . . . . . . . . . 47 7.14.2. Message: ConnectPendingResponse . . . . . . . . . . 47 7.15. Transaction: ConnectComplete . . . . . . . . . . . . . . 47 7.15.1. Message: ConnectCompleteRequest . . . . . . . . . . 47 7.15.2. Message: ConnectCompleteResponse . . . . . . . . . . 48 7.16. Transaction: Transfer . . . . . . . . . . . . . . . . . . 48 7.16.1. Message: TransferRequest . . . . . . . . . . . . . . 48 7.16.2. Message: TransferResponse . . . . . . . . . . . . . 48 8. Security Considerations . . . . . . . . . . . . . . . . . . . 49 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 49 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 11.1. Normative References . . . . . . . . . . . . . . . . . . 49 11.2. Informative References . . . . . . . . . . . . . . . . . 49 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 50 1. Introduction NB: The reference material in this document is generated from the schema used to derive the source code. The tool used to create this material has not been optimized to produce output for the IETF documentation format at this time. Consequently, the formatting is currently sub-optimal. 2. Definitions This section presents the related specifications and standard, the terms that are used as terms of art within the documents and the terms used as requirements language. 2.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] [RFC2119] . Hallam-Baker Expires March 22, 2018 [Page 4] Internet-Draft Mathematical Mesh Reference September 2017 2.2. Defined Terms The terms of art used in this document are described in the Mesh Architecture Guide [draft-hallambaker-mesh-architecture] [draft-hallambaker-mesh-architecture] . 2.3. Related Specifications The architecture of the Mathematical Mesh is described in the Mesh Architecture Guide [draft-hallambaker-mesh-architecture] [draft-hallambaker-mesh-architecture] . The Mesh documentation set and related specifications are described in this document. 2.4. Implementation Status The implementation status of the reference code base is described in the companion document [draft-hallambaker-mesh-developer] [draft-hallambaker-mesh-developer] . 3. Protocol Overview [Account request does not specify the portal in the request body, only the HTTP package includes this information. This is probably a bug.] 3.1. Creating a new portal account A user interacts with a Mesh service through a Mesh portal provider with which she establishes a portal account. For user convenience, a portal account identifier has the familiar @ format established in [~RFC822]. For example Alice selects example.com as her portal provider and chooses the account name alice. Her portal account identifier is alice. A user MAY establish accounts with multiple portal providers and/or change their portal provider at any time they choose. 3.1.1. Checking Account Identifier for uniqueness The first step in creating a new account is to check to see if the chosen account identifier is available. This allows a client to validate user input and if necessary warn the user that they need to choose a new account identifier when the data is first entered. Hallam-Baker Expires March 22, 2018 [Page 5] Internet-Draft Mathematical Mesh Reference September 2017 The ValidateRequest message contains the requested account identifier and an optional language parameter to allow the service to provide informative error messages in a language the user understands. The Language field contains a list of ISO language identifier codes in order of preference, most preferred first. POST /.well-known/mmm/HTTP/1.1 Host: example.com Content-Length: 90 { "ValidateRequest": { "Account": "test@prismproof.org", "Language": ["en-uk"]}} Figure 1 The ValidateResponse message returns the result of the validation request in the Valid field. Note that even if the value true is returned, a subsequent account creation request MAY still fail. HTTP/1.1 200 OK Date: Mon 18 Sep 2017 04:26:53 Content-Length: 190 { "ValidateResponse": { "Status": 201, "StatusDescription": "Operation completed successfully", "Valid": true, "Minimum": 1, "InvalidCharacters": ".,:;{}()[]<>?|\\@#"}} Figure 2 [Note that for the sake of concise presentation, the HTTP binding information is omitted from future examples.] 3.2. Creating a new user profile The first step in creating a new personal profile is to create a Master Profile object. This contains the long term Master Signing Key that will remain constant for the life of the profile, at least one Online Signature Key to be used for administering the personal profile and (optionally), one or more master escrow keys. For convenience, the descriptions of the Master Signing Key, Online Signing Keys and Escrow Keys typically include PKIX certificates Hallam-Baker Expires March 22, 2018 [Page 6] Internet-Draft Mathematical Mesh Reference September 2017 signed by the Master Signing Key. This allows PKIX based applications to make use of PKIX certificate chains to express the same trust relationships described in the Mesh. { "MasterProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "MasterSignatureKey": { "UDF": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "X509Certificate": " MIIFXTCCBEWgAwIBAgIRAO4lVl8XvXHmnLVO7Y_uumowDQYJKoZIhvcNAQENBQAw LjEsMCoGA1UEAxYjTUNGUTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYw ... NpT-YZeFhK1Fa3AcuUBhoLDkrSnJFRHYj19JSHXFnzIt" , "PublicParameters": { "PublicKeyRSA": { "kid": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "n": " y0yq1NLVAEuZCzGPR_YFxJlvWH-QyiJOBhHeILjCoWYfoiQKp-FthIyK5EyWT_5T oRCdGMEh6rCkPpE369Ulx7hqvurhRW_XVXwojUox1afNW6QBu5S-usIeh0CGbRT8 v_fWefjtJQkfnv9o10zX93XMOnCC3t6R9L_apvFAvzqIjsAZWMuPcFlKBuRLXzSA e-fBS6GRPbhzK5pvtkcZ5VGoxMIDi7Lx0YCP9qIHXRIdeM5nn8uZxtgiz0llWokw Fr8y9KnnRHq2cYOcuOgGkfTf5PjExwG3dEvhFSUrLI4hQYHBmPS9nHsook4kyVWQ fzhh5mg9RxNanzXuB_nz1Q" , "e": " AQAB" }}}, "MasterEscrowKeys": [{ "UDF": "MBHK6-BY4CY-WV7QP-CRVLQ-KNTNY-ZIJ6F", "X509Certificate": " MIIFXTCCBEWgAwIBAgIRAI9a_sgdTt7vVulDCwV--skwDQYJKoZIhvcNAQENBQAw LjEsMCoGA1UEAxYjTUNGUTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYw ... FNm77_d-jSpmkGIBchbBNradXoBxC-cnZtz_TXXSFsVc" , "PublicParameters": { "PublicKeyRSA": { "kid": "MBHK6-BY4CY-WV7QP-CRVLQ-KNTNY-ZIJ6F", "n": " ufbxrsYOeupOcbyo0hxTAbvWNcD44YfAydFz6-ZSUSAEML9fUFkj4_n3gLz742Fm PKpmab3vaaKjq9LTt18oMKp2hqxh7xKxIaNzv5ABLpBBI9AQ5uSInivNxpd9I2Zb i7Up_8GNJwmfdPL0rGeUGyon0dyEGcj-s439NMhGXn-us1X61-jEAYDY_ObhQF7s 6OXC2uHQProd2GuDNvKRBSiTjV8pCu48dXg0N9tMICtvt3IEYR0S5nm4AWSYlQKy QY4QNQ5Blg6vzTycphe6aSu0DwAmvy4EznYaRhZnnYetLl5mD21Gr2wUwvwb-RrG YHREemz3cxvl35KKc59dBQ" , Hallam-Baker Expires March 22, 2018 [Page 7] Internet-Draft Mathematical Mesh Reference September 2017 "e": " AQAB" }}}], "OnlineSignatureKeys": [{ "UDF": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI", "X509Certificate": " MIIFXTCCBEWgAwIBAgIRAJxgDfp834fYUf5Y1XmzHnswDQYJKoZIhvcNAQENBQAw LjEsMCoGA1UEAxYjTUNGUTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYw ... 9BAdMXUcNhRSOTXdi1pjn9QYx86L8PxIcBcAvYQyDNfg" , "PublicParameters": { "PublicKeyRSA": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI", "n": " 0UWt5lAp-wVdch500PxJHgoxkwexryTteKVu7UEg7SS3Ig0rzwiZz0KgjpiGu09R WArK-JhpIcFFJjxMYUVAgL5xqWVC9JML8O6hj7bPjpjeUM0PTa5JcAKuMdXXzO-V 0tFvNeI_52qrZPEdCAXlaZmj4I85dsdtNyniXQgykePV9M5a7fI2M2wZ-8F-qEeL -C43w_g2W5zlK2LOpGR_UPpDH45p7VRN_WaV0Bzr11ZAIo1WYSovDJAMkMlOn_Zi uabgiVDFvIVOLR3kLzVB0j8S8abxxPiwD5vgwLuPu9q5FXfDzWJAd2gqw2mSYqFT dNrrr4W7pfwSTYOw8_bzQQ" , "e": " AQAB" }}}]}} Figure 3 The Master Profile is always signed using the Master Signing Key: Hallam-Baker Expires March 22, 2018 [Page 8] Internet-Draft Mathematical Mesh Reference September 2017 { "SignedMasterProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJNYXN0ZXJQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTUNGUTct TUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYiLAogICAgIk1hc3RlclNpZ25h ... QUIifX19XX19" , "signatures": [{ "header": { "kid": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCm9yQlJrRWIwTUduaGdQSUll eTFmam5QZkc2aFlXOXpjdkZ0MVpDMVlISVZDWUN4RjB1dlJQRHU2MVA5dnVVNmgK cnp1ZnhYU21nZWNqc0ZaTVgxY1g4USJ9" , "signature": " gnWbTtze2P981plb1yzdJumrQuyOZLf4jRTmiqZffg3gSpqtYPRCqidtJ6yqO7wN PTji2ecbWOYkqzppH9jUH5N5jjXkCR78lnBj7GSIfguQ6cFuOncpBEJ7Xs4lVU-h TP23yzVnhRKlFMthcthCJ5Yn1FuzX1oUYEAZPXUe64bURNRJxJkLpmECWRYl8IZa Sk3sotniX15EwbgWJbCRansOpFZzD44Ak4o1GwDYPKifvx9dmrbRXpBDQirpLCWE vANYSVVS74tCkPb0zbTI1qL6UQaCv4XV8pX7hQBpaG8KEn3wi9BujQtSJqG7zUN_ -6w6qYf8cC9SVUE3NQ_pgA" }]}}} Figure 4 Since the device used to create the personal profile is typically connected to the profile, a Device profile entry is created for it. This contains a Device Signing Key, a Device Encryption Key and a Device Authentication Key: Hallam-Baker Expires March 22, 2018 [Page 9] Internet-Draft Mathematical Mesh Reference September 2017 { "JoseWebSignature": { "unprotected": { "dig": "S512"}, "payload": " ewogICJEZXZpY2VQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTURCQTUt TFpMRFotTkdZWlQtUjdWMkUtQ09UMjctRVAyS1YiLAogICAgIk5hbWVzIjogWyJE ... VzRNU0dRIiwKICAgICAgICAgICJlIjogIgpBUUFCIn19fX19" , "signatures": [{ "header": { "kid": "MDBA5-LZLDZ-NGYZT-R7V2E-COT27-EP2KV"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmtLTzFNeGRHbXdHS2FnRTNZ X2ZWazltZENpTzMtS2xpUlZBX3d1Sm1DZ0JPN1J4bi12eVp6VjFmZG9ZU3h1c2YK MExVWGl2M2kzbkVIbkJDS0I0US04QSJ9" , "signature": " vI8ZRS0xegVWrQRXbytEL1Ooy509Bpo6lOu4zCQcoOpSDTIMkI3ovPei82YH1ar0 EPLibXUzfKqojQJTVnvpr57deSxcf_Y2v67cah1_OVyuIbZIw7Jd-0UjyHRlGbAd 6uXYXt37ocbd_KLvdjgNw-QHkdIdVhIoYJGYvliCNFbPIhqjIm1-DCrKeO_7MNRr oYbCTfDsnk6cHQi5JtDfqzyfyRWsr0untvw8G9EaHijellQUpu9HFwdJ-kVYwnOz 0G23Nxz0UCNMI2fXKHICs9B7vdxsZXj2LXeZu7SVmmqHRKM3sO7_DzA7cXdLSjvg SIB7D3V85pED_fcxpFGy7w" }]}} Figure 5 The Device Profile is signed using the Device Signing Key: Hallam-Baker Expires March 22, 2018 [Page 10] Internet-Draft Mathematical Mesh Reference September 2017 { "SignedDeviceProfile": { "Identifier": "MDBA5-LZLDZ-NGYZT-R7V2E-COT27-EP2KV", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJEZXZpY2VQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTURCQTUt TFpMRFotTkdZWlQtUjdWMkUtQ09UMjctRVAyS1YiLAogICAgIk5hbWVzIjogWyJE ... VzRNU0dRIiwKICAgICAgICAgICJlIjogIgpBUUFCIn19fX19" , "signatures": [{ "header": { "kid": "MDBA5-LZLDZ-NGYZT-R7V2E-COT27-EP2KV"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmtLTzFNeGRHbXdHS2FnRTNZ X2ZWazltZENpTzMtS2xpUlZBX3d1Sm1DZ0JPN1J4bi12eVp6VjFmZG9ZU3h1c2YK MExVWGl2M2kzbkVIbkJDS0I0US04QSJ9" , "signature": " vI8ZRS0xegVWrQRXbytEL1Ooy509Bpo6lOu4zCQcoOpSDTIMkI3ovPei82YH1ar0 EPLibXUzfKqojQJTVnvpr57deSxcf_Y2v67cah1_OVyuIbZIw7Jd-0UjyHRlGbAd 6uXYXt37ocbd_KLvdjgNw-QHkdIdVhIoYJGYvliCNFbPIhqjIm1-DCrKeO_7MNRr oYbCTfDsnk6cHQi5JtDfqzyfyRWsr0untvw8G9EaHijellQUpu9HFwdJ-kVYwnOz 0G23Nxz0UCNMI2fXKHICs9B7vdxsZXj2LXeZu7SVmmqHRKM3sO7_DzA7cXdLSjvg SIB7D3V85pED_fcxpFGy7w" }]}}} Figure 6 A personal profile would typically contain at least one application when first created. For the sake of demonstration, we will do this later. The personal profile thus consists of the master profile and the device profile: { "PersonalProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedMasterProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJNYXN0ZXJQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTUNGUTct Hallam-Baker Expires March 22, 2018 [Page 11] Internet-Draft Mathematical Mesh Reference September 2017 TUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYiLAogICAgIk1hc3RlclNpZ25h ... QUIifX19XX19" , "signatures": [{ "header": { "kid": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCm9yQlJrRWIwTUduaGdQSUll eTFmam5QZkc2aFlXOXpjdkZ0MVpDMVlISVZDWUN4RjB1dlJQRHU2MVA5dnVVNmgK cnp1ZnhYU21nZWNqc0ZaTVgxY1g4USJ9" , "signature": " gnWbTtze2P981plb1yzdJumrQuyOZLf4jRTmiqZffg3gSpqtYPRCqidtJ6yqO7wN PTji2ecbWOYkqzppH9jUH5N5jjXkCR78lnBj7GSIfguQ6cFuOncpBEJ7Xs4lVU-h TP23yzVnhRKlFMthcthCJ5Yn1FuzX1oUYEAZPXUe64bURNRJxJkLpmECWRYl8IZa Sk3sotniX15EwbgWJbCRansOpFZzD44Ak4o1GwDYPKifvx9dmrbRXpBDQirpLCWE vANYSVVS74tCkPb0zbTI1qL6UQaCv4XV8pX7hQBpaG8KEn3wi9BujQtSJqG7zUN_ -6w6qYf8cC9SVUE3NQ_pgA" }]}}, "Devices": [{ "Identifier": "MDBA5-LZLDZ-NGYZT-R7V2E-COT27-EP2KV", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJEZXZpY2VQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTURCQTUt TFpMRFotTkdZWlQtUjdWMkUtQ09UMjctRVAyS1YiLAogICAgIk5hbWVzIjogWyJE ... VzRNU0dRIiwKICAgICAgICAgICJlIjogIgpBUUFCIn19fX19" , "signatures": [{ "header": { "kid": "MDBA5-LZLDZ-NGYZT-R7V2E-COT27-EP2KV"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmtLTzFNeGRHbXdHS2FnRTNZ X2ZWazltZENpTzMtS2xpUlZBX3d1Sm1DZ0JPN1J4bi12eVp6VjFmZG9ZU3h1c2YK MExVWGl2M2kzbkVIbkJDS0I0US04QSJ9" , "signature": " vI8ZRS0xegVWrQRXbytEL1Ooy509Bpo6lOu4zCQcoOpSDTIMkI3ovPei82YH1ar0 EPLibXUzfKqojQJTVnvpr57deSxcf_Y2v67cah1_OVyuIbZIw7Jd-0UjyHRlGbAd 6uXYXt37ocbd_KLvdjgNw-QHkdIdVhIoYJGYvliCNFbPIhqjIm1-DCrKeO_7MNRr oYbCTfDsnk6cHQi5JtDfqzyfyRWsr0untvw8G9EaHijellQUpu9HFwdJ-kVYwnOz 0G23Nxz0UCNMI2fXKHICs9B7vdxsZXj2LXeZu7SVmmqHRKM3sO7_DzA7cXdLSjvg SIB7D3V85pED_fcxpFGy7w" }]}}], "Applications": []}} Hallam-Baker Expires March 22, 2018 [Page 12] Internet-Draft Mathematical Mesh Reference September 2017 Figure 7 The personal profile is then signed using the Online Signing Key: { "SignedPersonalProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJQZXJzb25hbFByb2ZpbGUiOiB7CiAgICAiSWRlbnRpZmllciI6ICJNQ0ZR Ny1NQVE3Ti1NVUU2SC03TDNLTC1NMzMzUS1CUFVFRiIsCiAgICAiU2lnbmVkTWFz ... dGlvbnMiOiBbXX19" , "signatures": [{ "header": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmF5NU1uQU1ORDA0ZWgzMEJf T3RQYnpLdFN6ekd4UW5LS0M3VnZqU1ZkUlhqM2dmQ3BOZHN2U2pSc1JqZGFFWDMK M2oxSnZ6SDJwYm03UmtZMHl6NzRNdyJ9" , "signature": " G6_MLrhberYQJTmEyBhlGgITkYNR5qYa-3Fnic0yF_npZOLBDiBzTblUOhxg0-4B firilJ6PWwb1FRc-GxakchPs4BY-Kn5s10Gbss0M6TAtRrejmvVtxplGgiXwI3am 00aNPryRO_134_d7DYePT_Er2X2ZEVX7_-M2dRogj7m-ldhXWBmZE5_ZOolqAe3a f6rLJNwdTmG8XDopNmYm-N8e3yOKMUWxpKa1oGAq1izvFJqtOSRSTn25AcX5fJDS wQpoGV2-4Pz2rQcAQ5-cIsoVFccWNIXxwKu7X9QVX-T21fEH-xot1oA03pxmzJgR -DV4r9e6Xn6wDvAUHSbsOg" }]}}} Figure 8 3.2.1. Publishing a new user profile Once the signed personal profile is created, the client can finaly make the request for the service to create the account. The request object contains the requested account identifier and profile: Hallam-Baker Expires March 22, 2018 [Page 13] Internet-Draft Mathematical Mesh Reference September 2017 { "CreateRequest": { "Account": "test@prismproof.org", "Profile": { "SignedPersonalProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJQZXJzb25hbFByb2ZpbGUiOiB7CiAgICAiSWRlbnRpZmllciI6ICJNQ0ZR Ny1NQVE3Ti1NVUU2SC03TDNLTC1NMzMzUS1CUFVFRiIsCiAgICAiU2lnbmVkTWFz ... dGlvbnMiOiBbXX19" , "signatures": [{ "header": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmF5NU1uQU1ORDA0ZWgzMEJf T3RQYnpLdFN6ekd4UW5LS0M3VnZqU1ZkUlhqM2dmQ3BOZHN2U2pSc1JqZGFFWDMK M2oxSnZ6SDJwYm03UmtZMHl6NzRNdyJ9" , "signature": " G6_MLrhberYQJTmEyBhlGgITkYNR5qYa-3Fnic0yF_npZOLBDiBzTblUOhxg0-4B firilJ6PWwb1FRc-GxakchPs4BY-Kn5s10Gbss0M6TAtRrejmvVtxplGgiXwI3am 00aNPryRO_134_d7DYePT_Er2X2ZEVX7_-M2dRogj7m-ldhXWBmZE5_ZOolqAe3a f6rLJNwdTmG8XDopNmYm-N8e3yOKMUWxpKa1oGAq1izvFJqtOSRSTn25AcX5fJDS wQpoGV2-4Pz2rQcAQ5-cIsoVFccWNIXxwKu7X9QVX-T21fEH-xot1oA03pxmzJgR -DV4r9e6Xn6wDvAUHSbsOg" }]}}}}} Figure 9 The service reports the success (or failure) of the account creation request: { "CreateResponse": { "Status": 201, "StatusDescription": "Operation completed successfully"}} Figure 10 Hallam-Baker Expires March 22, 2018 [Page 14] Internet-Draft Mathematical Mesh Reference September 2017 3.3. Connecting a device profile to a user profile Connecting a device to a profile requires the client on the new device to interact with a client on a device that has administration capabilities, i.e. it has access to an Online Signing Key. Since clients cannot interact directly with other clients, a service is required to mediate the connection. This service is provided by a Mesh portal provider. All service transactions are initiated by the clients. First the connecting device posts ConnectStart, after which it may poll for the outcome of the connection request using ConnectStatus. Periodically, the Administration Device polls for a list of pending connection requests using ConnectPending. After posting a request, the administration device posts the result using ConnectComplete: Connecting Mesh Administration Device Service Device | | | | ConnectStart | | | ----------------------> | | | | ConnectPending | | | <---------------------- | | | | | | ConnectComplete | | | <---------------------- | | ConnectStatus | | | ----------------------> | | Figure 11 The first step in the process is for the client to generate a device profile. Ideally the device profile is bound to the device in a read-only fashion such that applications running on the device can make use of the deencryption and authentication keys but these private keys cannot be extracted from the device: { "DeviceProfile": { "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "Names": ["Default"], "Description": "Unknown", "DeviceSignatureKey": { "UDF": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "PublicParameters": { "PublicKeyRSA": { Hallam-Baker Expires March 22, 2018 [Page 15] Internet-Draft Mathematical Mesh Reference September 2017 "kid": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "n": " xD8Id4Q0ejWFGam9SEsJnWcKumcCHyecfCDmCN8aqygbmcNgo-W4vBXs83eJ_qW7 uzoOJXdS5-5xMnsRK0C-ruCjRQEtbh0GHPqmssK8fWRGGAoyqN1tUMPlugavbyEE FQZHU5Zol7z9VxvpbQh1IwKmKcYt5TOFOz0z2f5HbnzMD2QoSgiK8kHUdJf8zStL 2JxjNIhpkBz2c8gU1hk4l4b-vpd4qDwRuqEb6Qty5flie2BzorTjLKv3AvvqhshA kUAPeHS4Bps1CgpHGqwmynsTkuGDlSCdQAIHfZ-tKMZN-fIWDeJiYa9GrUxCIXXg 11sxc0UjSZPwOYj_MTaRCQ" , "e": " AQAB" }}}, "DeviceAuthenticationKey": { "UDF": "MB4Z4-6UMPE-MNKFE-YDOZN-OBMAJ-UYYQ3", "PublicParameters": { "PublicKeyRSA": { "kid": "MB4Z4-6UMPE-MNKFE-YDOZN-OBMAJ-UYYQ3", "n": " xkXoHEnKaKb4EQF32NBkflUZUkEm1bo33Yzjto5ne0ZOlKQ0LGdZ6woTHMAQ7RRP Ad52om_qMecUohKyoRk9OutsLxqGWndPAdTZcNwm0sthVNNC4w3ZuyiRvrIAWB_e ymL591ZyLPSxqGpt57E3ajSN_Ao7ciLZ30_-eR_XKFsWx1acj78K-pW7sqoSMi5p 0NtIhnpLchcdrlGuAh9n0H0hI-31A_2baqX_AltGYcc4ZFLM8JYtm4ZN4jZHavTo DB3lIQH-dU9VCkL81jQ1OH1BpnhRaeu0yLCYbcaHM4woP4em3WgtxSLSqmLaPcnq iJ1Porcb3gJHZ0rly53s6Q" , "e": " AQAB" }}}, "DeviceEncryptiontionKey": { "UDF": "MAGB2-ANCIZ-O3GCH-DROQO-KIDPP-7E26X", "PublicParameters": { "PublicKeyRSA": { "kid": "MAGB2-ANCIZ-O3GCH-DROQO-KIDPP-7E26X", "n": " taTPTKcKxqeOk1t-6iiQ5A08u5sgVnM04K-Aj9_QbWR-xyMmfWnBKu_rNj06dMPI jlXSNzv9O7YCKvKaGSOh_uwVY3jvsgWwMmeVNG8VRqzDlMQ59J1wnjdJB-mctOBq Ka9Ce0sCzehdzrTK1a_BCWl7vLgszvL0IbLkw1l-dxrTRJ2MHU5BETq-npwasXBr 2h86eQ0b0Rlurr8gUc0I5e9GKP4tV4fqlnyqrCsXc_WtI2_5wmFD_5zb9nisL3t3 hvr5ukdlxtG0D4d1d-_ztgsk5GOWU9TPBQmYG6Xz23CmeWeeyCTBfSj8QlqfbkkT hUVPhYKz2E3k7c1oA47OrQ" , "e": " AQAB" }}}}} Figure 12 The device profile is then signed: Hallam-Baker Expires March 22, 2018 [Page 16] Internet-Draft Mathematical Mesh Reference September 2017 { "SignedDeviceProfile": { "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJEZXZpY2VQcm9maWxlIjogewogICAgIklkZW50aWZpZXIiOiAiTUNaS0kt T0tUUUYtTTNLUVktRktHVFUtVDNTT0ktSzMzSTMiLAogICAgIk5hbWVzIjogWyJE ... ICAgICAgICAgImUiOiAiCkFRQUIifX19fX0" , "signatures": [{ "header": { "kid": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjFsZkFIOHEwbGFVN0k2TkFw SDhxZkwyTEJ2azBEV3A5T1BDY1pwWnhsTC1iTi1ZUjhuQV8zanZIanlGNnBDN2oK SF8xREJ5WHdLVmhYWUFUM0FtMkVmdyJ9" , "signature": " D6zqFeO_RelamJq43ya9A3Qyfm67rffwgbGLgHSRECxTiQgTeoGHcKzeeUHvLyS5 XYEGR-CrNm65GTHJyfPcQGfV1qnCOd_BclzvfcBi5vJ1R9_m54IVwNvf5VlnGecT YSeCaTMLUsnags04dSV0nSXIWgMpYf8I9g4luq_KAuFedqJKHXUG4vmpR6gKsM_Q UT9ChhD2uK1Sql13lF9BYSKpkH6oRMLdWCTHuoQZ_MSU8d-BTQSYbwoRNMUHjhDc woUYQuXYM-eX5aM3v20qr86-JT7BUSM4XwH_Lf--eT4DQ8EabYgwKXmfzQDNG846 xkjV4ZUZdSOlvlSNiUAtag" }]}}} Figure 13 3.3.1. Profile Authentication One of the main architecutral principles of the Mesh is bilateral authentication. Every device that is connected to a Mesh profile MUST authenticate the profile it is connecting to and every Mesh profile administrator MUST authenticate devices that are connected. Having created the necessary profile, the device MUST verify that it is connecting to the correct Mesh profile. The best mechanism for achieving this purpose depends on the capabilities of the device being connected. The administration device obviously requires some means of communicating with the user to serve its function. But the device being connected may have a limited display capability or no user interaction capability at all. Hallam-Baker Expires March 22, 2018 [Page 17] Internet-Draft Mathematical Mesh Reference September 2017 3.3.1.1. Interactive Devices If the device has user input and display capabilities, it can verify that it is connecting to the correct display by first requesting the user enter the portal account of the profile they wish to connect to, retreiving the profile associated with the device and displaying the profile fingerprint. The client requests the profile for the requested account name: { "GetRequest": { "Account": "test@prismproof.org", "Multiple": false}} Figure 14 The response contains the requested profile information. Hallam-Baker Expires March 22, 2018 [Page 18] Internet-Draft Mathematical Mesh Reference September 2017 { "GetResponse": { "Status": 201, "StatusDescription": "Operation completed successfully", "Entries": [{ "SignedPersonalProfile": { "Identifier": "MCFQ7-MAQ7N-MUE6H-7L3KL-M333Q-BPUEF", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJQZXJzb25hbFByb2ZpbGUiOiB7CiAgICAiSWRlbnRpZmllciI6ICJNQ0ZR Ny1NQVE3Ti1NVUU2SC03TDNLTC1NMzMzUS1CUFVFRiIsCiAgICAiU2lnbmVkTWFz ... dGlvbnMiOiBbXX19" , "signatures": [{ "header": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCmF5NU1uQU1ORDA0ZWgzMEJf T3RQYnpLdFN6ekd4UW5LS0M3VnZqU1ZkUlhqM2dmQ3BOZHN2U2pSc1JqZGFFWDMK M2oxSnZ6SDJwYm03UmtZMHl6NzRNdyJ9" , "signature": " G6_MLrhberYQJTmEyBhlGgITkYNR5qYa-3Fnic0yF_npZOLBDiBzTblUOhxg0-4B firilJ6PWwb1FRc-GxakchPs4BY-Kn5s10Gbss0M6TAtRrejmvVtxplGgiXwI3am 00aNPryRO_134_d7DYePT_Er2X2ZEVX7_-M2dRogj7m-ldhXWBmZE5_ZOolqAe3a f6rLJNwdTmG8XDopNmYm-N8e3yOKMUWxpKa1oGAq1izvFJqtOSRSTn25AcX5fJDS wQpoGV2-4Pz2rQcAQ5-cIsoVFccWNIXxwKu7X9QVX-T21fEH-xot1oA03pxmzJgR -DV4r9e6Xn6wDvAUHSbsOg" }]}}}]}} Figure 15 Having received the profile data, the user can then verify that the device is attempting to connect to the correct profile by verifying that the fingerprint shown by the device attempting to connect is correct. 3.3.1.2. Constrained Interaction Devices Connection of an Internet of Things 'IoT' device that does not have the ability to accept user input requires a mechanism by which the user can identify the device they wish to connect to their profile and a mechanism to authenticate the profile to the device. Hallam-Baker Expires March 22, 2018 [Page 19] Internet-Draft Mathematical Mesh Reference September 2017 If the connecting device has a wired communication capability such as a USB port, this MAY be used to effect the device connection using a standardized interaction profile. But an increasing number of constrained IoT devices are only capable of wireless communication. Configuration of such devices for the purpose of the Mesh requires that we also consider configuration of the wireless networking capabilities at the same time. The precise mechanism by which this is achieved is therefore outside the scope of this particular document. However prototypes have been built and are being considered that make use of some or all of the following communication techniques: o Wired serial connection (RS232, RS485). o DHCP signalling. o Machine readable device identifiers (barcodes, QRCodes). o Default device profile installed during manufacture. o Optical communication path using camera on administrative device and status light on connecting device to communicate the device identifier, challenge nonce and confirm profile fingerprint. o Speech output on audio capable connecting device. 3.3.2. Connection request After the user verifies the device fingerprint as correct, the client posts a device connection request to the portal: Hallam-Baker Expires March 22, 2018 [Page 20] Internet-Draft Mathematical Mesh Reference September 2017 { "ConnectStartRequest": { "SignedRequest": { "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJDb25uZWN0aW9uUmVxdWVzdCI6IHsKICAgICJQYXJlbnRVREYiOiAiTUNG UTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYiLAogICAgIkRldmljZSI6 ... fX0sCiAgICAiRGV2aWNlRGF0YSI6IFtdfX0" , "signatures": [{ "header": { "kid": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjQ1dkRWQkg0VndGTHhWZ0lX VlI2MGxGSm1KY1B1aUI4aUo5V1g2TWhlSU9VZGZsUmtzcEQ2ZHpza3F1cjdWZC0K YVZyQ0lQR29jVldLVEF6OUFZN0U2QSJ9" , "signature": " kZn-7SOivXJjkhLiSZkz5KMM0X6dHnxNIvqIhBRMbldcmSGNadU3-pLz6UjHqMKR 1dYa4lmyPU1_9fv-z5T1JwCte5w7byv8HfJcqfbUgqtaVe5AIm7DugurvqKjOFb- uFM9FJKI356CuVJ4Qie7U_Xh3LJ0HJF5ipMWJOqskm2zh2DN7d3-hYGymwtEE8NZ _TqnmE1VlKZKUgnkrjFU1FgmAdBzp3zFJExFZzCOWcbxbqkohY3jiCIFecHqt8g7 RLSMqQST4VcL3KvIMLrvcXYdJGQixu_iFViMI66ijjdeuMaUHpK4NaMpMYk-0mcJ 65qFw1xv8rHL6S4QLdolng" }]}}, "AccountID": "test@prismproof.org"}} Figure 16 The portal verifies that the request is accepable and returns the transaction result: { "ConnectStartResponse": {}} Figure 17 3.3.3. Administrator Polls Pending Connections The client can poll the portal for the status of pending requests at any time (modulo any service throttling restrictions at the service side). But the request status will only change when an update is posted by an administration device. Hallam-Baker Expires March 22, 2018 [Page 21] Internet-Draft Mathematical Mesh Reference September 2017 Since the user is typically connecting a device to their profile, the next step in connecting the device is to start the administration client. When started, the client polls for pending connection requests using ConnectPendingRequest. { "ConnectPendingRequest": { "AccountID": "test@prismproof.org"}} Figure 18 The service responds with a list of pending requests: { "ConnectPendingResponse": { "Pending": [{ "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJDb25uZWN0aW9uUmVxdWVzdCI6IHsKICAgICJQYXJlbnRVREYiOiAiTUNG UTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYiLAogICAgIkRldmljZSI6 ... fX0sCiAgICAiRGV2aWNlRGF0YSI6IFtdfX0" , "signatures": [{ "header": { "kid": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjQ1dkRWQkg0VndGTHhWZ0lX VlI2MGxGSm1KY1B1aUI4aUo5V1g2TWhlSU9VZGZsUmtzcEQ2ZHpza3F1cjdWZC0K YVZyQ0lQR29jVldLVEF6OUFZN0U2QSJ9" , "signature": " kZn-7SOivXJjkhLiSZkz5KMM0X6dHnxNIvqIhBRMbldcmSGNadU3-pLz6UjHqMKR 1dYa4lmyPU1_9fv-z5T1JwCte5w7byv8HfJcqfbUgqtaVe5AIm7DugurvqKjOFb- uFM9FJKI356CuVJ4Qie7U_Xh3LJ0HJF5ipMWJOqskm2zh2DN7d3-hYGymwtEE8NZ _TqnmE1VlKZKUgnkrjFU1FgmAdBzp3zFJExFZzCOWcbxbqkohY3jiCIFecHqt8g7 RLSMqQST4VcL3KvIMLrvcXYdJGQixu_iFViMI66ijjdeuMaUHpK4NaMpMYk-0mcJ 65qFw1xv8rHL6S4QLdolng" }]}}]}} Figure 19 Hallam-Baker Expires March 22, 2018 [Page 22] Internet-Draft Mathematical Mesh Reference September 2017 3.3.4. Administrator updates and publishes the personal profile. The device profile is added to the Personal profile which is then signed by the online signing key. The administration client publishes the updated profile to the Mesh through the portal: { "ConnectPendingRequest": { "AccountID": "test@prismproof.org"}} Figure 20 As usual, the service returns the response code: { "ConnectPendingResponse": { "Pending": [{ "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJDb25uZWN0aW9uUmVxdWVzdCI6IHsKICAgICJQYXJlbnRVREYiOiAiTUNG UTctTUFRN04tTVVFNkgtN0wzS0wtTTMzM1EtQlBVRUYiLAogICAgIkRldmljZSI6 ... fX0sCiAgICAiRGV2aWNlRGF0YSI6IFtdfX0" , "signatures": [{ "header": { "kid": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjQ1dkRWQkg0VndGTHhWZ0lX VlI2MGxGSm1KY1B1aUI4aUo5V1g2TWhlSU9VZGZsUmtzcEQ2ZHpza3F1cjdWZC0K YVZyQ0lQR29jVldLVEF6OUFZN0U2QSJ9" , "signature": " kZn-7SOivXJjkhLiSZkz5KMM0X6dHnxNIvqIhBRMbldcmSGNadU3-pLz6UjHqMKR 1dYa4lmyPU1_9fv-z5T1JwCte5w7byv8HfJcqfbUgqtaVe5AIm7DugurvqKjOFb- uFM9FJKI356CuVJ4Qie7U_Xh3LJ0HJF5ipMWJOqskm2zh2DN7d3-hYGymwtEE8NZ _TqnmE1VlKZKUgnkrjFU1FgmAdBzp3zFJExFZzCOWcbxbqkohY3jiCIFecHqt8g7 RLSMqQST4VcL3KvIMLrvcXYdJGQixu_iFViMI66ijjdeuMaUHpK4NaMpMYk-0mcJ 65qFw1xv8rHL6S4QLdolng" }]}}]}} Figure 21 Hallam-Baker Expires March 22, 2018 [Page 23] Internet-Draft Mathematical Mesh Reference September 2017 3.3.5. Administrator posts completion request. Having accepted the device and connected it to the profile, the administration client creates and signs a connection completion result which is posted to the portal using ConnectCompleteRequest: { "ConnectCompleteRequest": { "Result": { "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJDb25uZWN0aW9uUmVzdWx0IjogewogICAgIkRldmljZSI6IHsKICAgICAg IklkZW50aWZpZXIiOiAiTUNaS0ktT0tUUUYtTTNLUVktRktHVFUtVDNTT0ktSzMz ... MnF6Clg0X0NwM1ltOTZoNjlLUXBiZUM0ZFEifV19fX19fQ" , "signatures": [{ "header": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjRkZEpmMF9Qc2FwZUVFMDJf SzdMT3FneUZrWC01YXdOLTBLQndvRnRoQ3diT1hnbXRDR2RadWt0bU9vT1YxUEEK U0xqc2RJX3R1QkRjQm9OSGg5VGRfZyJ9" , "signature": " R6KQt_WAF3uz5DWRCL6zYvLS8_VNbNvEO7L40jFunA0OwfuvojCnRAqXQaVOVJon hD9Q8gsjPt1nyQY0THJLGAv8SlQMlQ4L-l-PjNWhF0IVt9ZQe4AkDeV2Ua8sf2xA MahVApuqSs7Ut4OQJPQ8j_DxdWDPVzxABaOTclMOpwz0TTLy-r7IYYWob2y03nzV TSEeCgLTSkxAsEAAJqPxutMBDgzLO_-AfCYSNqHlMYqHdVVvLDUytQt1pYsTqL-5 57RcssggByeKv2Wm5v8NebgPuYJKlBPueFH6_5Koo_uFUPTU8aydrvVnBCLsm9pL 0OW9DQKR-xV4G9cXg6taOA" }]}}, "AccountID": "test@prismproof.org"}} Figure 22 Again, the service returns the response code: { "ConnectCompleteResponse": {}} Figure 23 Hallam-Baker Expires March 22, 2018 [Page 24] Internet-Draft Mathematical Mesh Reference September 2017 3.3.6. Connecting device polls for status update. As stated previously, the connecting device polls the portal periodically to determine the status of the pending request using ConnectStatusRequest: { "ConnectStatusRequest": { "AccountID": "test@prismproof.org", "DeviceID": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3"}} Figure 24 If the response is that the connection status has not changed, the service MAY return a response that specifies a minimum retry interval. In this case however there is a connection result: { "ConnectStatusResponse": { "Result": { "Identifier": "MCZKI-OKTQF-M3KQY-FKGTU-T3SOI-K33I3", "SignedData": { "unprotected": { "dig": "S512"}, "payload": " ewogICJDb25uZWN0aW9uUmVzdWx0IjogewogICAgIkRldmljZSI6IHsKICAgICAg IklkZW50aWZpZXIiOiAiTUNaS0ktT0tUUUYtTTNLUVktRktHVFUtVDNTT0ktSzMz ... MnF6Clg0X0NwM1ltOTZoNjlLUXBiZUM0ZFEifV19fX19fQ" , "signatures": [{ "header": { "kid": "MCURC-P23JV-PVSLE-JPPJO-65QB2-6BNEI"}, "protected": " ewogICJhbGciOiAiUlM1MTIiLAogICJ2YWwiOiAiCjRkZEpmMF9Qc2FwZUVFMDJf SzdMT3FneUZrWC01YXdOLTBLQndvRnRoQ3diT1hnbXRDR2RadWt0bU9vT1YxUEEK U0xqc2RJX3R1QkRjQm9OSGg5VGRfZyJ9" , "signature": " R6KQt_WAF3uz5DWRCL6zYvLS8_VNbNvEO7L40jFunA0OwfuvojCnRAqXQaVOVJon hD9Q8gsjPt1nyQY0THJLGAv8SlQMlQ4L-l-PjNWhF0IVt9ZQe4AkDeV2Ua8sf2xA MahVApuqSs7Ut4OQJPQ8j_DxdWDPVzxABaOTclMOpwz0TTLy-r7IYYWob2y03nzV TSEeCgLTSkxAsEAAJqPxutMBDgzLO_-AfCYSNqHlMYqHdVVvLDUytQt1pYsTqL-5 57RcssggByeKv2Wm5v8NebgPuYJKlBPueFH6_5Koo_uFUPTU8aydrvVnBCLsm9pL 0OW9DQKR-xV4G9cXg6taOA" }]}}}} Figure 25 Hallam-Baker Expires March 22, 2018 [Page 25] Internet-Draft Mathematical Mesh Reference September 2017 [Should probably unpack further.] 3.4. Adding an application profile to a user profile Application profiles are published separately from the personal profile to which they are linked. This allows a device to be given administration capability for a particular application without granting administration capability for the profile itself and the ability to connect additional profiles and devices. Another advantage of this separation is that an application profile might be managed by a separate party. In an enterprise, the application profile for a user's corporate email account could be managed by the corporate IT department. A user MAY have multiple application profiles for the same application. If a user has three email accounts, they would have three email application profiles, one for each account. In this example, the user has requested a PaswordProfile to be created. When populated, this records the usernames and passwords for the various Web sites that the user has created accounts at and has requested the Web browser store in the Mesh. Unlike a traditional password management service, the data stored the Password Profile is encrypted end to end and can only be decrypted by the devices that hold a decryption key. {Example.PasswordProfile1} Figure 26 The application profile is published to the Mesh in the same way as any other profile update, via a a Publish transaction: % Point = Example.Traces.Get (Example.LabelApplicationWeb1); {Point.Messages[0].String()} The service returns a status response. {Point.Messages[1].String()} Note that the degree of verification to be performed by the service when an application profile is published is an open question. Having created the application profile, the administration client adds it to the personal profile and publishes it: Hallam-Baker Expires March 22, 2018 [Page 26] Internet-Draft Mathematical Mesh Reference September 2017 {Point.Messages[0].String()} Note that if the publication was to happen in the reverse order, with the personal profile being published before the application profile, the personal profile might be rejected by the portal for inconsistency as it links to a non existent application profile. Though the value of such a check is debatable. It might well be preferable to not make such checks as it permits an application profile to have a degree of anonymity. {Point.Messages[1].String()} 3.5. Creating a recovery profile The Mesh invites users to put all their data eggs in one cryptographic basket. If the private keys in their master profile are lost, they could lose all their digital assets. The debate over the desirability of key escrow is a complex one. Not least because voluntary key escrow by the user to protect the user's digital assets is frequently conflated with mechanisms to support 'Lawful Access' through government managed backdoors. Accidents happen and so do disasters. For most users and most applications, data loss is a much more important concern than data disclosure. The option of using a robust key recovery mechanism is therefore essential for use of strong cryptography is to become ubiquitous. There are of course circumstances in which some users may prefer to risk losing some of their data rather than risk disclosure. Since any key recovery infrastructure necessarily introduces the risk of coercion, the choice of whether to use key recovery or not is left to the user to decide. The Mesh permits users to escrow their private keys in the Mesh itself in an OfflineEscrowEntry. Such entries are encrypted using the strongest degree of encryption available under a symmetric key. The symmetric key is then in turn split using Shamir secret sharing using an n of m threshold scheme. The OfflineEscrowEntry identifier is a UDF fingerprint of the symmetric key used to encrypt the data. This guarantees that a party that has the decryption key has the ability to locate the corresponding Escrow entry. The OfflineEscrowEntry is published using the usual Publish transaction: Hallam-Baker Expires March 22, 2018 [Page 27] Internet-Draft Mathematical Mesh Reference September 2017 {Point.Messages[0].String()} The response indicates success or failure: {Point.Messages[1].String()} 3.6. Recovering a profile To recover a profile, the user MUST supply the necessary number of secret shares. These are then used to calculate the UDF fingerprint to use as the locator in a Get transaction: {Point.Messages[0].String()} If the transaction succeeds, GetResponse is returned with the requested data. {Point.Messages[1].String()} The client can now decrypt the OfflineEscrowEntry to recover the private key(s). 4. Shared Classes The following classes are used as common elements in Mesh profile specifications.a 4.1. Cryptographic Data Classes Most Mesh objects are signed and/or encrypted. For consistency all Mesh classes make use of the cryptographic data classes described in this section. 4.1.1. Structure: PublicKey The PublicKey class is used to describe public key pairs and trust assertions associated with a public key. String (Optional) UDF fingerprint of the public key parameters/ Binary (Optional) List of X.509 Certificates Binary [0..Many] Hallam-Baker Expires March 22, 2018 [Page 28] Internet-Draft Mathematical Mesh Reference September 2017 X.509 Certificate chain. Binary (Optional) X.509 Certificate Signing Request. 4.1.2. Structure: SignedData Container for JOSE signed data and related attributes. Binary (Optional) The signed data 4.1.3. Structure: EncryptedData Container for JOSE encrypted data and related attributes. Binary (Optional) The encrypted data 4.2. Common Application Classes 4.2.1. Structure: Connection Describes network connection parameters for an application String (Optional) DNS address of the server Integer (Optional) TCP/UDP Port number String (Optional) DNS service prefix as described in [!RFC6335] String [0..Many] Describes the security mode to use. Valid choices are Direct/Upgrade/None String (Optional) Username to present to the service for authentication Hallam-Baker Expires March 22, 2018 [Page 29] Internet-Draft Mathematical Mesh Reference September 2017 String (Optional) Password to present to the service for authentication String (Optional) Service connection parameters in URI format String (Optional) List of the supported/acceptable authentication mechanisms, preferred mechanism first. Integer (Optional) Service timeout in seconds. Boolean (Optional) If set, the client should poll the specified service intermittently for updates. 5. Mesh Profile Objects 5.1. Base Profile Objects 5.1.1. Structure: Entry Base class for all Mesh Profile objects. String (Optional) Globally unique identifier that remains constant for the lifetime of the entry. 5.1.2. Structure: SignedProfile Entry Contains a signed profile entry JoseWebSignature (Optional) The signed profile. Note that each child of SignedProfile requires that the Payload field of the SignedData object contain an object of a specific Hallam-Baker Expires March 22, 2018 [Page 30] Internet-Draft Mathematical Mesh Reference September 2017 type. For example, a SignedDeviceProfile object MUST contain a Payload field that contains a DeviceProfile object. Advice (Optional) Additional data that is not authenticated. 5.1.3. Structure: Advice Additional data bound to a signed profile that is not authenticated. DateTime (Optional) If specified, the profile was the default profile at the specified date and time. The current default for that type of profile is the profile with the most recent Default timestamp. 5.1.4. Structure: PortalAdvice Advice String [0..Many] A portal address at which this profile is registered. 5.1.5. Structure: Profile Entry Parent class from which all profile types are derived String [0..Many] Fingerprints of index terms for profile retrieval. The use of the fingerprint of the name rather than the name itself is a precaution against enumeration attacks and other forms of abuse. DateTime (Optional) The time instant the profile was last modified. String (Optional) A Uniform Notary Token providing evidence that a signature was performed after the notary token was created. Hallam-Baker Expires March 22, 2018 [Page 31] Internet-Draft Mathematical Mesh Reference September 2017 5.2. Device Profile Classes 5.2.1. Structure: SignedDeviceProfile SignedProfile Contains a signed device profile [No fields] 5.2.2. Structure: DeviceProfile Profile Describes a mesh device. String (Optional) Description of the device PublicKey (Optional) Key used to sign certificates for the DAK and DEK. The fingerprint of the DSK is the UniqueID of the Device Profile PublicKey (Optional) Key used to authenticate requests made by the device. PublicKey (Optional) Key used to pass encrypted data to the device such as a DeviceUseEntry 5.2.3. Structure: DevicePrivateProfile Private portion of device encryption profile. Key (Optional) Private portion of the DeviceSignatureKey Key (Optional) Private portion of the DeviceAuthenticationKey Key (Optional) Hallam-Baker Expires March 22, 2018 [Page 32] Internet-Draft Mathematical Mesh Reference September 2017 Private portion of the DeviceEncryptiontionKey 5.3. Master Profile Objects 5.3.1. Structure: SignedMasterProfile SignedProfile Contains a signed Personal master profile [No fields] 5.3.2. Structure: MasterProfile Profile Describes the long term parameters associated with a personal profile. PublicKey (Optional) The root of trust for the Personal PKI, the public key of the PMSK is presented as a self-signed X.509v3 certificate with Certificate Signing use enabled. The PMSK is used to sign certificates for the PMEK, POSK and PKEK keys. PublicKey [0..Many] A Personal Profile MAY contain one or more PMEK keys to enable escrow of private keys used for stored data. PublicKey [0..Many] A Personal profile contains at least one POSK which is used to sign device administration application profiles. 5.4. Personal Profile Objects 5.4.1. Structure: SignedPersonalProfile SignedProfile Contains a signed Personal current profile [No fields] Hallam-Baker Expires March 22, 2018 [Page 33] Internet-Draft Mathematical Mesh Reference September 2017 5.4.2. Structure: PersonalProfile Profile Describes the current applications and devices connected to a personal master profile. SignedMasterProfile (Optional) The corresponding master profile. The profile MUST be signed by the PMSK. SignedDeviceProfile [0..Many] The set of device profiles connected to the profile. The profile MUST be signed by the DSK in the profile. ApplicationProfileEntry [0..Many] Application profiles connected to this profile. 5.4.3. Structure: ApplicationProfileEntry Personal profile entry describing the privileges of specific devices. String (Optional) The unique identifier of the application String (Optional) The application type String (Optional) Optional friendly name identifying the application. String [0..Many] List of devices authorized to sign application profiles String [0..Many] List of devices authorized to read private parts of application profiles. Hallam-Baker Expires March 22, 2018 [Page 34] Internet-Draft Mathematical Mesh Reference September 2017 5.5. Application Profile Objects 5.5.1. Structure: SignedApplicationProfile SignedProfile Contains a signed device profile [No fields] 5.5.2. Structure: ApplicationProfile Profile Parent class from which all application profiles inherit. [No fields] 5.5.3. Structure: ApplicationProfilePrivate Entry The base class for all private profiles. [No fields] 5.5.4. Structure: ApplicationDevicePublic Entry Describes the public per device data String (Optional) Description of the device for convenience of the user. String (Optional) Fingerprint of device that this key corresponds to. 5.5.5. Structure: ApplicationDevicePrivate Entry Describes the private per device data [No fields] Hallam-Baker Expires March 22, 2018 [Page 35] Internet-Draft Mathematical Mesh Reference September 2017 5.6. Key Escrow Objects 5.6.1. Structure: EscrowEntry Entry Contains escrowed data JoseWebEncryption (Optional) The encrypted escrow data 5.6.2. Structure: OfflineEscrowEntry EscrowEntry Contains data escrowed using the offline escrow mechanism. [No fields] 5.6.3. Structure: OnlineEscrowEntry EscrowEntry Contains data escrowed using the online escrow mechanism. [No fields] 5.6.4. Structure: EscrowedKeySet A set of escrowed keys. [No fields] 6. Portal Connection 6.1. Connection Request and Response Structures 6.1.1. Structure: ConnectionRequest Describes a connection request. String (Optional) UDF of Mesh Profile to which connection is requested. SignedDeviceProfile (Optional) Hallam-Baker Expires March 22, 2018 [Page 36] Internet-Draft Mathematical Mesh Reference September 2017 The Device profile to be connected 6.1.2. Structure: SignedConnectionRequest SignedProfile Contains a ConnectionRequest signed by the corresponding device signature key. [No fields] 6.1.3. Structure: ConnectionResult Describes the result of a connection request. ConnectionRequest String (Optional) The result of the connection request. Valid responses are: Accepted, Refused, Query. 6.1.4. Structure: SignedConnectionResult SignedProfile Contains a signed connection result [No fields] 7. Mesh Portal Service Reference _mmm._tcp /.well-known/mmm Every Mesh Portal Service transaction consists of exactly one request followed by exactly one response. Mesh Service transactions MAY cause modification of the data stored in the Mesh Portal or the Mesh itself but do not cause changes to the connection state. The protocol itself is thus idempotent. There is no set sequence in which operations are required to be performed. It is not necessary to perform a Hello transaction prior to a ValidateAccount, Publish or any other transaction. Hallam-Baker Expires March 22, 2018 [Page 37] Internet-Draft Mathematical Mesh Reference September 2017 7.1. Request Messages A Mesh Portal Service request consists of a payload object that inherits from the MeshRequest class. When using the HTTP binding, the request MUST specify the portal DNS address in the HTTP Host field. 7.1.1. Message: MeshRequest Base class for all request messages. String (Optional) Name of the Mesh Portal Service to which the request is directed. 7.2. Response Messages A Mesh Portal Service response consists of a payload object that inherits from the MeshResponse class. When using the HTTP binding, the response SHOULD report the Status response code in the HTTP response message. However the response code returned in the payload object MUST always be considered authoritative. 7.2.1. Message: MeshResponse Base class for all response messages. Contains only the status code and status description fields. [No fields] 7.3. Imported Objects The Mesh Service protocol makes use of JSON objects defined in the JOSE Signatgure and Encryption specifications. 7.4. Common Structures The following common structures are used in the protocol messages: 7.4.1. Structure: KeyValue Describes a Key/Value structure used to make queries for records matching one or more selection criteria. String (Optional) The data retrieval key. Hallam-Baker Expires March 22, 2018 [Page 38] Internet-Draft Mathematical Mesh Reference September 2017 String (Optional) The data value to match. 7.4.2. Structure: SearchConstraints Specifies constraints to be applied to a search result. These allow a client to limit the number of records returned, the quantity of data returned, the earliest and latest data returned, etc. DateTime (Optional) Only data published on or after the specified time instant is requested. DateTime (Optional) Only data published before the specified time instant is requested. This excludes data published at the specified time instant. Integer (Optional) Maximum number of data entries to return. Integer (Optional) Maximum number of data bytes to return. String (Optional) Specifies a page key returned in a previous search operation in which the number of responses exceeded the specified bounds. When a page key is specified, all the other search parameters except for MaxEntries and MaxBytes are ignored and the service returns the next set of data responding to the earlier query. 7.5. Transaction: Hello HelloRequest HelloResponse Report service and version information. Hallam-Baker Expires March 22, 2018 [Page 39] Internet-Draft Mathematical Mesh Reference September 2017 The Hello transaction provides a means of determining which protocol versions, message encodings and transport protocols are supported by the service. 7.6. Transaction: ValidateAccount ValidateRequest ValidateResponse Request validation of a proposed name for a new account. For validation of a user's account name during profile creation. 7.6.1. Message: ValidateRequest MeshRequest Describes the proposed account properties. Currently, these are limited to the account name but could be extended in future versions of the protocol. String (Optional) Account name requested Boolean (Optional) If true, request a reservation for the specified account name. Note that the service is not obliged to honor reservation requests. String [0..Many] List of ISO language codes in order of preference. For creating explanatory text. 7.6.2. Message: ValidateResponse MeshResponse States whether the proposed account properties are acceptable and (optional) returns an indication of what properties are valid. Note that receiving a 'Valid' responseto a Validate Request does not guarantee creation of the account. In addition to the possibility that the account namecould be requested by another user between the Validate and Create transactions, a portal service MAY perform more Hallam-Baker Expires March 22, 2018 [Page 40] Internet-Draft Mathematical Mesh Reference September 2017 stringent validation criteria when an account is actually being created. For example, checking with the authoritative list of current accounts rather than a cached copy. Boolean (Optional) If true, the specified account identifier is acceptable. If false, the account identifier is rejected. Integer (Optional) Specifies the minimum length of an account name. Integer (Optional) Specifies the maximum length of an account name. String (Optional) A list of characters that the service does not accept in account names. The list of characters MAY not be exhaustive but SHOULD include any illegal characters in the proposed account name. String (Optional) Text explaining the reason an account name was rejected. 7.7. Transaction: CreateAccount CreateRequest CreateResponse Request creation of a new portal account. Unlike a profile, a mesh account is specific to a particular Mesh portal. A mesh account must be created and accepted before a profile can be published. 7.7.1. Message: CreateRequest Request creation of a new portal account. The request specifies the requested account identifier and the Mesh profile to be associated with the account. MeshRequest String (Optional) Hallam-Baker Expires March 22, 2018 [Page 41] Internet-Draft Mathematical Mesh Reference September 2017 Account identifier requested. 7.7.2. Message: CreateResponse MeshResponse Reports the success or failure of a Create transaction. [No fields] 7.8. Transaction: DeleteAccount DeleteRequest DeleteResponse Request deletion of a portal account. Deletes a portal account but not the underlying profile. Once registered, profiles are permanent. 7.8.1. Message: DeleteRequest Request deletion of a new portal account. The request specifies the requested account identifier. MeshRequest String (Optional) Account identifier to be deleted. 7.8.2. Message: DeleteResponse MeshResponse Reports the success or failure of a Delete transaction. [No fields] 7.9. Transaction: Get GetRequest GetResponse Search for data in the mesh that matches a set of properties described by a sequence of key/value pairs. Hallam-Baker Expires March 22, 2018 [Page 42] Internet-Draft Mathematical Mesh Reference September 2017 7.9.1. Message: GetRequest Describes the Portal or Mesh data to be retreived. MeshRequest String (Optional) Lookup by profile ID String (Optional) Lookup by Account ID KeyValue [0..Many] List of KeyValue pairs specifying the conditions to be met SearchConstraints (Optional) Constrain the search to a specific time interval and/or limit the number and/or total size of data records returned. Boolean (Optional) If true return multiple responses if available Boolean (Optional) If true, the client requests that the full Mesh data record be returned containing both the Mesh entry itself and the Mesh metadata that allows the date and time of the publication of the Mesh entry to be verified. 7.9.2. Message: GetResponse Reports the success or failure of a Get transaction. If a Mesh entry matching the specified profile is found, containsthe list of entries matching the request. MeshResponse DataItem [0..Many] List of mesh data records matching the request. String (Optional) Hallam-Baker Expires March 22, 2018 [Page 43] Internet-Draft Mathematical Mesh Reference September 2017 If non-null, indicates that the number and/or size of the data records returned exceeds either the SearchConstraints specified in the request or internal server limits. 7.10. Transaction: Publish PublishRequest PublishResponse Publish a profile or key escrow entry to the mesh. 7.10.1. Message: PublishRequest Requests publication of the specified Mesh entry. MeshRequest [No fields] 7.10.2. Message: PublishResponse Reports the success or failure of a Publish transaction. MeshResponse [No fields] 7.11. Transaction: Status StatusRequest StatusResponse Request the current status of the mesh as seen by the portal to which it is directed. The response to the status request contains the last signed checkpoint and proof chains for each of the peer portals that have been checkpointed. [Not currently implemented] 7.11.1. Message: StatusRequest MeshRequest Initiates a status transaction. Hallam-Baker Expires March 22, 2018 [Page 44] Internet-Draft Mathematical Mesh Reference September 2017 [No fields] 7.11.2. Message: StatusResponse Reports the success or failure of a Status transaction. MeshResponse DateTime (Optional) Time that the last write update was made to the Mesh DateTime (Optional) Time that the last Mesh checkpoint was calculated. DateTime (Optional) Time at which the next Mesh checkpoint should be calculated. String (Optional) Last checkpoint value. 7.12. Transaction: ConnectStart ConnectStartRequest ConnectStartResponse Request connection of a new device to a mesh profile 7.12.1. Message: ConnectStartRequest MeshRequest Initial device connection request. SignedConnectionRequest (Optional) Device connection request signed by thesignature key of the device requesting connection. String (Optional) Account identifier of account to which the device is requesting connection. Hallam-Baker Expires March 22, 2018 [Page 45] Internet-Draft Mathematical Mesh Reference September 2017 7.12.2. Message: ConnectStartResponse Reports the success or failure of a ConnectStart transaction. MeshRequest [No fields] 7.13. Transaction: ConnectStatus ConnectStatusRequest ConnectStatusResponse Request status of pending connection request of a new device to a mesh profile 7.13.1. Message: ConnectStatusRequest MeshRequest Request status information for a pending request posted previously. String (Optional) Account identifier for which pending connection information is requested. String (Optional) Device identifier of device requesting status information. 7.13.2. Message: ConnectStatusResponse Reports the success or failure of a ConnectStatus transaction. MeshRequest SignedConnectionResult (Optional) The signed ConnectionResult object. 7.14. Transaction: ConnectPending ConnectPendingRequest ConnectPendingResponse Hallam-Baker Expires March 22, 2018 [Page 46] Internet-Draft Mathematical Mesh Reference September 2017 Request a list of pending requests for an administration profile. 7.14.1. Message: ConnectPendingRequest MeshRequest Specify the criteria for pending requests. String (Optional) The account identifier of the account for which pending connection requests are requested. SearchConstraints (Optional) Constrain the search to a specific time interval and/or limit the number and/or total size of data records returned. 7.14.2. Message: ConnectPendingResponse Reports the success or failure of a ConnectPending transaction. MeshRequest SignedConnectionRequest [0..Many] A list of pending requests satisfying the criteria set out in the request. String (Optional) If non-null, indicates that the number and/or size of the data records returned exceeds either the SearchConstraints specified in the request or internal server limits. 7.15. Transaction: ConnectComplete ConnectCompleteRequest ConnectCompleteResponse Post response to a pending connection request. 7.15.1. Message: ConnectCompleteRequest Reports the success or failure of a ConnectComplete transaction. MeshRequest Hallam-Baker Expires March 22, 2018 [Page 47] Internet-Draft Mathematical Mesh Reference September 2017 SignedConnectionResult (Optional) The connection result to be posted to the portal. The result MUST be signed by a valid administration key for the Mesh profile. String (Optional) The account identifier to which the connection result is posted. 7.15.2. Message: ConnectCompleteResponse MeshRequest Reports the success or failure of a ConnectComplete transaction. [No fields] 7.16. Transaction: Transfer TransferRequest TransferResponse Perform a bulk transfer of the log between the specified transaction identifiers. Requires appropriate authorization [Not currently implemented] 7.16.1. Message: TransferRequest Request a bulk transfer of the log between the specified transaction identifiers. Requires appropriate authorization MeshRequest SearchConstraints (Optional) Constrain the search to a specific time interval and/or limit the number and/or total size of data records returned. 7.16.2. Message: TransferResponse MeshResponse Reports the success or failure of a Transfer transaction. If successful, contains the list of Mesh records to be transferred. DataItem [0..Many] Hallam-Baker Expires March 22, 2018 [Page 48] Internet-Draft Mathematical Mesh Reference September 2017 List of mesh data records matching the request. String (Optional) If non-null, indicates that the number and/or size of the data records returned exceeds either the SearchConstraints specified in the request or internal server limits. 8. Security Considerations 9. IANA Considerations All the IANA considerations for the Mesh documents are specified in this document 10. Acknowledgements 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. Cheshire, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry", BCP 165, RFC 6335, DOI 10.17487/RFC6335, August 2011. 11.2. Informative References [draft-hallambaker-mesh-architecture] Hallam-Baker, P., "Mathematical Mesh: Architecture", draft-hallambaker-mesh-architecture-03 (work in progress), May 2017. [draft-hallambaker-mesh-developer] Hallam-Baker, P., "Mathematical Mesh: Reference Implementation", draft-hallambaker-mesh-developer-03 (work in progress), August 2017. [RFC822] Crocker, D., "STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES", STD 11, RFC 822, DOI 10.17487/RFC0822, August 1982. Hallam-Baker Expires March 22, 2018 [Page 49] Internet-Draft Mathematical Mesh Reference September 2017 11.3. URIs [1] http://prismproof.org/Documents/draft-hallambaker-mesh- reference.html Author's Address Phillip Hallam-Baker Comodo Group Inc. Email: philliph@comodo.com Hallam-Baker Expires March 22, 2018 [Page 50]