Versions Compared

Old Version 1

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (umar.kalim)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

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. Deployment: Faran
    1. Look into Mathematics of Singular Vector Decomposition technique. (agreed 11/16/06): Faran
  5. Visualization
    1. Provide documentation (in progress 2/27/07, documented maths of selection 3/20/07, needs updating, agreed to update 3/22/07, should it be a wiki? - Umar thinks good idea need Faran view 4/30/07, Faran agrees 5/10/07): Farhan, Faran
    2. Can we add AS's to routes: Yee, Faran
    3. DiscoveryStatistics =>LandMark Analysis need to identify which Site number is displayed (i.e. from which window): Faran
    4. Sites.txt
      1. Need to be able to edit existing sites: Faran
    5. When zooming maintain size of dots (Faran will propose to Umar as a student project 4/10/07, he is concerned about the download time, Asif suggests using NASA images for Java platform, will send link 4/12/07, assigned to Rehan 5/10/07):  Faran, Rehan
  6. Bugs:
  7. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from): Faran
  8. Improvements
    2. Allow alpha to change (lot of work, many changes, will could improve greatly, changes design, Faran focussing on 4/12/07, need progressneed analysis & understanding)
    3. Look at using PingER historical data to optimize alpha (agreed 4/12/07): Faran
    Need a way to display alpha used: Faran
    2. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from):
    3. Add traceroute location:
    4. Add results from GeoIP:
  9. 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. China (sent email to ctsnet 7/26/06, reminded 12/6/06, 1/27/07): Les
      2. Try and get sites in Africa (Les sent email 11/28/06): Les
      3. Wiki Markup
        -COMTEC, Japan \[Done 5/11/07\]: Les-
      4. Wiki Markup
        -HSPC, Hsinchu, Taiwan \[Done 5/11/07\]: les-
      5. Add traceroute/Looking Glass servers in critical areas, if they have a common format (asked for 11/15/06, Les did a manual look at traceroute.org and found about 20 potential landmarks 11/17/06, Faran not clear if one can automate 2/27/07, several are automateable, to prove it Les has added 8, Faran will work on, re-requested 3/26/07 with suggestions, Faran is having problems with blocking after several accesses, will get a list then will try and contact to open up 5/10/07): Faran
      6. Get site in Korea at Ajou university (trying to persuade 5/8/07): Umar
      7. Get site at KHU (server available, problems with permissions to open UDP sockets 5/8/07, Bartelt knows of nothing in the Apache config file that would cause this, may be a priviledges the command line user has more privs than the web server 5/11/07, traceroute server is not responding 5/11/07): Umar
    2. Add NetDiGi route servers (asked for 8/30/06, is able to parse them, will look at adding appropriate hosts 3/22/07): Faran
  10. Apply to PingER node database to check the lat/longs are roughly correct (tried with 300-400 sites but cannnot get results due to fragile Internet at NIIT, will interact with Akbar to make tests at SLAC 8/31/06, exchanged emails on list of PingER hosts to locate 9/3/06, Shahryar sent information on how to access pingtable.pl data): Faran
      1. Is IHEP in list?
  12. Documentation
    1. Add information on the interpretive script sent to PlanetLab hosts: Shahryar
    2. Update thesis documentation and make it available online: Umar
  13. Analysis
    1. Provide API (agreed 6/28/07, changes to TULIP mean current API is not working):
    Analysis
    1. Literature search on triangulation, multi-lateration: Faranunmigrated-wiki-markup
      -Measure landmarks from landmarks \[Done 2/15/07\]: Faran-
    2. 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
    3. Document Faran's algorithm, try new algorithm that does not require destination to be inside triangle: Faran, Umar
    4. Analyse the effect of passing IP addresses to landmarks rather than names: Faran
    5. Look at impact of increasing number of pings for getting accurate min_RTT (Faran measured for a few sites, Les gave ideas on how to extend and analyze for multiple sites, could be a major project 4/4/07): Faran
    6. Map TULIPs accuracy by region. This will help in identifying where to add new landmarks : Shahryar
    7. 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
    8. Compare with GeoIP Tool & Hostip.info
      1. Find cases where TULIP beats GeoIP Tool [Done
      Compare with GeoIP Tools
      1. Wiki MarkupFind a case where TULIP beats GeoIP Tool \[Done 4.68.116.16, probably backbone routers too\]:
      For US compare Faran's algorithm with GeoIP & simple triangulation for PingER hosts(in progress 2/1/07)
      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. Confidence estimates
      6. Applied to PingER hosts
      7. Outside triangles, area coverage
      8. Effect/need to vary alpha: Faran
      9. Look at big discrepancies
    Analysis of Accuracy and applicability
    2. Accuracy vs known locations (landmarks & PingER hosts): faran
    3. Provide bubble maps of accuracy: FaranShahryar
    4. What area/population is covered by TULIP
    5. Show accuracy by region and country: Faran
    6. Come up with a way to estimate the accuracy/confidence of estimates: Faran
      1. Document in the TULIP web page: Faran
    7. Shahryar
  14. Look at publication Look at publication (helps advance Faran's career and possibly "best project",  will need more analysis)
    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