the static profile table are deleted. If the current mode is active and the new mode is test, no further action is required. 

According to the subject matter described herein, the mode of routing node 100 with respect to dynamic foreign mobility management node learning may be configurable by setting a value in a table maintained in memory of routing node 100$_{.}$ The default mode may be set to off. Similarly, the success and failure thresholds used in determining the status of a node may be configurable with the default value of none. If the default values change during operation of routing node 100$_{,}$ the new threshold values will be taken into effect for graylisted dynamic VLRs or other nodes when in active mode. Threshold values are only required in active mode and only for dynamic VLRs corresponding to which no static VLR profile exists. 

When a new static VLR profile entry is added to the static profile table, because routing node 100 picks the status of the VLR from the static entry, the status of the dynamic VLR entry does not matter. Accordingly, there is no need to update or delete an existing VLR entry. The dynamic entry will age out after a configurable time period if it is not used. 

If an existing static VLR profile status is changed, there is likewise no need to update the dynamic profile entry because the static status controls. If a static VLR profile entry is deleted, no action is required with regard to the dynamic VLR status. The dynamic VLR status will remain unchanged. 

As indicated above, dynamic learning may be performed for velocity checking by automatically learning what would be considered reasonable time periods for travel between foreign mobility management nodes. It is risky to learn “velocity” from an unknown or graylisted mobility management node as the communication from such a node may actually be from a hacker. Therefore, routing node 100 may learn velocity (or associated time period) only when one of the following criteria is met: 

- A message is received from a trusted mobility management node 

• All mobility management nodes are trusted during learn mode, and only whitelisted mobility management nodes are trusted in other modes. 

