3.2.6.2 Maintenance Timer Expiry

  • Article

When the Maintenance Timer expires, the PNRP node MUST attempt to detect cloud splits (as specified in section 3.2.6.2.1).

If a node finds that it has no entries in its cache, it SHOULD also try to resynchronize with the nodes it knows in order to obtain more entries. Synchronization is initiated when the node sends a SOLICIT message, as specified in section 3.1.4.3.

The PNRP node MAY<6> also resolve any PNRP IDs that it wants in order to ensure that the cache requirements, as specified in section 3.2.1.1, continue to be met. If it does resolve, then the ResolveReasonCode MUST be set to REASON_CACHE_MAINTENANCE.