Connect Communicate Collaborate DEVELOPMENTS IN GANT 2 ENDTOEND

Connect. Communicate. Collaborate DEVELOPMENTS IN GÉANT 2: END-TO-END SERVICES Roberto Sabatino - DANTE (roberto@dante. org. uk) I 2 fall meeting 4 December 2006

Agenda Connect. Communicate. Collaborate • GÉANT 2 briefing and developments • End to end services and the hybrid infrastructure • GÉANT 2 activity JRA 3 (Bo. D) introduction • Monitoring 2

GÉANT 2 Connect. Communicate. Collaborate Some New Facts & Figures… • • • 25 POPs (+4) serve >30 NRENs 11600 km of fibre + 140 ILA sites 50+ x (own) 10 G lambdas 9 x (leased) 10 G lambda 8 x 2. 5 G (leased) “lambda” + some lower speed links Juniper T 640, M 160, M 40 routers NREN accesses at up to 10 Gbps (+ backup) + P 2 P 4 x 10 G to North America POP in NY connections to other R&E networks as before : Abilene, ESnet, CA*net 4, SINET, TENET, Red. CLARA, EUMEDCONNECT, TEIN 2 3

The GÉANT 2 fibre topology Connect. Communicate. Collaborate Core fibre topology (initial) Figures in circles represents the number of lambdas Valid at July 2006 4

Agenda Connect. Communicate. Collaborate • GEANT 2 status and developments • End to end services and the hybrid infrastructure • JRA 3 introduction • Monitoring 5

Services over GÉANT 2 Connect. Communicate. Collaborate Point-to-point GE (GE access) POP C POP A Essentially an implementation of ITU-T G. 8011. 1 EPL service Type 1 GÉANT 2 POP D POP B Features: • uses GFP/VCAT • GE port per instance • more dynamic • sub 1 G possible 6

Services over GÉANT 2 Connect. Communicate. Collaborate Point-to-point GE (10 GE access) POP C POP A VLAN X VLAN Y Essentially an implementation of ITU-T G. 8011. 2 EVPL service Type 1 GÉANT 2 POP D POP B Features: • uses GFP/VCAT • 10 GE port (supporting multiple instances) • use 802. 1 Q VLAN tags as IDs • sub (or >) 1 G possible 7

Services over GÉANT 2 Connect. Communicate. Collaborate Point-to-point GE (10 G SDH access) POP C POP A VCG X VCG Y GÉANT 2 POP D POP B Features: • uses GFP/VCAT • 10 G SDH port • GFP done in NREN • sub 1 G possible 8

Services over GÉANT 2 Connect. Communicate. Collaborate Managed wavelength service POP C POP A GÉANT 2 POP D POP B Features: • 10 G only • SONET/SDH or 10 GE LAN PHY • static • 10 GE is “full-rate” 9

LCG TIER 0 – TIER 1 Optical Private Network - OPN, RAL Connect. Communicate. Collaborate Nordugrid FNAL BNL TRIUMF ASCC UK DK CERN T 0 CH NL SARA GEANT 2 DE FR IT ES GRIDKa IN 2 P 3 PIC CNAF 10

Agenda Connect. Communicate. Collaborate • GEANT 2 status and developments • End to end services and the hybrid infrastructure • JRA 3 introduction • Monitoring 11

The JRA 3 Activity of GN 2 Connect. Communicate. Collaborate • JRA 3 is investigating the provision of ‘Bandwidth on Demand’ services to the NREN community • The goal implies an environment that is: – Multi-domain – Using multiple transmission technologies • SDH, GFP over SDH, L 2 MPLS VPN, Ethernet • Requirements for: – end-to-end delivery of a non-contended capacity – a standardized interface for service requests at end-points – service level indication to end-users – advance reservation (scheduled) – modular and technology independent implementation 12

JRA 3 architecture Connect. Communicate. Collaborate Key elements: - Inter-Domain manager (IDM) - Domain manager (DM) - Resource modeling (aka Abstract representation) - Path finder - Technology proxies - Standardized interfaces L 2 MPLS VPN Each domain participating in the Bo. D service provisioning needs to operate an IDM and honor the IDM-DM and IDMIDM interfaces. The local DM can be any technology, just a proxy is needed towards the IDM 13

JRA 3 Distributed approach Connect. Communicate. Collaborate (1) (6) (4) (10) (3) (9) (5) (8) (7) Inter-domain path-finding (2) 14

JRA 3: Current status Connect. Communicate. Collaborate • Framework and Architecture defined • IDM functional specification released • IDM phase 0 (simplified in some modules) implementation and testing done • Draft abstract notation available • Working on Pathfinding module , IDM phase 1 and abstract representation 15

Agenda Connect. Communicate. Collaborate • GEANT 2 status and developments • End to end services and the hybrid infrastructure • JRA 3 introduction • Monitoring 16

Problem space Connect. Communicate. Collaborate E 2 ELink A-B Domain B Point A Domain C Point. B Goal: (near) real-time monitoring (link status) of constituent Domain. Links (and links between domains) and whole end-to-end Link A-B. 17

Approach Connect. Communicate. Collaborate E 2 ELink A-B Domain B Point A Domain C perf. SONAR MP or MA Point. B Domain. Link and (partial) ID_Link info perf. SONAR MP or MA perf. SONAR Measurement Point (MP) or Measurement Archive (MA) E 2 ECU operators E 2 Emon correlator “Weathermap” view for users 18

Connect. Communicate. Collaborate Demo 19

Connect. Communicate. Collaborate Thank you 20

JRA 3 Why an Inter-Domain Manager Connect. Communicate. Collaborate • The effort to provision end-to-end Bandwidth on Demand services in the European scenario requires specific developments in inter-domain collaboration • Splitting intra-domain management functionalities from inter -domain ones in separate modules, allows multi-domain R&D to proceed autonomously and focus on this less standardized area • At the same time, it allows to leverage existing inter-domain managers through wrappers/proxies and interfaces, exploiting a modular approach • This effort can provide solid experience for brokering services other than Bandwidth on Demand 21

JRA 3 Domain independence Connect. Communicate. Collaborate • Collaborative and distributed effort through newly defined interfaces which extend the NNI standards • No centralised management • Better resilience • A common naming and addressing schema for a large amount of devices • An abstract network representation to ensure faithful service description • Possibility to hide domain internals • Clear separation of control and data plane also at the physical level when needed 22

JRA 3: IDM multi-domain issues • • Connect. Communicate. Collaborate The IDM faces a number of requirements and corresponding challenges related to its multi-domain scope: domain independence for resource usage policies and technological choices a service and network abstraction schema (language/notation) to describe very different networks, with different policies – a schema to allow a clear specification of the service – a network abstraction which allows inter-domain information exchange independently of the underlying technologies stitching of multi technology domains multi-domain path finding procedure advance reservation monitoring Authentication and Authorization 23