{'fraction_non_alphanumeric': 0.009557945041816009, 'fraction_numerical': 0.0, 'mean_word_length': 5.396946564885496, '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}}
Network management for multi-network terminals

There is increasing interest in using terminal architectures capable of supporting multiple networks. A terminal that is episodically present on a network is a new situation for most Network Managers and for computer network defense needs. Likewise, having to accommodate interaction with multiple network managers is a different paradigm for the terminal. This paper discusses the kinds of node architecture features that would support this kind of interaction. It looks at the extension of traditional control plane architectures to support the use of Cognitive engines to simplify interactions with network managers and network security functions. It also discusses the use of a Service Oriented Architecture for alerting user networks when a terminal becomes part of the backhaul path.