{'fraction_non_alphanumeric': 0.016079632465543645, 'fraction_numerical': 0.0, 'mean_word_length': 5.079069767441861, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Improved network convergence and quality of service by strict priority queuing of routing traffic

During the transient period after a link failure the network cannot guarantee the agreed service levels to user data. This is due to the fact that forwarding tables in the network are inconsistent. Moreover, link states can inadvertently be advertised wrong due to protocol time outs, which may result in persistent route flaps. Reducing the probability of wrongly advertised link states, and the time during which the forwarding tables are inconsistent, is therefore of eminent importance to provide consistent and high level QoS to user data. By queuing routing traffic in a queue with strict priority over all other (data) queues, i.e. assigning the highest priority in a Differentiated Services model, we were able to reduce the probability of routing data loss to almost zero, and reduce flooding times almost to their theoretical limit. The quality of service provided to user traffic was considerable higher than without the proposed modification. The scheme is independent of the routing protocol, and can be used with most differentiated service models. It is compatible with the current OSPF standard, and can be used in conjunction with other improvements in the protocol with similar objectives.