Mathematical Mesh 3.0 Part XI: Mesh Presence Service

2.1. Related Specifications

The Mesh Callsign registry is a component part of the Mathematical Mesh [draft-hallambaker-mesh-architecture] and makes use of the data formats and service formats described therein. In particular:¶

Uniform Data Fingerprint [draft-hallambaker-mesh-udf].

Describes the UDF format used to represent cryptographic nonces, keys and content digests in the Mesh and the use of Encrypted Authenticated Resource Locators (EARLs) and Strong Internet Names (SINs) that build on the UDF platform.¶

Data at Rest Encryption [draft-hallambaker-mesh-dare].

Describes the cryptographic message and append-only sequence formats used in Mesh applications and the Mesh Service protocol.¶

JSON-BCD Encoding [draft-hallambaker-jsonbcd].

Describes extensions to the JSON serialization format to allow direct encoding of binary data (JSON-B), compressed encoding (JSON-C) and extended binary data encoding (JSON-D). Each of these encodings is a superset of the previous one so that JSON-B is a superset of JSON, JSON-C is a superset of JSON-B and JSON-D is a superset of JSON-C.¶

2.2. Defined Terms

This document makes use of the terms defined in [draft-hallambaker-mesh-architecture].¶

2.3. 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 RFC 2119 [RFC2119].¶

2.4. Implementation Status

The implementation status of the reference code base is described in the companion document [draft-hallambaker-mesh-developer].¶

The examples in this document were created on 18-Oct-22 1:16:01 PM. Out of 249 examples, 52 failed.¶

2.5. Reserved Callsigns

The following callsigns are reserved identifiers in the callsign registry. When used in this document, these callsigns refer to the following parties:¶

@alice, @bob, @carol, @doug

The generic end users, Alice, Bob, Carol and Doug.¶

@callsign, @callsign1, @callsign2

Generic callsigns¶

@corporation, @customer, @competitor

A generic corporation and its customer and competitor.¶

@eve

An eavesdropper¶

@grace

A government representative¶

@heidi

A malicious designer for cryptographic standards¶

@judy

A judge who may be called upon to resolve a potential dispute between participants.¶

@mallet

A malicious party engaged in an active attack¶

@provider, @provisional

Mesh Service Providers¶

@quartermaster

The callsign of the registry quartermaster.¶

@sybil, @sybil0, @sybil-1, @sybil-n

A pseudonymous attacker, who usually uses a large number of identities.¶

@ted

A trusted arbitrator, who acts as a neutral third party.¶

@wendy

A whistleblower, who is an insider with privileged access capable of divulging information.¶

@Firstname_Lastname

A generic user whose name is 'Firstname Lastname'¶