{'fraction_non_alphanumeric': 0.02206531332744925, 'fraction_numerical': 0.00353045013239188, 'mean_word_length': 4.968421052631579, '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}}
Impact of IPv4 address allocation practice on BGP routing table growth

Rapid BGP (border gateway protocol) routing table growth has been a main concern for the operation of the Internet in recent years. We study how current IPv4 address allocation practice affects the BGP table growth. The practice includes both newly-made allocations and two address policies, i.e., allocation size and minimum allocation size. We first found that the address blocks allocated during the past five years contributed to more than 71% of the BGP table growth within the same period. Moreover, contributions made by allocated address blocks quickly become static after the allocation. Based on this observation, we propose an empirical model to emulate table growth. We next study the impact of two address policies and show that while the "allocation size" policy is observed to have visible impact on the growth, there is no clear evidence that the "minimum allocation size" policy, designed for slowing down table size increase, has suppressed growth. We finally discuss how the address policies could have better controlled the BGP table growth.