{'fraction_non_alphanumeric': 0.03362690152121697, 'fraction_numerical': 0.006405124099279423, 'mean_word_length': 5.038647342995169, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 1, '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}}
Traffic engineering of high-rate large-sized flows

High-rate large-sized (α) flows have adverse effects on delay-sensitive flows. Research-and-education network providers are interested in identifying such flows within their networks, and directing these flows to traffic-engineered QoS-controlled virtual circuits. To achieve this goal, a design is proposed for a hybrid network traffic engineering system (HNTES) that would run on an external server, gather NetFlow reports from routers, analyze these reports to identify α-flow source/destination address prefixes, configure firewall filter rules at ingress routers to extract future flows and redirect them to previously provisioned intra-domain virtual circuits. This paper presents an evaluation of this HNTES design using NetFlow reports collected over a 7-month period from four ESnet routers. Our analysis shows that had HNTES been deployed, it would have been highly effective, e.g., > 90% of α-bytes that arrived at the four routers over the 7-month period would have been redirected to virtual circuits. Design aspects such as whether to use /24 subnet IDs or /32 addresses in firewall filters, and which router interfaces' NetFlow reports to include in the HNTES analysis, are studied.