Internet-Draft | Mesh Presence Service | October 2022 |
Hallam-Baker | Expires 26 April 2023 | [Page] |
https://mailarchive.ietf.org/arch/browse/mathmesh/Discussion of this draft should take place on the MathMesh mailing list (mathmesh@ietf.org), which is archived at .¶
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 (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.¶
This section presents the related specifications and standards....¶
This document makes use of the terms defined in [draft-hallambaker-mesh-architecture].¶
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].¶
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.¶
The following callsigns are reserved identifiers in the callsign registry. When used in this document, these callsigns refer to the following parties:¶
The generic end users, Alice, Bob, Carol and Doug.¶
Generic callsigns¶
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¶
Mesh Service Providers¶
The callsign of the registry quartermaster.¶
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'¶
This document requires no IANA actions.¶