{'fraction_non_alphanumeric': 0.01567398119122257, 'fraction_numerical': 0.0, 'mean_word_length': 5.992700729927007, '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}}
Unintended Consequences of NAT Deployments with Overlapping Address Space

This document identifies two deployment scenarios that have arisen
from the unconventional network topologies formed using Network
Address Translator devices (NATs). First, the simplicity of
administering networks through the combination of NAT and DHCP has
increasingly lead to the deployment of multi-level inter-connected
private networks involving overlapping private IP address spaces.
Second, the proliferation of private networks in enterprises, hotels
and conferences, and the wide spread use of Virtual Private Networks
(VPNs) to access enterprise intranet from remote locations has
increasingly lead to overlapping private IP address space between
remote and corporate networks. The document does not dismiss these
unconventional scenarios as invalid, but recognizes them as real and
offers recommendations to help ensure these deployments can function
without a meltdown.