Hi! I'm a PhD student in the University of Oregon Computer Science Department. I am advised by Andrzej Proskurowski.
For my PhD I'm taking a long term survey of the internet topology, and trying to track what political, economic, and technological factors have helped and hindered the internet's growth, robustness, efficiency, and internationality. This involves a bit of historical digging and reading all about various controversial decisions and events, but much more graph theory and statistics. The graph series I'm generally looking at is the internet's AS graph, and the best source of historical data for the AS graph is the University of Oregon Computing Center's Routeviews Project, but if you have access to other long-term internet data, I would love to get my hands on it!
When I was in the throes of doing my area exam, I compiled a list of area exam tips and tricks. With other peoples' contributions included, it kind of morphed into an overall hints page, but I'm keeping the title.
I've also made a University of Oregon theme for Beamer that I encourage you to use if you want to make presentations in LaTeX and you want a UO theme.
If you'd like to get in touch with me, my email address is peter@cs.uoregon.edu, my office phone is 541-346-4436, and my office number is Deschutes 254 . My door is always open!
| Sole Instructor and Course Designer | Assisted |
|---|---|
|
|
Graduate Student in Computer Science at the University of Oregon, 2002-???
Software developer at Gordian 2000-2002
Joint Major in Mathematics and Computer Science, Harvey Mudd College 1996-2000
[ix.cs.uoregon.edu]
Login name: peter In real life: Peter Boothe
Directory: /home/users/peter Shell: /bin/bash
Last login Mon Nov 2 09:30 on ssh from 149.61.3.21
Mail last read Fri Nov 6 05:47:32 2009
Project: Do my area exam.
Plan:
Paper on the completeness of Routeviews is due on the 27th
How complete is Routeviews? How wrong is everyone to treat it as symmetric
and complete?
Theory approach:
Formally write down the local optimality property of BGP, and then take
the routeviews graph and add in the maximum number of edges that could be
unseen without violating the optimality property at any of the ASs we
have full feeds from.
Statistical/Experimental approach:
Look at the routeviews peers, and characterize those ASs - maybe Tiers 1
through 3, maybe something like edge vs core - and then see how the
routeviews view changed with each additional feed. Then, we take the
total number of ASs of each type, and try and generate a full view of
what is going on
There are other approaches, but these seem the best.
4 comment(s)
A
Note - there is no HTML allowed in comments. Newlines become <br/> tags.