IPv4 address sharing mechanism classification and tradeoff analysis

The growth of the Internet has made IPv4 addresses a scarce resource. Due to slow IPv6 deployment, IANA-level IPv4 address exhaustion was reached before the world could transition to an IPv6-only Internet. The continuing need for IPv4 reachability will only be supported by IPv4 address sharing. This paper reviews ISP-level address sharing mechanisms, which allow Internet service providers to connect multiple customers who share a single IPv4 address. Some mechanisms come with severe and unpredicted consequences, and all of them come with tradeoffs. We propose a novel classification, which we apply to existing mechanisms such as NAT444 and DS-Lite and proposals such as 4rd, MAP, etc. Our tradeoff analysis reveals insights into many problems including: abuse attribution, performance degradation, address and port usage efficiency, direct intercustomer communication, and availability

Impact of routing parameters on route diversity and path inflation

Years after the initial development of the current routing protocols we still lack an understanding of the impact of various parameters on the routes chosen in today’s Internet. Network operators are struggling to optimize their routing, but the effectiveness of those efforts is limited. In this article, we study sensitivity of routing stretch and diversity metrics to factors such as policies, topology, IGP weights, etc. using statistical techniques. We confirm previous findings that routing policies and AS size (in number of routers) are the dominating factors. Surprisingly, we find that intra-domain factors only have marginal impact on global path properties. Moreover, we study path inflation by comparing against the paths that are shortest in terms of AS-level/router-level hops or geographic distances. Overall, the majority of routes incur reasonable stretch. From the experience with our Internet-scale simulations, we find it hard to globally optimize path selection with respect to the geographic length of the routes, as long as inter-domain routing protocols do not include an explicit notion of geographic distance in the routing information

Detecting unsafe BGP policies in a flexible world

Internet Service Providers (ISPs) need to balance multiple opposing objectives. On one hand, they strive to offer innovative services to obtain competitive advantages; on the other, they have to interconnect with potentially competing ISPs to achieve reachability, and coordinate with them for certain services. The complexity of balancing these objectives is reflected in the diversity of policies of the Border Gateway Protocol (BGP), the standard inter-domain routing protocol. Unforeseen interactions among the BGP policies of different ISPs can cause routing anomalies. In this work, we propose a methodology to allow ISPs to check their BGP policy configurations for guaranteed convergence to a single stable state. This requires that a set of ISPs share their configurations with each other, or with a trusted third party. Compared to previous approaches to BGP safety, we (1) allow ISPs to use a richer set of policies, (2) do not modify the BGP protocol itself, and (3) detect not only instability, but also multiple stable states. Our methodology is based on the extension of current theoretical frameworks to relax their constraints and use incomplete data. We believe that this provides a rigorous foundation for the design and implementation of safety checking tools