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 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-East vBN pt o pt o ESne pt o NGIX-CH (AADS) tctc / pt o vBN tctc / pt o shsh / pt o shsh / pt o pt o ESne shsh / tctc / pt o Sprint NY-NAP vBN pt o pt o ESne shsh ?/ pt o MCIW-PYM vBN shsh shsh ESne shsh / pt o NGIX-DC (UMCP) tctc vBN tctc ? shsh ? ESne shsh ? MAX (BA ATM) Abilene tctc vBN tctc SDSC vBN tctc ESne tctc NGIX-SF (Ames) tctc vBN tctc, pt o pt o ESne shsh ? FIX/MAE-West (Ames) tctc, pt o pt o ESne pt o Sox/Atlanta tctc vBN tctc ESne tctc UCB/ CalRE N Abilene tctc ESne shsh : SHare d circuit to the exchange point tctc : circuit also serving as Tail Circuit for some customers pt o : Peering Traffic with Others (non- JETnet s ) goes on the same circuit temp: Temporary peering until a nearby NGIX is established NGIX Public Exchange Point Private Exchange Point JETne t : connected to the exchange point JETne t : plan to connect to the exchange point JETne t : no current plan to connect but maybe desired JB 5Oct99 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
ISP SURFnet NORDUnet Chicago New York City Europe Teleglobe Qwest Abilene
ISP SURFnet 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
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!