|
|
|
|||||||
Networking Workshop
0368-3500-67
Semester II, 2003
Classes: Monday, 202 Dan-David, 14:00-16:00
Basic Requirements from all
projects:
·
Well
documented and usable:
The project
should be usable by others after you finish it and after you have left the
university. The code should be well
documented and explained with accompanying documents.
·
Presentation:
Projects should
have convenient presentation of the results, usually with graphical
presentation (when ever appropriate).
If necessary the project will have other easy to use outputs.
Suggested Projects
·
Beacons: BGP convergence measurements
Beacons are special boxes that own a specific
prefix (usually /24) and which they withdraw and announce periodically every
2 or 4 hours. I.e., they generate
artificial noise (as if there is something not artificial in the Internet)
into the BGP routing algorithm, which allows researchers like us to measure and
observe the BGP behavior. Two
requirements on these prefixes are:
1. That they are not used by
any customer, i.e., there is no real host behind any IP address in these
prefixes, and 2. that the ISP that
hosts the beacon machine would not aggregate that prefix with other
prefixes. Otherwise the noise would
not be felt outside that ISP AS (autonomous system). In this project you will learn more about
the beacons and collect information about the convergence of BGP as observed
on the beacons. The information
collected will have to be explained, and presented graphically.
Relevant
links:
·
RIS Routing Beacons
·
Tool for
prefix ownership check
As we teach in class, each prefix is owned by some
ISP (AS) or has not been assigned yet, in which case it is called bogon. (There are some specific prefixes which
are illegal, these are described in RFC1918). The tool we develop here will monitor who claims ownership on
each prefix and will alert as soon as a prefix owned by A is claimed by B, A
not equal B. The tool should have the
option to send an email alert to the contact of A.
Relevant
links:
· Routing tables achieve:o Routing Information Serviceo Oregon Route Views Project·
Measure
asymmetric routes in the Internet
In this project we will discover (s, t) pairs of
prefixes, or of IP addresses such that the route from s to t is different
from the route from t to s. We will
study the statistics of this phenomena and present it graphically. We will use two methods to measure and
discover these: 1. Using traceroute, 2. investigating the routing tables in RIPE
and Oregon.
Relevant
links:
· Routing tables achieve:o Routing Information Serviceo Oregon Route Views Project·
Measure dark
spaces in the Internet and their behavior
This project is
similar to the prefix ownership project.
Here we want to follow on IP addresses that become unavailable from
some parts of the Internet and re-appear.
By disappear we mean that these addresses/prefixes become
non-routable, i.e., some backbone routers stop having a route for these prefixes.
Relevant
links:
· Routing tables achieve:o Routing Information Serviceo Oregon Route Views Project·
Types
Updates statistics
In this project
we will collect statistics on the different types of BGP announcements and
withdrawals and study their meaning.
Relevant
links:
o Routing Information Service·
TTM: Test Traffic Measurements box
The purpose of
this project is to install a TTM box in Tel-Aviv and use it to collect
traffic measurements between TAU and other locations in the world.
Relevant
links:
o RIPE NCC Test Traffic Measurements Relevant and recommended links
o Griffin Homepage on interdomain routing
Suggested Books
Research
Groups:
o
The NLANR Measurement and
Network Analysis Group
o
CAIDA
|
|
|||||||
