1.1 Glossary

  • Article

This document uses the following terms:

ClientId: A unique string that the client uses to identify itself to the resolver service, as described in section 1.3.1.2.

endpoint information: An endpoint address, formatted as a Uniform Resource Identifier (URI), along with a set of IP addresses. Describes the set of addresses on which a node is listening.

expiration time: A date-time value, in Coordinated Universal Time (UTC) format, that indicates when an instance of binary data is no longer valid.

globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).

mesh name: A set of nodes that establish connections to each other to form a mesh.

PeerNodeAddress: A structure that contains the URI of a node and a set of IP addresses on which the client is listening ([MC-PRCR] section 2.2.2.1).

registration lifetime: The amount of time during which a registration record is guaranteed to be preserved by the resolver service; always associated with a particular registration record. This time starts upon the successful addition of a registration record to the resolver service. After this time has elapsed, the resolver service can choose to delete the corresponding registration record (section 3).

registration record: A set of endpoint information that is stored at the resolver service.

RegistrationId: A unique identifier in the form of a GUID, as described in section 1.3.1.3.

resolver client: An application endpoint that uses a resolver service to publish or obtain endpoint information.

resolver service: An application implementing this protocol that stores and distributes endpoint information.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.