You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

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

  1. Visualization 
    1. 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, assigned to Rehan 5/10/07, has images, will be a separate jar file to reduce disturbance, Rahan hopes to start after examine in two weeks 6/13/07, work in progress 7/26/07 faran is tracking Rehan's work):  Faran, Rehan
    2. Need a way to display alphas used: Faran
    3. Show the Geo IP Tool result also: Faran
  2. Bugs:
    1. Sorting on header in Site Lists does not work (7/3/07): Faran
    2. Traceroute Results table does not sort when clicking on column headings (7/5/07): Faran

    3. Double clicking on a row in Ping Results frame does not bring up the pings for that host but a randomly selected host (reported 7/26/07) [Done fixed by Faran7/27/07]: Faran

    4. The log does not appear to be visible under Security: Faran

    5. SNo are not consistent across tables [Done 7/27/07]: Faran

  3. Improvements
    1. Allow alpha to change (lot of work, many changes, could improve, need analysis & understanding*)*
    2. Left hand pane labeled Looking Glass, should be Landmarks.
    3. Look at using PingER historical data to optimize alpha (agreed 4/12/07): Faran
    4. Evaluate whether using traceroute data helps (Suggested by Umar & Les 2/26/07, could add 3 more RTTs to minimize from): Faran
    5. Logs
      1. Review logs to see if complete: Faran, Les
        1. Add timestamps (7/9/07): Faran
        2. Add complete dns name of client (7/11/07): Faran
      2. Add password protection to reviewing logs(7/11/07): Faran
      3. Add log of failures, successes (7/11/07): Faran
    6. Add tiering (need to allow scaling to large numbers of landmarks)  (7/6/07): Faran
      1. Need a State column adding to the Sites List so can have tier 0 and 1 hosts and even Disable hosts without losing information (7/5/07), Faran looking at how to implement 7/26/07): Faran
        1. Decide whether to use PlanetLab as tier1 and others as tier0 (may be problem that will not have PlanetLab hosts in developing countries: faran
      2. Research effectiveness of tiering: Shahryar, Les
    7. Reduce size of Traceroute Results pane now traceroute is not done automatically (agreed 7/26/07): Faran
    8. Use proxy for making landmark requests (for log auditing, blocking, PlanetLab cookie) (7/6/07): Faran
      1. CGI script on proxy (limit simultaneous calls): Les, Shahryar
  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. 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. Add traceroute/Looking Glass servers in critical areas, if they have a common format (asked for 11/15/06). Nothing useful in http://www.caida.org/analysis/routing/reversetrace/. 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, Les sent another list from traceroute.org of some potential sites in East Asia and E. Europe): Faran
      4. Look into PlanetLab (18 China, 6 Brazil, 2 Uruguay, 2 Puerto Rico, plus lots in Europe and N. America): Shahryar, Faran
        1. Shahryar will send information to Faran 6/28/07: Shahryar
        2. Integrate script with TULIP: Faran
        3. Faran is writing CGI script in Perl so can use single host to make requests, at same time learning Perl so progress slow (7/26/07): faran
    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
  5. Analysis (need for examination 5/31/07)
    1. Provide API (agreed 6/28/07, changes to TULIP mean current API is not working): Faran
    2. Literature search on triangulation, multi-lateration: Faran
    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. Document Faran's algorithm, try new algorithm that does not require destination to be inside triangle: Faran, Umar
    5. Compare with GeoIP Tool & Hostip.info

      1. Find cases where TULIP beats GeoIP Tool [Done 4.68.116.16, probably backbone routers too] :

      2. Document comparison in Wiki: Shahryar
      3. Confidence estimates of accuracy
      4. Applied to PingER hosts
      5. Outside triangles, area coverage
      6. Effect/need to vary alpha: Faran
      7. Look at big discrepancies
    6. Provide bubble maps of accuracy: Faran
    7. What area/population is covered by TULIP
    8. Show accuracy by region and country: Faran
      1. Document in the TULIP web page: Faran
  6. 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: Faran
    5. Put Faran's final year project documentation online: Faran, Umar
  • No labels