Internet DRAFT - draft-hallambaker-mesh-presence
draft-hallambaker-mesh-presence
Network Working Group P. M. Hallam-Baker
Internet-Draft ThresholdSecrets.com
Intended status: Informational 23 October 2022
Expires: 26 April 2023
Mathematical Mesh 3.0 Part XI: Mesh Presence Service
draft-hallambaker-mesh-presence-01
Abstract
https://mailarchive.ietf.org/arch/browse/mathmesh/
(http://whatever)Discussion of this draft should take place on the
MathMesh mailing list (mathmesh@ietf.org), 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 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 26 April 2023.
Copyright Notice
Copyright (c) 2022 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2
Hallam-Baker Expires 26 April 2023 [Page 1]
Internet-Draft Mesh Presence Service October 2022
2.1. Related Specifications . . . . . . . . . . . . . . . . . 2
2.2. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 2
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.4. Implementation Status . . . . . . . . . . . . . . . . . . 3
2.5. Reserved Callsigns . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . 4
6. Informative References . . . . . . . . . . . . . . . . . . . 5
1. Introduction
2. Definitions
This section presents the related specifications and standards....
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].
Hallam-Baker Expires 26 April 2023 [Page 2]
Internet-Draft Mesh Presence Service October 2022
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.
Hallam-Baker Expires 26 April 2023 [Page 3]
Internet-Draft Mesh Presence Service October 2022
@wendy A whistleblower, who is an insider with privileged access
capable of divulging information.
@Firstname_Lastname A generic user whose name is 'Firstname
Lastname'
3. IANA Considerations
This document requires no IANA actions.
4. Acknowledgements
5. Normative References
[draft-hallambaker-jsonbcd]
Hallam-Baker, P., "Binary Encodings for JavaScript Object
Notation: JSON-B, JSON-C, JSON-D", Work in Progress,
Internet-Draft, draft-hallambaker-jsonbcd-23, 23 October
2022, <https://datatracker.ietf.org/doc/html/draft-
hallambaker-jsonbcd-23>.
[draft-hallambaker-mesh-architecture]
Hallam-Baker, P., "Mathematical Mesh 3.0 Part I:
Architecture Guide", Work in Progress, Internet-Draft,
draft-hallambaker-mesh-architecture-21, 23 October 2022,
<https://datatracker.ietf.org/doc/html/draft-hallambaker-
mesh-architecture-21>.
[draft-hallambaker-mesh-dare]
Hallam-Baker, P., "Mathematical Mesh 3.0 Part III : Data
At Rest Encryption (DARE)", Work in Progress, Internet-
Draft, draft-hallambaker-mesh-dare-16, 23 October 2022,
<https://datatracker.ietf.org/doc/html/draft-hallambaker-
mesh-dare-16>.
[draft-hallambaker-mesh-udf]
Hallam-Baker, P., "Mathematical Mesh 3.0 Part II: Uniform
Data Fingerprint.", Work in Progress, Internet-Draft,
draft-hallambaker-mesh-udf-17, 23 October 2022,
<https://datatracker.ietf.org/doc/html/draft-hallambaker-
mesh-udf-17>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
Hallam-Baker Expires 26 April 2023 [Page 4]
Internet-Draft Mesh Presence Service October 2022
6. Informative References
[draft-hallambaker-mesh-developer]
Hallam-Baker, P., "Mathematical Mesh: Reference
Implementation", Work in Progress, Internet-Draft, draft-
hallambaker-mesh-developer-10, 27 July 2020,
<https://datatracker.ietf.org/doc/html/draft-hallambaker-
mesh-developer-10>.
Hallam-Baker Expires 26 April 2023 [Page 5]
