TransPAC

1
US TransPAC Report
James Williams williams_at_iu.edu TransPAC Project
Manager Indiana University February 20, 2001
2
TransPAC activities for 2000

• John Hicks was hired as the TransPAC High
  Performance Computing and Communications (HPCC)
  applications engineer (jhicks_at_iu.edu).
• Chris Robb was hired as the TransPAC Network
  Engineer (chrobb_at_indiana.edu).
• Goals for TransPAC include working with network
  engineers and scientists to develop, debug,
  monitor, and provide analysis for international
  network applications.
• Other goals include providing support for
  advanced network services (e.g., Mbone, IPv6, and
  QoS).

3
TransPAC activities for 2000 (cont.)

• TransPAC annual report was completed and
  submitted to the US National Science Foundation
  (NSF) on July 30, 2000.
• Copies are available.

4
TransPAC activities for 2000 (cont.)

• TransPAC participated in the International Grid
  (iGrid) demonstration at INET2000, Yokohama,
  Japan 18 21 July 2000.
• iGrid featured 24 applications from 14 regions.
• Applications included tele-immersion, large
  datasets, distributed computing, remote
  instrumentation, streaming media, and
  high-definition television.
• iGrid is connected to the JGN, the WIDE Project
  Network (in cooperation with NTT, TTNet, and
  PNJC), APAN and APAN/TransPAC link to STAR TAP.

5
TransPAC activities for 2000 (cont.)

• New TransPAC Web page design (http//www.transpac.
  org)
• Features include
• ? News items
• ? Application database
• ? Network Operations Center
• ? Support services
• ? Engineering

6
TransPAC activities for 2000 (cont.)

• TransPAC HPIIS Performance Review, October 25,
  2000
• Positive response on all HPIIS networks
• Funding provided for next two years

7
TransPAC activities for 2000 (cont.)

• NLANR/Joint Techs meeting in Hawaii January 2001,
  jointly sponsored by TransPAC
• APAN Hawaii meeting

8

The Global Research Network Operations Center
(Global NOC) at Indiana University manages the
international network connections from advanced
research and education networks in the
Asia/Pacific, Europe, Russia and South America to
the Science Technology and Research Transit
Access Point (STAR TAP) and the leading US high
performance research and education networks.
9
(No Transcript)
10
(No Transcript)
11
Global NOC Functions

• Problem reporting, monitoring, resolution
• Report generation, distribution, archiving
• Web page development, maintenance
• Tool development, maintenance

12
Global NOC Future Plans

• Continued Web page development
• Packaging and deployment of traffic analysis
  tools
• Deployment of Abilene multicast tools
• NOC process analysis

13
Global NOC Future Plans(continued)

• Closer linkage between other NOCs (vBNS, ESNET,
  Canarie, APAN) to increase tool sharing and
  process cooperation (such as the NOC session in
  Hawaii)
• Closer linkage with national tool and measurement
  efforts
• Development of NOC Knowledge Base

14

• http//globalnoc.iu.edu/

15
Questions??

• Jim Williams
• williams_at_iu.edu

16
ATT TransPAC Link Report

• Jim Williams for Chris Stelter

17
TransPAC Link Status

• The TransPAC network currently runs from the
  Tokyo XP to the STAR TAP in Chicago.
• TransPAC was upgraded from 100Mpbs to 155 Mbps
  (122Mbps) on November 15, 2000.
• The current TransPAC configuration is referred to
  as the TransPAC Northern Route.

18
TransPAC Link Upgrades

• Current upgrades include development of the
  TransPAC Southern Route.
• Southern route consists of two pieces
• ? 45Mbps network from Tokyo to Hawaii. (in
  place today)
• ? 45Mbps network from Hawaii to the U.S.
• peering with Abilene on the west coast

19
TransPAC Link Upgrades (cont.)

• The TransPAC Project annual bandwidth renewal
  will occur in October 2001.
• In March 2001, TransPAC will request RFP
  responses for a two year extension (October
  2003).
• TransPAC will pursue expanding northern route to
  OC12.
• TransPAC will pursue expanding southern route to
  OC3.

20
Questions??

• Jim Williams
• williams_at_iu.edu
• Note - this is an item for discussion later on
  the agenda

21
Abilene ITN Engineering

• Brent Sweeny
• sweeny_at_iu.edu
• Indiana University

22
What is ITN?

• Basically, that participating peer networks can
  talk with each other across Abilene (and CAnet3,
  and STAR TAP).
• (for CAnet3 and STAR TAP peers traffic to be
  accepted by Abilene, there must be an Abilene MoU
  for that peer. Examples of outliers MIRnet,
  GEMnet)

23
Current Abilene Peer Networks

• 32 connections to 19 peer networks
• USA vBNS, Esnet, NREN, NISN, DREN
• 14 non-USA networks in Asia, Europe, Middle East,
  South America
• Non-USA connections at Chicago, New York,
  Seattle, Los Angeles

24
Abilene ITN Peer Networks

• APAN (Asia-Pacific Korea, Japan, Australia,
  Singapore)
• CANet3 (Canada)
• CERNET (China)
• CUDI (Mexico)
• IUCC (Israel)
• JANET (U.K.)
• NORDUnet (Scandanavian countries)
• RENATER (France)
• REUNA2 (Chile)
• SINET (Japan a.k.a. NII)
• SingAREN (Singapore)
• SURFnet (Netherlands)
• TANET2 (Taiwan)
• vBNS (USA)

25
Abilene ITN non-participants

• Only USA Fednets

26
How is it done?

• Peers were polled (early October 2000)
• All new peers are participants
• CAnet3, STAR TAP, and Abilene have agreed on a
  set of BGP community markings to indicate ITN
  status
• AS2501 ITN participant
• AS2500 ITN non-participant

27
How is it done?
28
For more information

• www.ucaid.edu/abilene/html/itnservice.html
• www.abilene.iu.edu/index.cgi?pagecommunity