| 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
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 .
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 (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 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.
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.
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.
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] .
The terms of art used in this document are described in the Mesh Architecture Guide [draft-hallambaker-mesh-architecture] .
The architecture of the Mathematical Mesh is described in the Mesh Architecture Guide [draft-hallambaker-mesh-architecture] . The Mesh documentation set and related specifications are described in this document.
The implementation status of the reference code base is described in the companion document [draft-hallambaker-mesh-developer] .
[Account request does not specify the portal in the request body, only the HTTP package includes this information. This is probably a bug.]
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 <username>@<domain> 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.
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.
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.]
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 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"
,
"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:
{
"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:
{
"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:
{
"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
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": []}}
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
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:
{
"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
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": {
"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:
{
"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
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.
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.
{
"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.
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.
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:
After the user verifies the device fingerprint as correct, the client posts a device connection request to the portal:
{
"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
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.
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
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
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
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
[Should probably unpack further.]
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:
{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()}
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:
{Point.Messages[0].String()}
The response indicates success or failure:
{Point.Messages[1].String()}
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).
The following classes are used as common elements in Mesh profile specifications.a
Most Mesh objects are signed and/or encrypted. For consistency all Mesh classes make use of the cryptographic data classes described in this section.
The PublicKey class is used to describe public key pairs and trust assertions associated with a public key.
Container for JOSE signed data and related attributes.
Container for JOSE encrypted data and related attributes.
Describes network connection parameters for an application
Base class for all Mesh Profile objects.
Contains a signed profile entry
Additional data bound to a signed profile that is not authenticated.
Parent class from which all profile types are derived
Contains a signed device profile
[No fields]
Describes a mesh device.
Private portion of device encryption profile.
Contains a signed Personal master profile
[No fields]
Describes the long term parameters associated with a personal profile.
Contains a signed Personal current profile
[No fields]
Describes the current applications and devices connected to a personal master profile.
Personal profile entry describing the privileges of specific devices.
Contains a signed device profile
[No fields]
Parent class from which all application profiles inherit.
[No fields]
The base class for all private profiles.
[No fields]
Describes the public per device data
Describes the private per device data
[No fields]
Contains escrowed data
Contains data escrowed using the offline escrow mechanism.
[No fields]
Contains data escrowed using the online escrow mechanism.
[No fields]
A set of escrowed keys.
[No fields]
Describes a connection request.
Contains a ConnectionRequest signed by the corresponding device signature key.
[No fields]
Describes the result of a connection request.
Contains a signed connection result
[No fields]
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.
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.
Base class for all request 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.
Base class for all response messages. Contains only the status code and status description fields.
[No fields]
The Mesh Service protocol makes use of JSON objects defined in the JOSE Signatgure and Encryption specifications.
The following common structures are used in the protocol messages:
Describes a Key/Value structure used to make queries for records matching one or more selection criteria.
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.
Report service and version information.
The Hello transaction provides a means of determining which protocol versions, message encodings and transport protocols are supported by the service.
Request validation of a proposed name for a new account.
For validation of a user's account name during profile creation.
Describes the proposed account properties. Currently, these are limited to the account name but could be extended in future versions of the protocol.
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 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.
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.
Request creation of a new portal account. The request specifies the requested account identifier and the Mesh profile to be associated with the account.
Reports the success or failure of a Create transaction.
[No fields]
Request deletion of a portal account.
Deletes a portal account but not the underlying profile. Once registered, profiles are permanent.
Request deletion of a new portal account. The request specifies the requested account identifier.
Reports the success or failure of a Delete transaction.
[No fields]
Search for data in the mesh that matches a set of properties described by a sequence of key/value pairs.
Describes the Portal or Mesh data to be retreived.
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.
Publish a profile or key escrow entry to the mesh.
Requests publication of the specified Mesh entry.
[No fields]
Reports the success or failure of a Publish transaction.
[No fields]
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]
Initiates a status transaction.
[No fields]
Reports the success or failure of a Status transaction.
Request connection of a new device to a mesh profile
Initial device connection request.
Reports the success or failure of a ConnectStart transaction.
[No fields]
Request status of pending connection request of a new device to a mesh profile
Request status information for a pending request posted previously.
Reports the success or failure of a ConnectStatus transaction.
Request a list of pending requests for an administration profile.
Specify the criteria for pending requests.
Reports the success or failure of a ConnectPending transaction.
Post response to a pending connection request.
Reports the success or failure of a ConnectComplete transaction.
Reports the success or failure of a ConnectComplete transaction.
[No fields]
Perform a bulk transfer of the log between the specified transaction identifiers. Requires appropriate authorization
[Not currently implemented]
Request a bulk transfer of the log between the specified transaction identifiers. Requires appropriate authorization
Reports the success or failure of a Transfer transaction. If successful, contains the list of Mesh records to be transferred.
All the IANA considerations for the Mesh documents are specified in this document
| [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. |
| [draft-hallambaker-mesh-architecture] | Hallam-Baker, P., "Mathematical Mesh: Architecture", Internet-Draft draft-hallambaker-mesh-architecture-03, May 2017. |
| [draft-hallambaker-mesh-developer] | Hallam-Baker, P., "Mathematical Mesh: Reference Implementation", Internet-Draft draft-hallambaker-mesh-developer-03, August 2017. |
| [RFC822] | Crocker, D., "STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES", STD 11, RFC 822, DOI 10.17487/RFC0822, August 1982. |