Download - Abilene Update
Abilene Update
SC'99 :: Portland :: 17-Nov-99
Outline
• Goals• Architecture• Current Status• NGI Peering• International Peering• Multicast
Goals• Support very high data-rates
– OC-48 in phase 1
• Minimize speed-of-light delay• Provide Sonet access at over 100 Qwest
PoPs• Support advanced IP functionality such
as multicast and QoS• Support advanced applications!
Core Architecture• Router Nodes
– About 10-15, located at Qwest PoPs– Cisco 12008 routers– Out-of-band access, Surveyor
• Interior Circuits– Qwest OC-48 and OC-12 Sonet– Simple POS between Router Nodes
Seattle
Kansas City
Denver
Cleveland
New York
Atlanta
Houston
Abilene Core :: Nov-1999
Sacramento
Los Angeles
Denver
Indianapolis
Seattle
Kansas City
Denver
Cleveland
New York
Atlanta
Houston
Abilene Core :: spring 2000
Sacramento
Los Angeles
Denver
Indianapolis
Washington
Access Architecture• Access Circuit: site to Router Node
– OC-3, OC-12 now; OC-48 possible– IP/Sonet or IP/ATM framing
• Access Node: any Qwest Sonet PoP– Backhaul from Access Node to Router Node
viewed as part of Abilene– Local from site to Access Node varies
Abilene Connections :: Nov-1999
Abilene Connections :: now and in process
Summary of Connections• Connections
– 28 now– 9 on the way
• Participants– 102 now– 27 on the way
The Abilene Team• Qwest Communications• Nortel• Cisco• Indiana University (NOC)• MCNC and OARnet (ITEC)• UCAID
NGI Peering• Internet2 and federal NGI networks peer
at a set of NGI exchanges, or NGIXes– Chicago (same ATM switch as StarTAP)– NASA Ames– Univ Maryland College Park, near DC
• Other ad hoc connection points also exist
JETnets Interconnections and Peering
MAE-EastvBNS@DS3
NISN@DS3>OC3 pt
o
DREN@?? pt
oESnet@DS3 pt
o
NGIX-CH (AADS)
Abilene@OC12 tc /pt
o
vBNS
@OC12 tc /pto
NREN@OC3 sh /pt
o
NISN@OC3 sh /pt
o
DREN@OC3 pt
oESnet@OC3 sh /tc /pt
o
Sprint NY-NAPvBNS@DS3
NISN@DS3 pt
o
DREN@?? pt
oESnet@DS3 sh ?/pt
o
MCIW-PYMvBNS@OC3
NREN@OC3 sh
NISN @OC3 sh
ESnet@OC3 sh /pt
o
NGIX-DC (UMCP)Abilene@OC12 tc
vBNS
@OC3 tc ?
NREN@OC3
NISN@OC3 sh ?
DREN@OC3
ESnet@OC3 sh ?
MAX (BA ATM)Abilene (temp)@OC3 tc
vBNS
@OC3 tc
SDSCvBNS
@OC12 tc
ESnet@DS3 tc
NGIX-SF (Ames)Abilene@OC12 tc
vBNS@OC3
NREN@OC3
NISN@OC3 tc ,pt
o
DREN@OC3? pt
oESnet@OC3 sh ?
FIX/MAE-West (Ames)
NISN@OC3 tc ,pt
o
DREN@? pt
oESnet@DS3 pt
o
Sox/Atlanta
Abilene@OC12 tc
vBNS
@OC3 tc
ESnet@DS3? tc
UCB/ CalREN Abilene
(temp)@OC12 tc
ESnet@OC12
sh : SHare
d circuit to the exchange point tc : circuit also serving as Tail Circuit for some customerspto : Peering Traffic with Others (non-JETnet
s ) goes on the same circuittemp: Temporary peering until a nearby NGIX is established
NGIXPublic Exchange PointPrivate Exchange Point
JETnet : connected to the exchange point JETnet : plan to connect to the exchange pointJETnet : no current plan to connect but maybe desired
JB 5Oct99
NREN@OC3 pt
o
Specific Abilene NGI Peering• vBNS: Chicago and Washington• NREN: Ames and Chicago• NISN: Chicago• DREN: Ames and Chicago• ESnet: Berkeley, Chicago, Atlanta
• Theme: reduce latency in univ-lab paths
International Peering• Focused on non-US advanced R/E
networks• Supports StarTAP exchange point• But also uses other peering locations to
minimize:– latency– cost burden for peer
ISPSURFnet
NORDUnet
Chicago
New York City Europe
Teleglobe
Qwest
Abilene
ISPSURFnet
NORDUnet
Chicago
New York City Europe
Teleglobe
Qwest
Abilene
Joint Techs Meeting• Miami, Florida, 6-8 December 1999• Joint project of:
– Internet2– NLANR
• Advanced networking technology and infrastructure consultation
• www.internet2.edu/html/dec99miami.html
Goals for SC'00• Increase support for native multicast• Increase experience with high-speed
wide-area TCP– Web100 project beginning
• Make OC-12 (600 Mb/s) performance ordinary
The Bottom Line for SC'99• The aggressive combination of high-
speed computing and high-speed networking is exactly why Internet2 infrastucture, including Abilene, have been built
• We welcome the challenge to support this!