90 likes | 197 Vues
This discussion addresses the urgent need for greater diversity in inter-continental links among research and education (R&E) network operators. It highlights the current lack of coordination in link procurement, which can lead to multiple networks relying on the same physical cables, increasing vulnerability. Key questions include how to obtain and share information about cable usage, the feasibility of prioritizing diversity in procurement, and the potential of enhancing routing policies. The aim is to improve resilience and connectivity across global research networks.
E N D
CCIRN topic: diversity of inter-continental links Heather Boyles, Internet2 heather@internet2.edu
Topic of Coordination for CCIRN? • Should we as R&E network operators do something about achieving more diversity in our inter-continental links connecting our respective networks?
Issues • Currently no real coordination between R&E networks in procurement • often not aware of what cables others' links are being provisioned on • where multiple entities procuring for same route (e.g. Amsterdam-New York or Tokyo-LA), it could be that all of our circuits are on the same physical cable (even if procured from different vendors) • move to 'unprotected' circuits from vendors means more relying on backup with each other (e.g. JGN2 and TransPAC2, GEANT and NSF IRNC-funded links)
Questions • Can we get information from vendors about which cable our circuits are on? (yes, seems to be the answer) • How to capture that information and share? • Are there issues in sharing publicly? • Can we get those procuring circuits to consider diversity as a desirable feature or a proposal? • At what point in process is this information useful? • Is it worth the effort? How big of an issue is this? • for routed IP, maybe not: enough multiple interconnections and open transit in R&E network community that occasionally cable outages don't mean complete unreachability (see the Taiwan straits case from New Year's 2007) - maybe just need more open transit policies, routing coordination • for circuit services, maybe so: less re-routablity (since not using IP routing)?
GEANT2 and other trans Atlantic links Courtesy: Guy Roberts, DANTE
Courtesy: Dan Nae, CalTech Circuit Status NYC 111 8th Bellport NYC-MANLAN Bude Whitesands AC-2 AMS-SARA VSNL North VSNL Frankfurt Highbridge GVA-CERN NY60 Hudson Wal, NJ CHI-Starlight VSNL South Paris Global Crossing Qwest Pottington (UK) Colt London Atlantic Ocean GEANT • Unprotected circuits (lower cost) • Service availability from provider’s offers: • Colt Target Service Availability is 99.5% • Global Crossing guarantees Wave Availability at 98% • Canarie and GEANT: No Service Level Agreement (SLA) LCG Availability requirement: 99.95% LHC OPN Meeting, Munich
Vendor Usage in Atlantic • Global Crossing • SURFnet (1) • IRNC (1) (procured by SURFnet) • Internet2 • CANARIE • VSNL • IRNC ( • IEEAF • GEANT2 • LHCnet (one on north, one on south) • FLAG • GEANT2 • T-Systems • GEANT2 • Qwest • LHCnet (Yellow/AC-2)
Cable Usage in the Atlantic • VSNL North • VSNL South • AC-2/Yellow • FLAG Atlantic-1 (FA 1) • AC-1 • North • South • TAT14
Pacific Diversity • George…..