1.1 Glossary

This document uses the following terms:

authenticator: A security token of a node computed using the password of the mesh and the node's public key.

channel type: A logical grouping of operations (messages) that can be sent over the mesh. A mesh can be used to handle more than one channel type simultaneously. A channel type is identified by a unique URI.

discovery: The process used to discover other nodes in the mesh of interest.

discovery service: The service that is used to discover other nodes. The Peer Channel Protocol [MC-PRCH] can use PNRP [MS-PNRP] or any other service implementing the Peer Channel Custom Resolver Protocol [MC-PRCR] to discover other nodes.

endpoint: A tuple (composed of an IP address, port, and protocol number) that uniquely identifies a communication endpoint.

flood (or flooding): The process of propagating messages throughout a mesh.

flood message: An application message.

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: A network of nodes that are all identified with the same mesh name.

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

multihoming: The practice of allowing TCP/IP connections on more than one interface adapter and network scope.

neighbor: A node that is directly connected to the given node.

neighbor connection: A TCP/IP connection between the endpoints of two nodes.

node: An instance of a channel endpoint participating in the mesh that implements the Peer Channel Protocol.

Peer Channel: The Peer Channel Protocol [MC-PRCH], used for broadcasting messages over a virtual network of cooperating nodes.

requesting node: A node that is requesting the formation of a neighbor connection to another node in the mesh.

responding node: A node that is responding to a request to form a neighbor connection from another node in the mesh.

Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].

Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.

XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].

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.