CAIDA Home
 measurement | taxonomy | utilities | visualization  
 www.caida.org > tools : utilities : : owl
    visit     contact     search:
CAIDA: Cooperative Association for Internet Data Analysis
owl

-----summary of contents-----
owl is a database and a collection of Perl scripts that provide a single database codified from whois pick a good overview URL and RouteViews data, stored in a consistent database format for use by the operational and research community.
-----end summary of contents-----

Owl use data from four primary sources:

  1. static geographic information from NetGeo,
  2. monthly table dumps from the four RIRs (see below),
  3. skitter (IP address topology) data, and
  4. RouteViews BGP tables.
We will gather these three sources of data into a single database that supports lookups on IP allocation blocks, autonomous systems, assigned organizations, and geographic information.

CAIDA has arrangements for monthly bulk table transfer from the four RIRs: APNIC, ARIN, LACNIC, and RIPE. From these tables we glean the current IP, AS, and organization information, and track changes over time.

Using RouteViews BGP tables in conjunction with data from CAIDA's Macroscopic Topology Project, we will derive an IP-forward-probe based AS topology map. We will also generate an AS graph directly from Routeviews' BGP tables, which may differ from the probed topology graph for many reasons. [ 1, 2, 3, 4 ] http://www.caida.org/publications/papers/2003/ASP/ http://www.caida.org/publications/papers/2003/3rdparty/ http://www.research.att.com/~jrex/papers/sigcomm03.ps http://www.research.att.com/~jrex/papers/infocom04.pdf) We use this AS topology data to assign each AS an outdegree and ranking. The RIR data allows us to group these ASes into adminstratively responsible organizations, so that we can provide degree and ranking at the organizational granularity as well.

CAIDA's NetGeo database contains tables that map location names (city, state, or country) or US zip codes to latitude/longitude values. We will use these tables to map address components found by the NetGeo parsing code to latitude/longitude, and then we store city, state, country, latitude and longitude with the target IP address or AS in the NetGeo database. No contact data, e.g., phone or email addresses, are ever stored in the NetGeo database.

1 Traceroute and BGP AS Path Incongruities
Young Hyun, Andre Broido, and k claffy
Cooperative Association for Internet Data Analysis - CAIDA
San Diego Supercomputer Center,
University of California, San Diego
2 On Third-party Addresses in Traceroute Paths
Presented at the Passive and Active Measurement Workshop in 2003
Young Hyun, Andre Broido, and kc claffy
Cooperative Association for Internet Data Analysis - CAIDA
San Diego Supercomputer Center,
University of California, San Diego
3 Towards an Accurate AS-Level Traceroute Tool
Presented at Sigcomm, 2003.
Zhuoqing Morley Mao
UC Berkeley
  Jennifer Rexford and Jai Wang
AT & T Labs-Research
  Randy H. Katz
UC Berkeley
4 Scalable and Accurate Identification of AS-Level Forwarding Paths
Presented at IEEE INFOCOM, March 2004.
Zhuoqing Morley Mao
UC Berkeley
  David Johnson, Jennifer Rexford, and Jai Wang
AT & T Labs-Research
  Randy H. Katz
UC Berkeley

Cooperative Association for Internet Data Analysis (CAIDA)
  Last Modified: Thurs Jun-26-2008 17:34:26 PDT
  Maintained by: Bradley Huffaker
  Page URL: http://www.caida.org/tools/utilities/owl/index.xml