{'fraction_non_alphanumeric': 0.01533406352683461, 'fraction_numerical': 0.002190580503833516, 'mean_word_length': 5.0131578947368425, '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}}
Fixing timeout intervals for lost packet detection in computer communication networks

In a packet-switched data communication network which provides internal packet accountability via an end-to-end positive acknowledgment protocol, it is necessary to include a mechanism for detection and retransmission of missing packets. In particular, a decision must be made as to how long a sending element should reasonably wait before declaring an unacknowledged packet lost and initiating a recovery action. This waiting time is one of a class of system parameters which have come to be known as timeout intervals. The choice of a timeout interval is a delicate problem. 1 , 2 If it is too short, network capacity is wasted by frequent unnecessary actions for packets which are not lost but merely delayed. If the timeout interval is too long, lost packets cause needlessly prolonged delays before recovery is initiated.