The Experts below are selected from a list of 9375 Experts worldwide ranked by ideXlab platform
Padma Raghavan - One of the best experts on this subject based on the ideXlab platform.
-
analysis of the Ipv4 Address space delegation structure
International Symposium on Computers and Communications, 2007Co-Authors: Anusha Sriraman, Kevin R B Butler, Patrick Mcdaniel, Padma RaghavanAbstract:The Internet has grown tremendously in terms of the number of users who rely on it and the number of organizations that are connected to it. Characterizing how this growth affects its structure and topology is vitally important to determine the fundamental characteristics and limitations that must be handled, such as Address space exhaustion; understanding the process of allocating and delegating Address space can help to answer these questions. In this paper, we analyze BGP routing data to study the structure and growth of Ipv4 Address space allocation, fragmentation and usage. We explore the notion of delegation relationships among prefixes and use this information to construct an autonomous system (AS) delegation tree. We show that delegation in the Internet is not significantly correlated to the underlying topology or AS customer-provider relationships. We also analyze the fragmentation and usage of Address space over a period of five years and examine prefixes that are delegated by organizations vs. those that are not delegated. We notice that the Address space usage due to delegating prefixes is increasing at the same rate as the Address space usage due to non-delegating prefixes. This indicates that fragmentation rate of the Address space is actually almost a constant with respect to total Address usage. Additionally, we show that most delegation is performed by a small number of organizations, which may aid in the implementation of a public-key infrastructure for the Internet.
-
ISCC - Analysis of the Ipv4 Address Space Delegation Structure
2007 IEEE Symposium on Computers and Communications, 2007Co-Authors: Anusha Sriraman, Kevin R B Butler, Patrick Mcdaniel, Padma RaghavanAbstract:The Internet has grown tremendously in terms of the number of users who rely on it and the number of organizations that are connected to it. Characterizing how this growth affects its structure and topology is vitally important to determine the fundamental characteristics and limitations that must be handled, such as Address space exhaustion; understanding the process of allocating and delegating Address space can help to answer these questions. In this paper, we analyze BGP routing data to study the structure and growth of Ipv4 Address space allocation, fragmentation and usage. We explore the notion of delegation relationships among prefixes and use this information to construct an autonomous system (AS) delegation tree. We show that delegation in the Internet is not significantly correlated to the underlying topology or AS customer-provider relationships. We also analyze the fragmentation and usage of Address space over a period of five years and examine prefixes that are delegated by organizations vs. those that are not delegated. We notice that the Address space usage due to delegating prefixes is increasing at the same rate as the Address space usage due to non-delegating prefixes. This indicates that fragmentation rate of the Address space is actually almost a constant with respect to total Address usage. Additionally, we show that most delegation is performed by a small number of organizations, which may aid in the implementation of a public-key infrastructure for the Internet.
Anusha Sriraman - One of the best experts on this subject based on the ideXlab platform.
-
analysis of the Ipv4 Address space delegation structure
International Symposium on Computers and Communications, 2007Co-Authors: Anusha Sriraman, Kevin R B Butler, Patrick Mcdaniel, Padma RaghavanAbstract:The Internet has grown tremendously in terms of the number of users who rely on it and the number of organizations that are connected to it. Characterizing how this growth affects its structure and topology is vitally important to determine the fundamental characteristics and limitations that must be handled, such as Address space exhaustion; understanding the process of allocating and delegating Address space can help to answer these questions. In this paper, we analyze BGP routing data to study the structure and growth of Ipv4 Address space allocation, fragmentation and usage. We explore the notion of delegation relationships among prefixes and use this information to construct an autonomous system (AS) delegation tree. We show that delegation in the Internet is not significantly correlated to the underlying topology or AS customer-provider relationships. We also analyze the fragmentation and usage of Address space over a period of five years and examine prefixes that are delegated by organizations vs. those that are not delegated. We notice that the Address space usage due to delegating prefixes is increasing at the same rate as the Address space usage due to non-delegating prefixes. This indicates that fragmentation rate of the Address space is actually almost a constant with respect to total Address usage. Additionally, we show that most delegation is performed by a small number of organizations, which may aid in the implementation of a public-key infrastructure for the Internet.
-
ISCC - Analysis of the Ipv4 Address Space Delegation Structure
2007 IEEE Symposium on Computers and Communications, 2007Co-Authors: Anusha Sriraman, Kevin R B Butler, Patrick Mcdaniel, Padma RaghavanAbstract:The Internet has grown tremendously in terms of the number of users who rely on it and the number of organizations that are connected to it. Characterizing how this growth affects its structure and topology is vitally important to determine the fundamental characteristics and limitations that must be handled, such as Address space exhaustion; understanding the process of allocating and delegating Address space can help to answer these questions. In this paper, we analyze BGP routing data to study the structure and growth of Ipv4 Address space allocation, fragmentation and usage. We explore the notion of delegation relationships among prefixes and use this information to construct an autonomous system (AS) delegation tree. We show that delegation in the Internet is not significantly correlated to the underlying topology or AS customer-provider relationships. We also analyze the fragmentation and usage of Address space over a period of five years and examine prefixes that are delegated by organizations vs. those that are not delegated. We notice that the Address space usage due to delegating prefixes is increasing at the same rate as the Address space usage due to non-delegating prefixes. This indicates that fragmentation rate of the Address space is actually almost a constant with respect to total Address usage. Additionally, we show that most delegation is performed by a small number of organizations, which may aid in the implementation of a public-key infrastructure for the Internet.
Sebastian Zander - One of the best experts on this subject based on the ideXlab platform.
-
LCN - Share or Not: Investigating the Presence of Large-Scale Address Sharing in the Internet
2017 IEEE 42nd Conference on Local Computer Networks (LCN), 2017Co-Authors: Sebastian Zander, David MurrayAbstract:Network Address Translation (NAT) allows multiple devices with private Addresses to share one public Address. NAT was mainly confined to home gateways, but with the exhaustion of the Ipv4 Address space, large-scale NATs have been deployed. Other technologies causing large-scale Address sharing are on the rise as well (e.g. VPNs). Large-scale Address sharing is problematic, since it limits the number of concurrent TCP connections and severely limits geolocation and geoblocking. We investigate the presence of large-scale Address sharing in the Internet, including how frequently it occurs, in which types of organisations it occurs, where it occurs geographically, how many users share Addresses, and whether its presence is linked to Ipv4 Address shortage. Our results show that there are thousands of Addresses with significant large-scale sharing with up to a few thousand users sharing a single Address. Most of this sharing occurs within ISPs, many of which are located in countries with Ipv4 Address shortage, indicating that large-scale NATs may be a consequence of Ipv4 shortages.
-
Internet Measurement Conference - Capturing ghosts: predicting the used Ipv4 space by inferring unobserved Addresses
Proceedings of the 2014 Conference on Internet Measurement Conference, 2014Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville ArmitageAbstract:The pool of unused routable Ipv4 prefixes is dwindling, with less than 4% remaining for allocation at the end of June 2014. Yet the adoption of IPv6 remains slow. We demonstrate a new capture-recapture technique for improved estimation of the size of "Ipv4 reserves" (allocated yet unused Ipv4 Addresses or routable prefixes) from multiple incomplete data sources. A key contribution of our approach is the plausible estimation of both observed and unobserved-yet-active (ghost) Ipv4 Address space. This significantly improves our community's understanding of Ipv4 Address space exhaustion and likely pressure for IPv6 adoption. Using "ping scans", network traces and server logs we estimate that 6.3 million /24 subnets and 1.2 billion Ipv4 Addresses are currently in use (roughly 60% and 45% of the publicly routed space respectively). We also show how utilisation has changed over the last 2--3 years and provide an up-to-date estimate of potentially-usable remaining Ipv4 space.
-
estimating Ipv4 Address space usage with capture recapture
Local Computer Networks, 2013Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville Armitage, Geoff HustonAbstract:As of April 2013 almost 95% of the Ipv4 Address space has been allocated. Yet, the transition to IPv6 is still relatively slow. One reason could be existing “Ipv4 reserves” - allocated but unused Ipv4 Addresses. Knowing how many Addresses are actively used is important to predict a potential Ipv4 Address market, predict the IPv6 deployment time frame, and measure progressive exhaustion after the Ipv4 space is fully allocated. Unfortunately, only a fraction of hosts respond to active probes, such as “ping”. We propose a capture-recapture method to estimate the actively used Ipv4 Addresses from multiple incomplete data sources, including “ping” censuses, network traces and server logs. We estimate that at least 950-1090 million Ipv4 Addresses are used, which is 36-41% of the publicly routed space. We analyse how the utilisation depends on various factors, such as region, country and allocation prefix length.
-
Estimating the used Ipv4 Address space with secure multi-party capture-recapture
2013 IEEE Conference on Computer Communications Workshops (INFOCOM WKSHPS), 2013Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville ArmitageAbstract:Many people have data sources of used Ipv4 Addresses, e.g. server logs or network measurements. However, the challenge when estimating Ipv4 Address usage is to combine the data sources of multiple collaborators in a secure and efficient way. The number of observed Addresses in one source is often not sensitive information, but most people do not want to share datasets of unanonymised Ipv4 Addresses. We propose using a secure and reasonably efficient protocol that combines the datasets while keeping the Addresses of collaborators private. We are also looking for more collaborators willing to share their data under our scheme.
-
LCN Workshops - Estimating Ipv4 Address space usage with capture-recapture
38th Annual IEEE Conference on Local Computer Networks - Workshops, 2013Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville Armitage, Geoff HustonAbstract:As of April 2013 almost 95% of the Ipv4 Address space has been allocated. Yet, the transition to IPv6 is still relatively slow. One reason could be existing “Ipv4 reserves” - allocated but unused Ipv4 Addresses. Knowing how many Addresses are actively used is important to predict a potential Ipv4 Address market, predict the IPv6 deployment time frame, and measure progressive exhaustion after the Ipv4 space is fully allocated. Unfortunately, only a fraction of hosts respond to active probes, such as “ping”. We propose a capture-recapture method to estimate the actively used Ipv4 Addresses from multiple incomplete data sources, including “ping” censuses, network traces and server logs. We estimate that at least 950-1090 million Ipv4 Addresses are used, which is 36-41% of the publicly routed space. We analyse how the utilisation depends on various factors, such as region, country and allocation prefix length.
Geoff Huston - One of the best experts on this subject based on the ideXlab platform.
-
estimating Ipv4 Address space usage with capture recapture
Local Computer Networks, 2013Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville Armitage, Geoff HustonAbstract:As of April 2013 almost 95% of the Ipv4 Address space has been allocated. Yet, the transition to IPv6 is still relatively slow. One reason could be existing “Ipv4 reserves” - allocated but unused Ipv4 Addresses. Knowing how many Addresses are actively used is important to predict a potential Ipv4 Address market, predict the IPv6 deployment time frame, and measure progressive exhaustion after the Ipv4 space is fully allocated. Unfortunately, only a fraction of hosts respond to active probes, such as “ping”. We propose a capture-recapture method to estimate the actively used Ipv4 Addresses from multiple incomplete data sources, including “ping” censuses, network traces and server logs. We estimate that at least 950-1090 million Ipv4 Addresses are used, which is 36-41% of the publicly routed space. We analyse how the utilisation depends on various factors, such as region, country and allocation prefix length.
-
LCN Workshops - Estimating Ipv4 Address space usage with capture-recapture
38th Annual IEEE Conference on Local Computer Networks - Workshops, 2013Co-Authors: Sebastian Zander, Lachlan L H Andrew, Grenville Armitage, Geoff HustonAbstract:As of April 2013 almost 95% of the Ipv4 Address space has been allocated. Yet, the transition to IPv6 is still relatively slow. One reason could be existing “Ipv4 reserves” - allocated but unused Ipv4 Addresses. Knowing how many Addresses are actively used is important to predict a potential Ipv4 Address market, predict the IPv6 deployment time frame, and measure progressive exhaustion after the Ipv4 space is fully allocated. Unfortunately, only a fraction of hosts respond to active probes, such as “ping”. We propose a capture-recapture method to estimate the actively used Ipv4 Addresses from multiple incomplete data sources, including “ping” censuses, network traces and server logs. We estimate that at least 950-1090 million Ipv4 Addresses are used, which is 36-41% of the publicly routed space. We analyse how the utilisation depends on various factors, such as region, country and allocation prefix length.
-
Ipv4 Address allocation and the BGP routing table evolution
ACM SIGCOMM Computer Communication Review, 2005Co-Authors: Xiaoqiao Meng, Geoff Huston, Beichuan Zhang, Lixia ZhangAbstract:The IP Address consumption and the global routing table size are two of the vital parameters of the Internet growth. In this paper we quantitatively characterize the Ipv4 Address allocations made over the past six years and the global BGP routing table size changes during the same period of time. About 63,000 Address blocks have been allocated since the beginning of the Internet, of which about 18,000 Address blocks were allocated during our study period, from November 1997 to August 2004. Among these 18,000 allocations, 90% of them started being announced into the BGP routing table within 75 days after the allocation, while 8% of them has not been used up to now. Among all the Address blocks that have ever been used, 45% of them were split into fragments smaller than the original allocated blocks; without these fragementations, the current BGP table would have been about half of its current size. Furthermore, we found that the evolution of BGP routing table consists of both the appearance of new prefixes and the disappearance of old prefixes. While the change of the BGP routing table size only reflects the combined results of the two processes, the dynamics of either process is much higher than that of the BGP table size. Finally, we classify routing prefixes into covering and covered ones, and examine their evolution separately. For the covered prefixes, which account for almost half of the BGP table size, we infer their practical motives such as multihoming, load balancing, and traffic engineering, etc., via a classification method.
Osamu Nakamura - One of the best experts on this subject based on the ideXlab platform.
-
SA46T Address Translator
2015Co-Authors: Naoki Matsuhira, Yukito Ueno, Osamu Nakamura, Katsuhiro HoribaAbstract:This document specifies SA46T Address Translator (SA46T-AT) specification. SA46T-AT enable access to Ipv4 only host from IPv6 host. Ipv4 host is identified as SA46T global Address in IPv6 Address space. The Address assigned to Ipv4 host may be global Ipv4 Address or private Ipv4 Address. SA46T-AT does not support access to IPv6 host from Ipv4 only host.
-
A Special Purpose TLD to resolve Ipv4 Address Literal on DNS64/NAT64 environments
2014Co-Authors: Yukito Ueno, Hiroaki Hazeyama, Akira Kato, Osamu NakamuraAbstract:In an IPv6-only environment with DNS64/NAT64 based translation service, there is no way to get access a URL whose domain name part includes an Ipv4 Address literal. This memo proposes a special purpose TLD so that the Ipv4 Address literal is accessible from such a DNS64/NAT64 environments.
-
a special purpose tld to resolve Ipv4 Address literal on dns64 nat64 environments
2014Co-Authors: Yukito Ueno, Hiroaki Hazeyama, Akira Kato, Osamu NakamuraAbstract:In an IPv6-only environment with DNS64/NAT64 based translation service, there is no way to get access a URL whose domain name part includes an Ipv4 Address literal. This memo proposes a special purpose TLD so that the Ipv4 Address literal is accessible from such a DNS64/NAT64 environments.