GLIF tech update iGrid2005Calit2, UCSD La Jolla, 29 September 2005 PowerPoint PPT Presentation

presentation player overlay
1 / 12
About This Presentation
Transcript and Presenter's Notes

Title: GLIF tech update iGrid2005Calit2, UCSD La Jolla, 29 September 2005


1
GLIF tech updateiGrid2005_at_Calit2, UCSDLa
Jolla, 29 September 2005
Erik-Jan.Bos_at_surfnet.nl Rene.Hatem_at_canarie.ca http
//www.glif.is/working-groups/tech/
2
GLIF tech WG - who
  • one of four GLIF WGs
  • support from TERENA secretary is Kevin Meynell
  • was closed now open to all, à la GGF et IETF
  • majority of participation to date has been by
  • - snr network engineers and network
    infrastructure directors of GLIF resource
    providers
  • - equipment vendors
  • - a few applications people
  • - one scientist

3
GLIF tech WG - history
  • Lambda workshops, i.e. Pre-GLIF meetings, in
    Amsterdam, NL (Sep 2001 and Sep 2002)
  • GLIF Tech 1 Reykjavik, IS Aug 2003
  • GLIF Tech 2 Nottingham, UK Sep 2004
  • - officially 29 participants
  • GLIF Tech 3 Salt Lake City, UT, USA Feb 13,
    2005
  • - oficially 34, but 50 counted
  • GLIF Tech 4 San Diego, CA, USA Sep 30,2005

4
GLIF tech WG - mandate
  • to design and implement an integrated global
    lambda infrastructure
  • - make it easier to for researchers to find and
    obtain end-end LightPaths
  • - focus is on today's coordination difficulties
    that can be addressed now
  • - provides a common ground for advancement

5
GLIF tech WG - tasks (1/2)
  • define standard "good enough" terms, i.e. to the
    extent that it will assist us in getting the job
    done
  • document and update GLIF resources
  • - GLIF optical exchanges
  • - GLIF lambdas
  • document and update GLIF resource provider
  • - policy information, and
  • - process guidelines
  • discuss, document, and encourage covergence
    regarding end-end LightPath Fault Management

6
GLIF tech WG - tasks (2/2)
  • document and update GLIF resource provider NOC
    and admin contact information
  • establish and maintain regular GLIF open-exchange
    coordination calls
  • discuss, document, and encourage covergence with
    respect to solutions to technical problems
  • work with the Ctrl plane WG
  • - share knowledge of provisioning as done today
  • - can invoke Tech for specific tasks

7
GLIF infrastructure update
  • large-scale GLIF open exchanges
  • - NetherLight (Amsterdam)
  • - MAN LAN (New York)
  • - new CANARIE-StarLight (Chicago)
  • - new CANARIE-PNWGP (Seattle)
  • more being added
  • - TokyoLight
  • - HongKongLight
  • - BusanLight

8
NetherLight
9
MAN LAN
10
StarLight GLIF open exchange (9 Sept)
OC-192 to Vancouver
OC-192 to Toronto
OC-192 to Winnipeg
2nd OC-192 to Toronto
OC-192 to Amsterdam
OC-192 to F10
IRNC OC-192 to Amsterdam
2nd OC-192 to F10
2x GbE to F10
GLIF node CANARIE HDXc SURFnet donated ONS
15454
TWAREN OC-48
11
Seattle GLIF open exchange (8 Sept)
CANARIE HDXc PNWGP 15454 dedicated
KREONet2/GLORIAD 15454
OC-192 to Victoria
OC-192 to Vancouver
OC-192 to Calgary
OC-192 to Busan
OC-192 to Vancouver (4th wave)
OC-192 to Chicago (5th wave)
OC-48 to Taipei
OC-192 to Tokyo
GbE to PWave switch 2nd GbE to PWave switch
12
GLIF tech WG - meeting 4
  • Agenda
  • Part 1 - joint Tech and Ctrl plane WG meeting
  • 1) seperation of mandate between Tech and Ctrl
  • 2) common terms and "good enough" definitions
  • 3) GLIF resource update
  • 4) Resource repository approaches / solutions
  • Part 2 - Tech WG meeting
  • 5) GLIF Open-exchange coordination
  • 6) Fault Management
  • 7) Policy and resource scheduling
  • 8) Developments in Transcontinental Ethernet
  • We'd love to see you there!
Write a Comment
User Comments (0)
About PowerShow.com