1 / 21

Abilene Update

This document outlines the key developments from the Abilene initiative presented at the SC'99 conference in Portland on November 17, 1999. Focused on goals such as supporting high data rates (OC-48), minimizing latency, and providing SONET access, it details the core architecture comprising Cisco routers at various Qwest PoPs. The update emphasizes advanced IP functionalities like multicast and QoS, current connection statuses, and plans for future international peering. The commitment to boosting high-speed networking capabilities for advanced applications remains clear.

ilar
Télécharger la présentation

Abilene Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Abilene Update SC'99 :: Portland :: 17-Nov-99

  2. Outline • Goals • Architecture • Current Status • NGI Peering • International Peering • Multicast

  3. 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!

  4. 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

  5. Abilene Core :: Nov-1999 Seattle New York Cleveland Indianapolis Sacramento Denver Denver Kansas City Los Angeles Atlanta Houston

  6. Abilene Core :: spring 2000 Seattle New York Cleveland Indianapolis Sacramento Washington Denver Denver Kansas City Los Angeles Atlanta Houston

  7. 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

  8. Abilene Connections :: Nov-1999

  9. Abilene Connections :: now and in process

  10. Summary of Connections • Connections • 28 now • 9 on the way • Participants • 102 now • 27 on the way

  11. The Abilene Team • Qwest Communications • Nortel • Cisco • Indiana University (NOC) • MCNC and OARnet (ITEC) • UCAID

  12. 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

  13. JETnets Interconnections and Peering Sox/Atlanta vBNS Abilene @OC3 tc @OC12 tc ESnet @DS3? tc NGIX Public Exchange Point Private Exchange Point Sprint NY-NAP NGIX-CH (AADS) MCIW-PYM UCB/ CalREN Abilene vBNS vBNS vBNS Abilene (temp) @OC12 tc / pto @OC3 @DS3 @OC12 tc / pto @OC12 tc NREN DREN NREN DREN @OC3 sh / pto @OC3 pto @OC3 sh @?? pto ESnet NISN ESnet ESnet NISN ESnet NISN @OC3 sh / tc / pto @OC3 sh / pto @OC3 sh / pto @OC12 @OC3 sh @DS3 sh ?/ pto @DS3 pto NGIX-DC (UMCP) NGIX-SF (Ames) vBNS Abilene Abilene vBNS @OC3 tc ? @OC12 tc @OC12 tc @OC3 NREN DREN NREN DREN @OC3 @OC3 @OC3 @OC3? pto ESnet NISN ESnet NISN @OC3 sh ? @OC3 sh ? @OC3 sh ? @OC3 tc , pto MAX (BA ATM) FIX/MAE-West (Ames) vBNS Abilene (temp) @OC3 tc @OC3 tc NREN DREN @OC3 pto MAE-East @? pto SDSC ESnet vBNS NISN vBNS @DS3 pto @DS3 @OC3 tc , pto @OC12 tc DREN @?? pto ESnet NISN ESnet @DS3 pto @DS3 >OC3 pto @DS3 tc sh : SHared circuit to the exchange point tc : circuit also serving as Tail Circuit for some customers JETnet : connected to the exchange point pto : Peering Traffic with Others (non- JETnets ) goes on the same circuit JETnet : plan to connect to the exchange point temp: Temporary peering until a nearby NGIX is established JETnet : no current plan to connect but maybe desired JB 5Oct99

  14. 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

  15. 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

  16. New York City Europe ISP SURFnet NORDUnet Teleglobe Qwest Abilene Chicago

  17. New York City Europe ISP SURFnet NORDUnet Teleglobe Qwest Abilene Chicago

  18. 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

  19. 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

  20. 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!

More Related