3.2.6.2.1 Detection of Cloud Splits

  • Article

PNRP nodes MUST periodically test to determine whether they have become isolated or split off from the main cloud. For performance reasons, the frequency of split detections SHOULD be roughly constant over the entire cloud. This prevents tests from occurring too frequently. It means that for a single node, the test frequency is inversely proportional to the cloud's estimated size as specified in section 3.2.6.2.1.1. If, therefore, a node estimates that the cloud is large, the probability of that node initiating the split detection decreases.

To initiate split detection, a PNRP node MUST initiate a PNRP ID resolve process as specified in section 3.1.4.4.2, with following parameters:

  • Target PNRP ID: A node MUST randomly select a locally registered PNRP ID and then add 1 to get a Target PNRP ID.

  • ResolveCriteria: SEARCH_OPCODE_NONE.

  • PickBestMatchFromLocalIds: False.

  • ResolveReasonCode: REASON_SPLIT_DETECTION.

  • InitialBestMatchRouteEntry: NULL.

  • InitialNextHopRouteEntry: A Route Entry with PNRP ID set to zero and the first address set to the address of a seed server that was selected as specified in section 3.1.4.2.1.