3.2.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

Each entry in the Cloud Table (as specified in section 3.1.1) is extended to have the following additional information:

  • Conversation Table: A table of active synchronization conversations from new nodes in the process of joining the cloud. Each entry has the following state:

    • Peer's IP Address and Port: The IP address and port number of the peer.

    • Hashed Nonce: The Hashed Nonce value received in a SOLICIT message from the node.

  • Locally Registered PNRP ID List: A list of all PNRP IDs registered by the PNRP node itself or on behalf of protocols or higher-layer applications publishing Peer Names. Each entry in the list has the following fields:

    • PNRP ID: The locally registered PNRP ID.

    • Leaf Set: A list of the route entries for the five numerically closest PNRP IDs that are less than the locally registered PNRP ID and the five numerically closest PNRP IDs that are greater than the locally registered PNRP ID.

Note The previously conceptual data can be implemented by using a variety of techniques. An implementer is at liberty to implement such data in any way that it pleases.

Show: