International Connectivity International Task Force Meeting Fall 2005 Internet2 Member Meeting

1
International ConnectivityInternational Task
Force MeetingFall 2005 Internet2 Member Meeting

• 19 September 2005
• Philadelphia, PA
• USA

2
International connectivity

• Transatlantic Networking in the LHC Era -Harvey
  Newman, CalTech (USA)
• ESnet international update - Joe Burrescia,
  ESnet, (USA)
• Abilene International Connectivity -- Peering
  policies, implementation and new updates Ana
  Preston, Chris Robb, Brent Sweeny (Abilene
  NOC/Engineering)
• IRNC Program and Updates
• TransPAC2
• TransLight/StarLight
• WHREN
• GLORIAD
• TransLight/Pacific Wave

3
Abilene International Connectivity

• Non-US network has to be under the cover of a
  Memorandum of Understanding (MoU) between
  Internet2 and in that country, that organization
  with goals and objectives similar as those of
  Internet2 in the United States.
• The non-US network with who we interconnect must
  complete an Interconnection Agreement with
  Abilene (also referred to as a Peering agreement)
• direct peerings with Abilene (network with
  networks behind)

4
Networks reachable via Abilene - by country
Last updated September 2005
Europe-Middle East
Asia-Pacific
Americas
Austria (ACOnet) Belgium (BELNET) Bulgaria
(ISTF) Croatia (CARNet) Czech Rep.
(CESNET) Cyprus (CYNET) Denmark
(Forskningsnettet) Estonia (EENet) Finland
(Funet) France (Renater) Germany (G-WIN) Greece
(GRNET) Hungary (HUNGARNET) Iceland
(RHnet) Ireland (HEAnet) Israel (IUCC) Italy
(GARR) Latvia (LATNET) Lithuania
(LITNET) Luxembourg (RESTENA)
Argentina (RETINA) Brazil (RNP2/ANSP) Canada
(CAnet) Chile (REUNA) Mexico (Red-CUDI) United
States (Abilene)Peru (RAAP) Venezuela
(REACCIUN-2)
Malta (Univ. Malta) Netherlands (SURFnet) Norway
(UNINETT) Poland (POL34) Portugal (RCTS2) Qatar
(Qatar FN) Romania (RoEduNet)Russia
(RBnet) Slovakia (SANET) Slovenia (ARNES) Spain
(RedIRIS) Sweden (SUNET) Switzerland
(SWITCH) United Kingdom (JANET) Turkey
(ULAKBYM) CERN
Australia (AARNET) China (CERNET, CSTNET,
NSFCNET) Hong Kong (HARNET) Japan (SINET, WIDE,
JGN2) Korea (KOREN, KREONET2) Singapore
(SingAREN) Philippines (PREGINET) Taiwan (TANet2,
ASNet) Thailand (UNINET, ThaiSARN)
Central Asia
Africa
Algeria (CERIST) Egypt (EUN/ENSTIN) Morocco
(CNRST) Tunisia (RFR) South Africa (TENET)
Armenia (ARENA) Georgia (GRENA) Kazakhstan
(KAZRENA) Tajikistan (TARENA) Uzbekistan (UZSCI)
More information at http//abilene.internet2.edu/
peernetworks/international.html
5
Peering with Abilene

• How?
• Via international exchange points
• via international links (often funded by US
  agencies like National Science Foundation)
• if via a layer-2 exchange point (i.e., where
  non-US network is expected to connect to a Layer
  2 switch)
• a VLAN is set up between Abilene and the non-US
  peer
• Other alternatives
• reviewed case by case
• Other alternatives include via eBGP multihop
  peering(s) and GRE/MPLS tunnels

6
International connectivity
September 2005
7
International Transit Network service

• Unless noted, implemented for all non-US peers
• Transit to Fednets (over Abilene) for non-US
  peers (and viceversa)
• Only if requested by both peers (peers to work
  out any conditions)
• Case by case review
• Please contact Ana for more information.

8
Issues to bring up

• Transit
• Want to make sure we better understand what other
  networks are transiting our international peers
• Route preferences (with multiple links, which one
  is preferred?)
• IPv6 (Brent Sweeny)

9
(No Transcript)
10
Abilene IPv6 routing policy

• Matt Davy Abilene NOC
• Presented by Brent Sweeny Abilene NOC

11
Background

• Abilene IPv4 Unicast Routing Policy
• Relaxed COU for Advanced Services (Multicast
  and IPv6)
• In Practice Full Route Swapping
• Peering _at_ MIX (California) some multicast, very
  few IPv6

12
(No Transcript)
13
Recent changes (and consequences)

• Added Peering at PAIX Palo Alto (California)
• ISPs only want our customer routes
• Abilene has global IPv6 connectivity (roughly 850
  routes)
• Kreonet (Korea) appears to be the only network
  providing transit to Abilene
• roughly 150-200 IPv6 routes go through Kreonet
• complaints of very long paths between Abilene and
  commercial ISPs, especially in Europe

14
Questions

• Should Abilene provide global IPv6 connectivity ?
• Can campuses gigapops get reasonable IPv6
  service from ISPs ?
• Is there an acceptable multihoming solution that
  works for everyone ?

15
Questions

• How can Abilene increase the robustness of its
  IPv6 peering?
• Commercial peering at both coasts (and midwest)?
• Transit from more than 1 provider ?
• How much bandwidth ?
• Should we pursue robust peering in addition to
  transit providers

16
Questions

• Should IPv6 policy match IPv4 Unicast policy ?
• Should Abilene accept commercial IPv6 routes from
  Connectors and other NRNs ?
• Example Korean RE network advertising IPv6
  routes to Korean ISPs

17
Direction

• Discussions over the past few months on how to
  proceed
• Exploring IPv6 transit options with ISPs
• Reviewing the Abilene ITN policy - will take into
  account IPv4 Multicast IPv6 as well as IPv4
  Unicast
• What are the IPv6 peering policies of our peer
  RE networks, both US international? What
  should those policies be?

18
(No Transcript)