Network Working Group P. Hallam-Baker
Internet-Draft April 4, 2019
Intended status: Informational
Expires: October 6, 2019
Mathematical Mesh Part IV: Schema Reference
draft-hallambaker-mesh-schema-00
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://mathmesh.com/Documents/draft-hallambaker-mesh-schema.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 October 6, 2019.
Copyright Notice
Copyright (c) 2019 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 October 6, 2019 [Page 1]
Internet-Draft Mesh Schema Reference April 2019
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 . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Related Specifications . . . . . . . . . . . . . . . . . 4
2.4. Implementation Status . . . . . . . . . . . . . . . . . . 5
3. Mesh Profiles . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Master Profile . . . . . . . . . . . . . . . . . . . . . 5
3.2. Device Profile . . . . . . . . . . . . . . . . . . . . . 5
3.3. Mesh Profile . . . . . . . . . . . . . . . . . . . . . . 5
4. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Data Model . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Objects . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Catalogs . . . . . . . . . . . . . . . . . . . . . . 6
4.1.3. Spools . . . . . . . . . . . . . . . . . . . . . . . 6
5. Catalog Entries . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Device . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3. Credential . . . . . . . . . . . . . . . . . . . . . . . 6
5.4. Network . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.5. Bookmark . . . . . . . . . . . . . . . . . . . . . . . . 6
5.6. Task . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.7. Application . . . . . . . . . . . . . . . . . . . . . . . 6
5.7.1. SSH . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.7.2. Mail . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Completion . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Connection . . . . . . . . . . . . . . . . . . . . . . . 7
6.3. Contact . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.4. Confirmation . . . . . . . . . . . . . . . . . . . . . . 7
7. Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Shared Classes . . . . . . . . . . . . . . . . . . . . . 7
7.1.1. Structure: PublicKey . . . . . . . . . . . . . . . . 7
7.2. Mesh Profile Objects . . . . . . . . . . . . . . . . . . 8
7.2.1. Structure: Profile . . . . . . . . . . . . . . . . . 8
7.2.2. Keyset Classes . . . . . . . . . . . . . . . . . . . 8
7.2.3. Structure: EscrowedKeySet . . . . . . . . . . . . . . 8
7.2.4. Profile Classes . . . . . . . . . . . . . . . . . . . 8
7.2.5. Structure: ProfileMaster . . . . . . . . . . . . . . 8
7.2.6. Structure: ProfileDevice . . . . . . . . . . . . . . 9
7.2.7. Structure: ProfileApplication . . . . . . . . . . . . 9
Hallam-Baker Expires October 6, 2019 [Page 2]
Internet-Draft Mesh Schema Reference April 2019
7.2.8. Structure: ProfileMesh . . . . . . . . . . . . . . . 9
7.2.9. Structure: ProfileMeshDevicePublic . . . . . . . . . 10
7.2.10. Structure: ProfileMeshDevicePrivate . . . . . . . . . 10
7.2.11. Structure: DeviceRecryptionKey . . . . . . . . . . . 10
7.3. Common Structures . . . . . . . . . . . . . . . . . . . . 10
7.3.1. Structure: Permission . . . . . . . . . . . . . . . . 10
7.3.2. Structure: Contact . . . . . . . . . . . . . . . . . 11
7.3.3. Structure: Role . . . . . . . . . . . . . . . . . . . 12
7.3.4. Structure: Address . . . . . . . . . . . . . . . . . 12
7.3.5. Structure: Location . . . . . . . . . . . . . . . . . 12
7.3.6. Structure: Reference . . . . . . . . . . . . . . . . 13
7.4. Catalog Entries . . . . . . . . . . . . . . . . . . . . . 13
7.4.1. Structure: CatalogEntry . . . . . . . . . . . . . . . 13
7.4.2. Structure: CatalogEntryDevice . . . . . . . . . . . . 13
7.4.3. Structure: CatalogEntryCredential . . . . . . . . . . 13
7.4.4. Structure: CatalogEntryNetwork . . . . . . . . . . . 14
7.4.5. Structure: CatalogEntryContact . . . . . . . . . . . 14
7.4.6. Structure: CatalogEntryContactRecryption . . . . . . 15
7.4.7. Structure: CatalogEntryBookmark . . . . . . . . . . . 15
7.4.8. Structure: CatalogEntryTask . . . . . . . . . . . . . 15
7.4.9. Structure: Task . . . . . . . . . . . . . . . . . . . 15
7.4.10. Structure: CatalogEntryApplication . . . . . . . . . 16
7.4.11. Structure: CatalogEntryApplicationEntry . . . . . . . 17
7.4.12. Structure: CatalogEntryApplicationRecryption . . . . 17
7.4.13. Structure: CatalogEntryApplicationSSH . . . . . . . . 17
7.4.14. Structure: CatalogEntryApplicationMail . . . . . . . 17
7.4.15. Structure: CatalogEntryApplicationNetwork . . . . . . 17
7.5. Messages . . . . . . . . . . . . . . . . . . . . . . . . 17
7.5.1. Structure: MeshMessage . . . . . . . . . . . . . . . 17
7.5.2. Structure: MeshMessageComplete . . . . . . . . . . . 17
7.5.3. Structure: MessageConnectionRequest . . . . . . . . . 18
7.5.4. Structure: MessageConnectionPIN . . . . . . . . . . . 18
7.5.5. Structure: MessageContactRequest . . . . . . . . . . 19
7.5.6. Structure: MessageConfirmationRequest . . . . . . . . 19
7.5.7. Structure: MessageConfirmationResponse . . . . . . . 19
7.5.8. Structure: MessageTaskRequest . . . . . . . . . . . . 19
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 20
11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20
Hallam-Baker Expires October 6, 2019 [Page 3]
Internet-Draft Mesh Schema Reference April 2019
1. Introduction
This document describes the data structures of the Mathematical Mesh
with illustrative examples. For an overview of the Mesh objectives
and architecture, consult the accompanying Architecture Guide
[draft-hallambaker-mesh-architecture] . For information on the
implementation of the Mesh Service protocol, consult the accompanying
Protocol Reference [draft-hallambaker-mesh-protocol]
This document has two main sections. The first section presents
examples of the Mesh profile, catalog entry and messages in use. The
second section contains the schema reference. All the material in
both sections is generated from the Mesh reference implementation
[draft-hallambaker-mesh-developer] .
Although some of the services described in this document could be
used to replace existing Internet protocols including FTP and SMTP,
the principal value of any communication protocol lies in the size of
the audience it allows them to communicate with. Thus, while the
Mesh Messaging service is designed to support efficient and reliable
transfer of messages ranging in size from a few bytes to multiple
terabytes, the near-term applications of these services will be to
applications that are not adequately supported by existing protocols
if at all.
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] .
2.2. Defined Terms
The terms of art used in this document are described in the Mesh
Architecture Guide [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] . The Mesh
documentation set and related specifications are described in this
document.
Hallam-Baker Expires October 6, 2019 [Page 4]
Internet-Draft Mesh Schema Reference April 2019
2.4. Implementation Status
The implementation status of the reference code base is described in
the companion document [draft-hallambaker-mesh-developer] .
3. Mesh Profiles
Mesh profiles are signed assertions that describe a set of
cryptographic credentials belonging to a user, a device or an
account.
Profiles perform a similar role to X.509v3 certificates but with
important differences:
o Profiles describe credentials, they do not make identity
statements
o Profiles do not expire, there is therefore no need to support
renewal processing.
o Profiles may be modified over time, the current and past status of
a profile being recorded in an append only log.
3.1. Master Profile
A Mesh master profile provides the root of trust for a mesh user.
Unless exceptional circumstances require, a
```` Example SchemaMaster ````
3.2. Device Profile
```` Example SchemaDevice ````
3.3. Mesh Profile
```` Example SchemaMesh ````
4. Data Model
4.1. Data Model
4.1.1. Objects
Unique identifier
Append only log
Hallam-Baker Expires October 6, 2019 [Page 5]
Internet-Draft Mesh Schema Reference April 2019
Log can be purged.
4.1.2. Catalogs
Set of entries
Entry state machine (Add-Update*-Delete)*
4.1.3. Spools
Queue of messages
Message state machine (Post-(Read-Unread)*-Delete)
5. Catalog Entries
5.1. Device
```` Example SchemaEntryDevice ````
5.2. Contact
```` Example SchemaEntryContact ````
5.3. Credential
```` Example SchemaEntryCredential ````
5.4. Network
```` Example SchemaEntryNetwork ````
5.5. Bookmark
```` Example SchemaEntryBookmark ````
5.6. Task
```` Example SchemaEntryTask ````
5.7. Application
5.7.1. SSH
```` Example SchemaEntrySSH ````
Hallam-Baker Expires October 6, 2019 [Page 6]
Internet-Draft Mesh Schema Reference April 2019
5.7.2. Mail
```` Example SchemaEntryMail ````
6. Messages
All communications between Mesh accounts takes the form of a Mesh
Message.
6.1. Completion
```` Example SchemaMessageCompletion ````
6.2. Connection
```` Example SchemaMessageConnection ````
6.3. Contact
```` Example SchemaMessageContact ````
6.4. Confirmation
```` Example SchemaMessageConfirmation ````
7. Schema
7.1. Shared Classes
The following classes are used as common elements in Mesh profile
specifications.a
7.1.1. Structure: PublicKey
The PublicKey class is used to describe public key pairs and trust
assertions associated with a public key.
UDF: String (Optional) UDF fingerprint of the public key parameters/
X509Certificate: Binary (Optional) List of X.509 Certificates
X509Chain: Binary [0..Many] X.509 Certificate chain.
X509CSR: Binary (Optional) X.509 Certificate Signing Request.
Hallam-Baker Expires October 6, 2019 [Page 7]
Internet-Draft Mesh Schema Reference April 2019
7.2. Mesh Profile Objects
Base class for all Mesh Profile objects.
7.2.1. Structure: Profile
Parent class from which all profile types are derived
Names: 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.
Updated: DateTime (Optional) The time instant the profile was last
modified.
NotaryToken: String (Optional) A Uniform Notary Token providing
evidence that a signature was performed after the notary token was
created.
7.2.2. Keyset Classes
7.2.3. Structure: EscrowedKeySet
A set of escrowed keys.
[No fields]
7.2.4. Profile Classes
7.2.5. Structure: ProfileMaster
Inherits: Profile
Describes the long term parameters associated with a personal
profile.
This profile MUST be signed by
MasterSignatureKey: 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.
MasterEscrowKeys: PublicKey [0..Many] A Personal Profile MAY contain
one or more PMEK keys to enable escrow of private keys used for
stored data.
Hallam-Baker Expires October 6, 2019 [Page 8]
Internet-Draft Mesh Schema Reference April 2019
OnlineSignatureKeys: PublicKey [0..Many] A Personal profile contains
at least one OSK which is used to sign device administration
application profiles.
7.2.6. Structure: ProfileDevice
Inherits: Profile
Describes a mesh device.
This profile MUST be signed by the DeviceSignatureKey
Description: String (Optional) Description of the device
DeviceSignatureKey: PublicKey (Optional) Key used to sign
certificates for the DAK and DEK. The fingerprint of the DSK is
the UniqueID of the Device Profile
DeviceAuthenticationKey: PublicKey (Optional) Key used to
authenticate requests made by the device.
DeviceEncryptionKey: PublicKey (Optional) Key used to pass encrypted
data to the device such as a DeviceUseEntry
7.2.7. Structure: ProfileApplication
Inherits: Profile
Contains the public description of a Mesh application.
[No fields]
7.2.8. Structure: ProfileMesh
Inherits: ProfileApplication
Contains the binding of a device to a MasterProfile. Each device has
a separate profile which MUST be signed by an OnlineSignatureKey
Account: String (Optional) Account address.
MasterProfile: DareMessage (Optional) Master profile of the account
being registered.
AccountEncryptionKey: PublicKey (Optional) Key used to encrypt data
under this profile
Hallam-Baker Expires October 6, 2019 [Page 9]
Internet-Draft Mesh Schema Reference April 2019
7.2.9. Structure: ProfileMeshDevicePublic
Inherits: ProfileApplication
Inherits: ProfileApplication
DeviceProfile: DareMessage (Optional) Device profile of the device
making the request.
Permissions: Permission [0..Many] List of the permissions that the
device has been granted.
7.2.10. Structure: ProfileMeshDevicePrivate
Inherits: ProfileApplication
Inherits: ProfileApplication
Permissions: Permission [0..Many] List of the permissions that the
device has been granted.
ProfileNonce: Binary (Optional) Random nonce used to mask the
fingerprint of the profile UDF.
ProfileWitness: Binary (Optional) Witness value calculated over the
ProfileNonce and profile UDF
7.2.11. Structure: DeviceRecryptionKey
UDF: String (Optional) The fingerprint of the encryption key
RecryptionKey: PublicKey (Optional) The recryption key
DeviceRecryptionKeyEncrypted: DareMessage (Optional) The decryption
key encrypted under the user's device key.
7.3. Common Structures
7.3.1. Structure: Permission
Name: String (Optional)
Name: String (Optional)
Role: String (Optional)
Role: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 10]
Internet-Draft Mesh Schema Reference April 2019
Capabilities: DareMessage (Optional) Keys or key contributions
enabling the operation to be performed
7.3.2. Structure: Contact
Identifier: String (Optional)
Identifier: String (Optional)
Account: String (Optional)
Account: String (Optional)
FullName: String (Optional)
FullName: String (Optional)
Title: String (Optional)
Title: String (Optional)
First: String (Optional)
First: String (Optional)
Middle: String (Optional)
Middle: String (Optional)
Last: String (Optional)
Last: String (Optional)
Suffix: String (Optional)
Suffix: String (Optional)
Labels: String [0..Many]
Labels: String [0..Many]
Addresses: Address [0..Many]
Addresses: Address [0..Many]
Locations: Location [0..Many]
Locations: Location [0..Many]
Hallam-Baker Expires October 6, 2019 [Page 11]
Internet-Draft Mesh Schema Reference April 2019
Roles: Role [0..Many]
7.3.3. Structure: Role
CompanyName: String (Optional)
CompanyName: String (Optional)
Addresses: Address [0..Many]
Addresses: Address [0..Many]
Locations: Location [0..Many]
7.3.4. Structure: Address
URI: String (Optional)
URI: String (Optional)
Labels: String [0..Many]
7.3.5. Structure: Location
Appartment: String (Optional)
Appartment: String (Optional)
Street: String (Optional)
Street: String (Optional)
District: String (Optional)
District: String (Optional)
Locality: String (Optional)
Locality: String (Optional)
County: String (Optional)
County: String (Optional)
Postcode: String (Optional)
Postcode: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 12]
Internet-Draft Mesh Schema Reference April 2019
Country: String (Optional)
7.3.6. Structure: Reference
MessageID: String (Optional) The received message to which this is a
response
ResponseID: String (Optional) Message that was generated in response
to the original (optional).
Relationship: String (Optional) The relationship type. This can be
Read, Unread, Accept, Reject.
7.4. Catalog Entries
7.4.1. Structure: CatalogEntry
[No fields]
7.4.2. Structure: CatalogEntryDevice
Inherits: CatalogEntry
Public device entry, indexed under the device ID
Account: String (Optional) The Account to which this entry binds
this device.
UDF: String (Optional) UDF of the signature key
AuthUDF: String (Optional) UDF of the authentication ID
ProfileMeshDevicePublicSigned: DareMessage (Optional) The device
profile
ProfileMeshDevicePrivateEncrypted: DareMessage (Optional) The device
profile
DeviceRecryptionKeys: DeviceRecryptionKey [0..Many] Decryption key
entries.
7.4.3. Structure: CatalogEntryCredential
Inherits: CatalogEntry
Inherits: CatalogEntry
Protocol: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 13]
Internet-Draft Mesh Schema Reference April 2019
Protocol: String (Optional)
Service: String (Optional)
Service: String (Optional)
Username: String (Optional)
Username: String (Optional)
Password: String (Optional)
7.4.4. Structure: CatalogEntryNetwork
Inherits: CatalogEntry
Inherits: CatalogEntry
Protocol: String (Optional)
Protocol: String (Optional)
Service: String (Optional)
Service: String (Optional)
Username: String (Optional)
Username: String (Optional)
Password: String (Optional)
7.4.5. Structure: CatalogEntryContact
Inherits: CatalogEntry
Inherits: CatalogEntry
Key: String (Optional) Unique key.
Permissions: Permission [0..Many] List of the permissions that the
contact has been granted.
Contact: DareMessage (Optional) The (signed) contact data.
Hallam-Baker Expires October 6, 2019 [Page 14]
Internet-Draft Mesh Schema Reference April 2019
7.4.6. Structure: CatalogEntryContactRecryption
Inherits: CatalogEntryContact
[No fields]
7.4.7. Structure: CatalogEntryBookmark
Inherits: CatalogEntry
Inherits: CatalogEntry
Uri: String (Optional)
Uri: String (Optional)
Title: String (Optional)
Title: String (Optional)
Path: String (Optional)
7.4.8. Structure: CatalogEntryTask
Inherits: CatalogEntry
Inherits: CatalogEntry
Task: DareMessage (Optional)
Task: DareMessage (Optional)
Key: String (Optional) Unique key.
7.4.9. Structure: Task
Key: String (Optional) Unique key.
Start: DateTime (Optional)
Start: DateTime (Optional)
Finish: DateTime (Optional)
Finish: DateTime (Optional)
StartTravel: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 15]
Internet-Draft Mesh Schema Reference April 2019
StartTravel: String (Optional)
FinishTravel: String (Optional)
FinishTravel: String (Optional)
TimeZone: String (Optional)
TimeZone: String (Optional)
Title: String (Optional)
Title: String (Optional)
Description: String (Optional)
Description: String (Optional)
Location: String (Optional)
Location: String (Optional)
Trigger: String [0..Many]
Trigger: String [0..Many]
Conference: String [0..Many]
Conference: String [0..Many]
Repeat: String (Optional)
Repeat: String (Optional)
Busy: Boolean (Optional)
7.4.10. Structure: CatalogEntryApplication
Inherits: CatalogEntry
Inherits: CatalogEntry
Key: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 16]
Internet-Draft Mesh Schema Reference April 2019
7.4.11. Structure: CatalogEntryApplicationEntry
[No fields]
7.4.12. Structure: CatalogEntryApplicationRecryption
[No fields]
7.4.13. Structure: CatalogEntryApplicationSSH
[No fields]
7.4.14. Structure: CatalogEntryApplicationMail
[No fields]
7.4.15. Structure: CatalogEntryApplicationNetwork
[No fields]
7.5. Messages
7.5.1. Structure: MeshMessage
MessageID: String (Optional)
MessageID: String (Optional)
Sender: String (Optional)
Sender: String (Optional)
Recipient: String (Optional)
Recipient: String (Optional)
References: Reference [0..Many]
7.5.2. Structure: MeshMessageComplete
Inherits: MeshMessage
[No fields]
Hallam-Baker Expires October 6, 2019 [Page 17]
Internet-Draft Mesh Schema Reference April 2019
7.5.3. Structure: MessageConnectionRequest
Inherits: MeshMessage
Inherits: MeshMessage
Account: String (Optional)
Account: String (Optional)
DeviceProfile: DareMessage (Optional) Device profile of the device
making the request.
ClientNonce: Binary (Optional)
ClientNonce: Binary (Optional)
ServerNonce: Binary (Optional)
ServerNonce: Binary (Optional)
Witness: String (Optional)
Witness: String (Optional)
PinID: String (Optional) Pin identifier used to identify a PIN
authenticated request.
7.5.4. Structure: MessageConnectionPIN
Inherits: MeshMessage
Inherits: MeshMessage
Account: String (Optional)
Account: String (Optional)
Expires: DateTime (Optional)
Expires: DateTime (Optional)
PIN: String (Optional)
Hallam-Baker Expires October 6, 2019 [Page 18]
Internet-Draft Mesh Schema Reference April 2019
7.5.5. Structure: MessageContactRequest
Inherits: MeshMessage
Inherits: MeshMessage
Contact: DareMessage (Optional) The contact data.
7.5.6. Structure: MessageConfirmationRequest
Inherits: MeshMessage
Inherits: MeshMessage
Text: String (Optional)
7.5.7. Structure: MessageConfirmationResponse
Inherits: MeshMessage
Inherits: MeshMessage
ResponseID: String (Optional)
ResponseID: String (Optional)
Accept: Boolean (Optional)
7.5.8. Structure: MessageTaskRequest
Inherits: MeshMessage
[No fields]
8. Security Considerations
The security considerations for use and implementation of Mesh
services and applications are described in the Mesh Security
Considerations guide [draft-hallambaker-mesh-security] .
9. IANA Considerations
All the IANA considerations for the Mesh documents are specified in
this document
Hallam-Baker Expires October 6, 2019 [Page 19]
Internet-Draft Mesh Schema Reference April 2019
10. Acknowledgements
11. References
11.1. Normative References
[draft-hallambaker-mesh-architecture]
Hallam-Baker, P., "Mathematical Mesh Part I: Architecture
Guide", draft-hallambaker-mesh-architecture-06 (work in
progress), August 2018.
[draft-hallambaker-mesh-protocol]
"[Reference Not Found!]".
[draft-hallambaker-mesh-security]
"[Reference Not Found!]".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997.
11.2. Informative References
[draft-hallambaker-mesh-developer]
Hallam-Baker, P., "Mathematical Mesh: Reference
Implementation", draft-hallambaker-mesh-developer-07 (work
in progress), April 2018.
11.3. URIs
[1] http://mathmesh.com/Documents/draft-hallambaker-mesh-schema.html
Author's Address
Phillip Hallam-Baker
Email: phill@hallambaker.com
Hallam-Baker Expires October 6, 2019 [Page 20]