A Challenge: Modeling the Dynamics of the Inter-domain Routing in the Internet. Timothy G. Griffin Matthew Roughan Computer Laboratory School of Mathematical Sciences University of Cambridge University of Adelaide, Australia
A Challenge:Modeling the Dynamics of the Inter-domain Routing in the Internet
Timothy G. Griffin Matthew Roughan
Computer Laboratory School of Mathematical Sciences
University of Cambridge University of Adelaide, Australia
Mathematics for Networks Workshop
March 23 2005
EGP (= BGP)
IGP = Interior Gateway Protocol
Metric based: OSPF, IS-IS, RIP,
EGP = Exterior Gateway Protocol
Policy based: BGP
The Routing Domain of BGP is the entire Internet
Establish session on
TCP port 179
is ALIVE exchange
route UPDATE messages
Jan 11, 2005
Thanks to Geoff Huston: http://www.potaroo.net/
Jan 11, 2005
From AS 4637: Reach Network
rrc00.ripe.net at RIPE NCC, Amsterdam, collects default free routing updates from peers. From October 1999.
rrc01.ripe.net at LINX, London. Collects route updates announced by LINX members. From July 2000.
rrc02.ripe.net at SFINX, Paris. Collects route updates announced by SFINX members . From March 2001.
rrc03.ripe.net at AMS-IX, Amsterdam. Collects route updates announced by AMS-IX members. From January 2001.
rrc04.ripe.net at CIXP, Geneva. Collects route updates announced by CIXP members. From April 2001.
rrc05.ripe.net at VIX, Vienna. Collects route updates announced by VIX members. From June 2001.
rrc06.ripe.net at Otemachi, Japan. Collects route updates announced by JPIX members. From August 2001.
rrc07.ripe.net in Stockholm, Sweden. Collects route updates announced by the NETNOD members. From April 2002.
rrc08.ripe.net at San Jose (CA), USA. Collects route updates announced by the MAE-WEST members. From May 2002.
rrc09.ripe.net at Zurich, Switzerland. Collected route updates announced by the TIX members. From May 2003 to until early Feb 2004.
rrc10.ripe.net at Milan, Italy. Collects route updates announced by the MIX members. From Nov 2003.
rrc11.ripe.net at New York (NY), USA. Collects route updates announced by the NYIIX members. From Feb 2004.
rrc12.ripe.net at Frankfurt, Germany. Collects route updates announced by the DE-CIX members. From Jul 2004.
AOL (NoVa) 220.127.116.11 through AS1668
APAN (tpr2-tokyo) 18.104.22.168 through AS7660
ATT (SFO) 22.214.171.124 through AS7018
Abilene (Indiana) 126.96.36.199 through AS11537
Accretive (PAO) 188.8.131.52 through AS11608
Accretive (SEA) 184.108.40.206 through AS11608
Army Research Lab 220.127.116.11 through AS13
Broadwing (ADDS) 18.104.22.168 through AS6395
Broadwing (MAE-EAST) 22.214.171.124 through AS6395
Broadwing (MAE-WEST) 126.96.36.199 through AS6395
C&W USA (Santa Clara) 188.8.131.52 through AS3561
COMindico (AU) 184.108.40.206 through AS9942
Carrier1 (NYC) 220.127.116.11 through AS8918
EBONE (EU) 18.104.22.168 through AS1755
ELI (MAE-EAST) 22.214.171.124 through AS5650
ELI (MAE-WEST) 126.96.36.199 through AS5650
EPOCH (PAIX) 188.8.131.52 through AS4565
ESnet (GA) 184.108.40.206 through AS293
France Telecom (NYC) 220.127.116.11 through AS5511
GLOBIX (LINX) 18.104.22.168 through AS4513
GLOBIX (New York) 22.214.171.124 through AS4513
GLOBIX (Chicago) 126.96.36.199 through AS4513
GLOBIX (Palo Alto) 188.8.131.52 through AS4513
GT Group Tel (Toronto,CA) 184.108.40.206 through AS6539
Genuity (Palo Alto) 220.127.116.11 through AS1
GlobalCrossing (PAIX) 18.104.22.168 through AS3549
IAGnet (Chicago) 22.214.171.124 through AS267
IIJ (Japan) 126.96.36.199 through AS2497
ISC (Palo Alto) 188.8.131.52 through AS3557
Intermedia (MAE-EAST) 184.108.40.206 through AS2548
JINX (Johannesburg) 220.127.116.11 through AS2905
Jippii (ESPANIX/Spain) 18.104.22.168 through AS8782
LINX (London) 22.214.171.124 through AS5459
Level3 (Denver) 126.96.36.199 through AS3356
MFN/AboveNet (MAE-WEST) 188.8.131.52 through AS6461
MFS/MAE-lab (San Jose) 184.108.40.206 through AS6066
Nacamar (Frankfurt) 220.127.116.11 through AS3257
Netrail (MAE-WEST) 18.104.22.168 through AS4006
Port80 (Stockholm) 22.214.171.124 through AS16150
RCN (PAIX) 126.96.36.199 through AS6079
RCN (VA) 188.8.131.52 through AS6079
RIPE NCC (Amsterdam) 184.108.40.206 through AS3333
STARTAP (Chicago) 220.127.116.11 through AS10764
Sprint (Stockton) 18.104.22.168 through AS1239
Telefonica (New York) 22.214.171.124 through AS12956
Teleglobe (London,UK) 126.96.36.199 through AS8297
Teleglobe (PAIX) 188.8.131.52 through AS6453
Telstra (Sydney,AU) 184.108.40.206 through AS1221
TELUS (Toronto) 220.127.116.11 through AS852
TouchAmerica () 18.104.22.168 through AS19092
Verio () 22.214.171.124 through AS2914
Verio () 126.96.36.199 through AS2914
WCI Cable (Hillboro, OR) 188.8.131.52 through AS14608
Williams (San Francisco) 184.108.40.206 through AS7911
Williams (San Francisco) 220.127.116.11 through AS7911
X0 (Bay Area) 18.104.22.168 through AS2828
Zocalo (Berkeley) 22.214.171.124 through AS715
blackrose.org (Ann Arbor) 126.96.36.199 through AS234
netINS (Des Moines) 188.8.131.52 through AS5056
Many streams since 2001
route_btoa translates binary to ASCII
Data from rrc01.ripe.net (LINX, London)
Can we develop rigorous stochastic models for
Thanks to Abha Ahuja and Craig Labovit for this plot.
Real-time Global Routing Metrics
What is the sound of one route flapping?