A GlobalDiscoveryServer is a Server implementing different global services for discovery, Certificate management, user or PubSub key management, user authorization, software and device management.

The number of applications using the different services may be large and a GDS is most likely not able to handle connections from all Clients at the same time. Therefore, a Client connected to a GDS should minimize the time it is connected to the GDS. The application shall disconnect as soon as it completes the sequence of actions needed to interact with the services. The applications shall not keep connections open between the execution of sequences.

If it runs out of connection resources, a GDS is allowed to close Sessions with Clients which have not be authenticated as one of the GDS administrative Roles. If the GDS needs to close Sessions, it should first close Sessions without GDS management Privileges. Otherwise, it may close the Session that was inactive for the longest time.

It is also recommended to use a short maximum session timeout on the GDS.

Actions performed cyclically by applications during PullManagement shall start the second cycle with a random delay that is between one and at least ten percent of the cycle period.