INTERNET MEASUREMENT INTERNET MAPPING OVERHEAD MINIMIZATION Intra- and inter-monitor redundancy reduction IBRAHIM ETHEM COSKUN University of Nevada, Reno M.Sc.
Intra –monitor redundancy Occurs when all traceroutes start from a single point Inter –monitor redundancy Occurs when multiple monitors visit the same point INTRA AND INTER –MONITOR REDUNDANCY
INTRA –MONITOR REDUNDANCY Monitor 1 Destination 1 Destination 2 Destination 3
INTER –MONITOR REDUNDANCY Monitor 1 Monitor 2 Monitor 3 Destination 1
PlanetLab currently consists of 1187 nodes at 582 sites AS numbers of 1047 nodes collected 111 nodes not responded Planetlab VPs
Archipelago (Ark for short) is CAIDA's next- generation active measurement infrastructure AS numbers of 91 nodes collected Ark VPs
RIPE NCC is building the largest Internet measurement network ever made AS numbers of 5373 Nodes collected 2025 different ASes RIPE NCC VPs
TOTAL (collected) ASN Information
Data downloaded from CAIDA AS relation Compared with collected ASes which includes VPs (Ark, Planetlab, RIPE NCC) ASN Neighboring Relations
~500 available nodes, ~350 usable Probed 3 hops of each VP ASes in average Selected 1 IP per AS ingress points identified Gathered peering relations identified (One AS to another) Planetlab Vantage Points
traceroute to ( ), 30 hops max, 60 byte packets [AS3851/AS22911] ms ms ms [AS65534] ms ms [AS65534] ms [AS65534] ms ms [AS65534] ms [AS3851/AS22911] ms ms ms [AS3851] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS4637] ms ms ms [AS55831] ms [AS3786] ms [AS3786] ms [AS3786] ms [AS3786] ms [AS55831] ms [AS3786] ms ms [AS55831] ms [AS3786] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms IGRESS POINT IDENTIFICATION
#Ingresses - #ASes
Pick 12 ASes Based on: Sizes (#IPs), #Observed IPs, #Peers, Ranks 1 small, 1 medium, 1 large Probe these ASes from each VP AS ingress analysis
#CONNECTIONS#PEERS #Peers - #Connections ASN1ASN2#CONNECTIONS
#Peers - #Connections
/20 AS45609 BHARTI-MOBILITY-AS-AP Bharti Airtel Ltd. AS for GPRS Service,IN /20 AS45609 BHARTI-MOBILITY-AS-AP Bharti Airtel Ltd. AS for GPRS Service,IN /16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN /16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN /16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN /16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN /24 AS58779 I4HKLIMITED-AS i4HK Limited,HK /24 AS58779 I4HKLIMITED-AS i4HK Limited,HK AS Sizes Data:
#/32: 1 IP address within the subnet #/31: 2 IP addresses within the subnet #/30: 4 IP addresses within the subnet #/29: 8 IP addresses within the subnet #/28: 16 IP addresses within the subnet #/27: 32 IP addresses within the subnet #/26: 64 IP addresses within the subnet #/25: 128 IP addresses within the subnet #/24: 256 IP addresses within the subnet #/23: 512 IP address within the subnet #/22: 1024 IP addresses within the subnet #/21: 2048 IP addresses within the subnet #/20: 4096 IP addresses within the subnet #/19: 8192 IP addresses within the subnet #/18: IP addresses within the subnet #/17: IP addresses within the subnet #/16: IP addresses within the subnet #/15: IP addresses within the subnet #/14: IP address within the subnet #/13: IP addresses within the subnet #/12: IP addresses within the subnet #/11: IP addresses within the subnet #/10: IP addresses within the subnet #/9: IP addresses within the subnet #/8: IP addresses within the subnet AS Sizes IP prefixes, #IPs
Announced Prefixes: …../24 …../16 …../8 /24 /24 /16 /8 /8 How to calculate AS size = SIZE
AS Rank Data:
Ingress point analysis VP analysis How to reduce redundant probing?
Pick 2 IPs from each prefix First IP, Last IP /24 Ingress Analysis - Probing Mechanism Probe these IPs If they enter the AS from the same ingress, then that means all IPs in this /24 subnet belongs to the same ingress. If they reveal different ingress points, then divide the prefix by 2 and continue probing each subnet.
Ingress Analysis - Probing Mechanism First IP: Last IP: First IP: Last IP: First IP: Last IP: /24 Divide: /25 || /25 Ingress A Done! Ingress A Ingress B Continue Done! Ingress A Done! Ingress B /25 Ingress B /25 Ingress A
Which subnets reached by which ingresses Which VPs enter the target AS through which ingresses How much data we lose from recalling a VP or multiple VPs How many hops VPs traverse to trace these ASes Which VPs would be enough to trace an AS and not to cause redundant probing. Analysis
VP analysis Target AS Ingress router VP Target AS Other ASes
? QUESTIONS?