Internet-Draft Mesh Presence Service October 2022
Hallam-Baker Expires 26 April 2023 [Page]
Network Working Group
Intended Status:
P. M. Hallam-Baker

Mathematical Mesh 3.0 Part XI: Mesh Presence Service

Abstract of this draft should take place on the MathMesh mailing list (, which is archived at .

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

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 26 April 2023.

2. Definitions

This section presents the related specifications and standards....

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.


An eavesdropper


A government representative


A malicious designer for cryptographic standards


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


A malicious party engaged in an active attack

@provider, @provisional

Mesh Service Providers


The callsign of the registry quartermaster.

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

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


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


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


A generic user whose name is 'Firstname Lastname'

3. IANA Considerations

This document requires no IANA actions.

5. Normative References

Hallam-Baker, P., "Binary Encodings for JavaScript Object Notation: JSON-B, JSON-C, JSON-D", Work in Progress, Internet-Draft, draft-hallambaker-jsonbcd-23, , <>.
Hallam-Baker, P., "Mathematical Mesh 3.0 Part I: Architecture Guide", Work in Progress, Internet-Draft, draft-hallambaker-mesh-architecture-21, , <>.
Hallam-Baker, P., "Mathematical Mesh 3.0 Part III : Data At Rest Encryption (DARE)", Work in Progress, Internet-Draft, draft-hallambaker-mesh-dare-16, , <>.
Hallam-Baker, P., "Mathematical Mesh 3.0 Part II: Uniform Data Fingerprint.", Work in Progress, Internet-Draft, draft-hallambaker-mesh-udf-17, , <>.
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <>.

6. Informative References

Hallam-Baker, P., "Mathematical Mesh: Reference Implementation", Work in Progress, Internet-Draft, draft-hallambaker-mesh-developer-10, , <>.