why is optical networking interesting? cees de laat delaat

Why is optical

networking interesting?

Cees de Laatwww.science.uva.nl/~delaat

Why is optical

networking interesting?

EUSURFnetUniversity of Amsterdam

SARANIKHEF

serena

Cees de aatCees de Laatwww.science.uva.nl/~delaatwww.science.uva.nl/~deaat

What is this buzz about optical

networking

• Networks are already optical for ages

• Users won’t see the light

• Almost all current projects are about SONET circuits and Ethernet (old wine in new bags?)

• Are we going back to the telecom world, do NRN’s want to become telco’s

• Does it scale

• Is it all about speed or is it integrated services

Current technology + (re)definition

• Current (to me) available technology consists of SONET/SDH switches

• Changing very soon!

• DWDM+switching coming up

• Starlight uses for the time being VLAN’s on Ethernet switches to connect [exactly] two ports

• So redefine a as:

“a is a pipe where you can inspect packets as they enter and when they exit, but principally not when in transit. In transit one

only deals with the parameters of the pipe: number, color, bandwidth”

VLBI

Know the user

BW requirements

# of users

C

A

B

A -> Lightweight users, browsing, mailing, home use

B -> Business applications, multicast, streaming, VPN’s, mostly LAN

C -> Special scientific applications, computing, data grids, virtual-presence

ADSL GigE LAN

(3 of 12)

F(t)

What the user

BW requirements

Total BW

C

A

B

A -> Need full Internet routing, one to many

B -> Need VPN services on/and full Internet routing, several to several

C -> Need very fat pipes, limited multiple Virtual Organizations, few to few

ADSL GigE LAN

(4 of 12)

So what are the facts

• Costs of fat pipes (fibers) are one/third of equipment to

light them up

– Is what Lambda salesmen tell me

• Costs of optical equipment 10% of switching 10 % of

full routing equipment for same throughput

– 100 Byte packet @ 10 Gb/s -> 80 ns to look up in 100 Mbyte

routing table (light speed from me to you on the back row!)

• Big sciences need fat pipes

• Bottom line: create a hybrid architecture which serves

all users in one consistent cost effective way

(5 of 12)

Scale 2-20-200

(5b of 12)

Services

2Metro

20National/regional

200World

A Switching/routing

Routing ROUTER$

B VPN’s, (G)MPLS

VPN’sRouting

Routing

C# ~ 200/RTT

dark fiberOptical switching

Lambda switching

Sub-lambdas, ethernet-sdh

COST

(5c of 12)

• lambda for high bandwidth

applications– Bypass of production network

– Middleware may request (optical) pipe

• RATIONALE:– Lower the cost of transport per

packet

Application

Middleware

Transport

Application

Middleware

Transport

Router

Router

UvA

Router

Router

3rd party carriers

Router

ams

chi

SURFnet5

UBC Vancouver

Switch

GbE

GbE

GbE

2.5Gb lambda

Lambda

Switch

Lambda

Switch

Lambda

Switch

Lambda

Switch

Switch

Router

High bandwidth app

(6 of 12)

CA*net 4 Architecture

Calgary ReginaWinnipeg

OttawaMontreal

Toronto

Halifax

St. John’s

Fredericton

Charlottetown

ChicagoSeattleNew York

CANARIEGigaPOP

ORAN DWDM

Carrier DWDM

Thunder Bay

CA*net 4 node)

Possible future CA*net 4 node

Quebec

Windsor

Edmonton

Saskatoon

Victoria

Vancouver

Boston

(7 of 12)

R

Architectures - L1 - L3

R

R

R

SWL2 VPN’s

Internet

Internet

Bring plumbing to the users, not just create sinks in the middle of nowhere

(8 of 12)

Distributed L2

lambda

SN5A’DAM

Univ A

SN5CHICAGO

Univ B

Univ X

Univ Y

Layer 2 VPN

(8a of 12)

Transport in the corners

BW*RTT

# FLOWS

For what current Internet was designed

Needs more App & Middleware interaction

C

A

B

Full optical future

?

(9 of 13)

QuickTime™ and aPNG decompressor

are needed to see this picture.

(9a of 13)

Layer - 2 requirements from 3/4

TCP is bursty due to sliding window protocol and slow start algorithm. So pick from menu:•Flow control•Traffic Shaping•RED (Random Early Discard)•Self clocking in TCP•Deep memory

