Skip to end of metadata
Go to start of metadata

Triangulate position of an unknown host (see http://www.slac.stanford.edu/comp/net/wan-mon/tulip): Shahryar, Les

  1. Visualization 
    1. When zooming maintain size of dots (awaits TULIP2)
  2. Bugs/questions (await TULIP2):
    1. How do Sno correlate when there are landmarks from SLAC and PlanetLab. It appears Sno for PlanetLab in Ping Results is not same as Sno in PlanetLab landmarks? (currently it is by order of of appearance in Ping Results 10/2/07):
    2. The alpha optimization using PingER data seems to do nothing useful:
    3. Confidence Estimates table does not sort on table heading (what does it mean, what are units, will replace with IQR/Median 10/2/07):
    4. Location History needs headings or something to explain what the columns are:
    5. Change Ladnmarks to Landmarks on tab in Ping window (reported 9/21/07, will be done in future release 10/2/07):
    6. Sort of LG/SLAC ping results for target = www.cern.ch of sort of  Min RTT gives the top entry as 1 (SWITCH,Switzerland), the next is 0.820 (CERN, Geneva), i.e. it has mis-sorted (reported 10/8/07):
    7. PlanetLab ping results table does not sort by table heading (reported 10/8/07):
    8. The alpha test under Discovery Statistics needs to throw away useless values of RTT else plot scaling can be useless:
    9. The alpha optimization using PingER seems to do nothing useful:
    10. South Africa landmark only accepts IP addresses so need to accommodate:
    11. What is fixed vs Min RTT under DiscoveryStatistics (Faran will talk to Asif 10/2/07, not needed now):
    12. Sometimes fails, maybe because when tulip starts it downloads Site.txt from niit server. If that be the case the left side table on the main frame should be empty and status bar should say "Error downloading config. file."
  3. Improvements/TULIP2 with Centralized Reflector
    1. Modify reflector.cgi to use the new sites.xml file, install at SLAC (done 1/12/08): Shahryar, Les
    2. Modify client to use new sites.xml file: Shahryar
    3. Redo NODEDETAILS database to clean up data , improve schema and generate the sites.xml file (done for landamrks only 11/30/07, awaits analyze hourly and ICFA year end report): Jared
      1. Clean up and add rest of PingER data: Jared
      2. Provide user interface
      3. Migrate from old to new version
    4. Allow alpha to change (lot of work, many changes, could improve, need analysis & understanding)
    5. Look at using PingER historical data to optimize alpha (agreed 4/12/07):
    6. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from):
    7. Add traceroute location:
    8. Add results from GeoIP:
  4. Landmarks
    1. Get more landmarks for TULIP, ideally need at least one landmark in all major developing countries that do not have direct connections to nearby countries.:
      1. Is IHEP in list?
  5. Documentation
    1. Add information on the interpretive script sent to PlanetLab hosts: Shahryar
    2. Update thesis documentation and make it available online: Umar
  6. Analysis
    1. Provide API (agreed 6/28/07, changes to TULIP mean current API is not working):
    2. Literature search on triangulation, multi-lateration:
    3. Optimize alpha by landmark (after have new location algorithm working, will try 1:2 for US, 1:3 for Europe, 2:15 Africa, done at NIIT, need to deploy at SLAC 4/10/07, Faran is worried about how to group nodes by region etc. and anomalies 6/13/07), hope to review results by 6/5/07): Faran
    4. Map TULIPs accuracy by region. This will help in identifying where to add new landmarks : Shahryar
    5. Analyze Speedtest sites with and without PlanetLabs landmarks. Also study results for North America using all 150 sites, will report results by 03/16/08: Shahryar
      1. Determine which sites have the highest frequency of being selected as one of the top 3 landmarks.
      2. Observe why some nodes are showing results with errors greater than 1000 Km.
      3. (Data used for analysis should be available to everyone (to allow them to conduct analysis)
      4. Why isn't SLAC listed in the list of sites?
      5. Why in the worst cases, the landmarks in the vicinity of the target failed to respond?
      6. Why do the results worsen (in some cases) when using both Planet Lab and PingER nodes?
      7. What values of alpha to use for each tier?
      8. Does the alpha value vary with increase in distance between the landmark and the target, how much and why?
      9. Document the findings
    6. Compare with GeoIP Tool & Hostip.info
      1. Find cases where TULIP beats GeoIP Tool [Done 4.68.116.16, probably backbone routers too]
      2. Compare with MaxMind (see http://www.maxmind.com/app/geolitecountry): Faran
      3. Document comparison in Wiki (is this done?): Shahryar
      4. Confidence estimates of accuracy
      5. Applied to PingER hosts
      6. Outside triangles, area coverage
      7. Effect/need to vary alpha: Faran
      8. Look at big discrepancies
    7. Provide bubble maps of accuracy: Shahryar
    8. What area/population is covered by TULIP
    9. Show accuracy by region and country: Shahryar
  7. Look at publication
    1. Find conference: all
    2. Can we get Cisco interested?: Arshad, Faran
    3. Update documentation: Les, Faran
    4. Read paper at http://research.microsoft.com/%7Epadmanab/papers/sigcomm2001.pdf:
    5. Put Faran's final year project documentation online: Faran, Umar
  • No labels