Internet-Draft Mesh Presence Service June 2023
Hallam-Baker Expires 30 December 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 30 December 2023.

1. Introduction

Mesh Presence Protocol (MPP) is a UDP publish/subscriber protocol. Devices subscribed to an event notification service associated with an account receive UDP notification of events posted to that channel. This service may be used to provide subscribing devices with immediate of an event without the need for polling.

Uses of the presence service include notifying a device that an inbound synchronous communication session has been requested, receipt of an asynchronous message, updates to a Mesh catalog, etc.

MPP provides NAT traversal capabilities similar to those provided by STUN . Combining these capabilities with a presence service avoids the need for a separate service. [rfc8489]

All MPP packets are encapsulated as RUD datagrams. Messages from the client to the service are limited to a single packet. Messages from the service to the client may contain between 1 and 16 packets.

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 28-Jun-23 5:01:01 PM. Out of 250 examples, 50 failed.

4. Protocol

4.1. Client Initiated

Client initiated messages MAY be sent via either Web Service transport or UDP transport.

4.1.3. Status

The status interaction requests that the service resend the last publication message sent. Request

The Status Response message

4.2. Service Initiated

Service initiated messages MUST be sent via UDP transport

4.2.1. Publish

The publish message is Status

Serial number of the status response.

IP Endpoint

The IP Endpoint from which the last UDP communication from the client was received.


The current date and time in ticks and leap seconds.

Store Status

A list of status values for stores that have been updated. Acknowledgement

The acknowledgement message acknowledges receipt of a Status message.

6. IANA Considerations

This document requires no IANA actions.

8. 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, , <>.

9. Informative References

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