Window = BandWidth * RTT & BW == slow

fast - slowMemory-at-bottleneck = ___________ * slow * RTT fast

WS WSL2

fast->slowL2

slow->fastfast fasthigh RTT

(10 of 14)

Forbidden area, solutions for s when f = 1 Gb/s, M = 0.5 MbyteAND NOT USING FLOWCONTROL

s

rtt

= 158 ms = RTT Amsterdam - Vancouver or Berkeley

0

100

200

300

400

500

600

700

800

900

1000

1 51 101 151 201 251 301 351 401 451 501

Daisy Chain control model of

administrative domainsSelectorSwitch

DistributorSwitch

AAA AAA

Domain X Domain Y

(11 of 14)

Problem Solving Environment

Applications and Supporting Tools

Application Development Support

Common Grid

Services

LocalResources

Gri

d

Info

rmat

ion

S

ervi

ce

Un

ifo

rmR

eso

urc

eA

cces

s

Bro

keri

ng

Glo

bal

Q

ueu

ing

Glo

bal

Eve

nt

Ser

vice

s

Co

-S

ched

uli

ng

Dat

a C

atal

og

uin

g

Un

ifo

rm D

ata

Acc

ess

Co

mm

un

icat

ion

S

ervi

ces

Au

tho

riza

tio

n

Grid Security Infrastructure (authentication, proxy, secure transport)

Au

dit

ing

Fau

lt

Man

ag

emen

t

Mo

nit

ori

ng

Communication

ResourceManager

CPUs

ResourceManagerTertiary Storage

ResourceManagerOn-Line Storage

ResourceManagerScientific

Instruments

ResourceManager Monitors

ResourceManager

Highspeed Data

Transport

ResourceManagernet QoS

(Resource)

layers of increasing abstraction taxonomy

Grid access (proxy authentication, authorization, initiation)

Grid task initiation

Collective Grid

Services

Fabric

the

nec

k

(12 of 14)

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

GRID-Layer

7, 6, 5, 4, 3, 2, 1

ISP’speering

L3

7, 6

, 5, 4

, 3, 2

, 1

7, 6, 5, 4, 3, 2, 1

GR

ID-L

ayer

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

CE

SE

UENE

L3

L2

L1

7, 6, 5, 4, 3, 2, 1

7, 6

, 5, 4

, 3, 2

, 1

7, 6

, 5, 4

, 3, 2

, 1

7, 6

, 5, 4

, 3, 2

, 1

(13 of 14)

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

GRID-Layer

7, 6, 5, 4, 3, 2, 1

ISP’s

L17,

6, 5

, 4, 3

, 2, 1

7, 6, 5, 4, 3, 2, 1

GR

ID-L

ayer

7, 6, 5, 4, 3, 2, 1

7, 6, 5, 4, 3, 2, 1

CE

SE

UE

NE

L1L2

L3/4

7, 6, 5, 4, 3, 2, 1L1-tranport

7, 6

, 5, 4

, 3, 2

, 1

7, 6

, 5, 4

, 3, 2

, 1

7, 6

, 5, 4

, 3, 2

, 1

(13b of 14)

Research needed

• Optical devices

• Internet Architecture

• Network Elements as Grid Resources

• Transport protocols get in other corners

• How dynamic must your optical underware be

• Don’t mix trucks and Ferrari’s

(13c of 14)

Revisiting the truck of tapes

Consider one fiber

•Current technology allows 320 in one of the frequency bands

•Each has a bandwidth of 40 Gbit/s

•Transport: 320 * 40*109 / 8 = 1600 GByte/sec

• Take a 10 metric ton truck

•One tape contains 50 Gbyte, weights 100 gr

•Truck contains ( 10000 / 0.1 ) * 50 Gbyte = 5 PByte

• Truck / fiber = 5 PByte / 1600 GByte/sec = 3125 s ≈ one hour

• For distances further away than a truck drives in one hour (50 km)

minus loading and handling 100000 tapes the fiber wins!!!

(14 of 14)

The END

Thanks to

TERENA: David Williams

SURFnet: Kees Neggers

UIC&iCAIR: Tom DeFanti, Joel Mambretti

CANARIE: Bill St. ArnaudSupport from:

SURFnet

EU-IST project DATATAG

(15 of 14)

26/11/1910 -- 11/9/2002