Implementation Considerations in an On-Demand Switched Lightpath Network Adapting the Network to the Application Rob Keates Optical Architecture and PLM

NORTEL 2 What is SURFnet? >Provides the Dutch National Research Network >150 connected organizations; 800,000 users >Production and research foci Key point is that I have never written foci on a slide before >Similar in scope to US RON >Collaborative partner for ‘practical research’

NORTEL 3 BW requirements #users#users C A B ADSL GigE A.Lightweight users, browsing, mailing, home use Need full Internet routing, one to many B.Business apps, multicast, streaming, VPN’s, mostly LAN Need VPN services and full Internet routing, several to several + uplink C.Special scientific applications, computing, data grids, virtual-presence Need very fat pipes, limited multiple Virtual Organizations, few to few Σ A ≈ 20 Gb/s Σ B ≈ 40 Gb/s  Σ C >> 100 Gb/s Source: C.T. de Laat, University of Amsterdam Traffic Characterization

NORTEL 4 Dynamic Resource Allocation What if we fundamentally changed net eng’g >Change the paradigm of static ‘hard-wired’ networks >An application drives shares of network resources Resources = {bandwidth, security, acceleration, …} Within policy-allowed envelopes, end-to-end No more point-and-click interfaces, no operators’ involved, etc. >Service-enable the network for greater control of such resources Ex: JIT, TOD-schedulable control of bandwidth Create alternatives to peak-provisioning across LAN/MAN/WAN With a continuum of satisfaction vs. utilization fruition points >Tame and exploit network diversity Heterogeneous and independently managed network clouds, e2e Ex: Integrated Packet-Optical to best match traffic patterns >Network as a 1 st class resource in Grid-like constructs Joins CPU, DATA resources Adapt the network to the application, not the application to the network

NORTEL 5 Customer A network Customer A network Customer B network Customer B network High-cap user Initial Deployment Model Routed IP Network Layer 2/1/0 network (Ethernet over ’s) UNI DRAC Control Plane Initial deployment creates an on-demand (or scheduled) GbE service driven by customer or application input Packet layer bypass for high bandwidth p2p apps over “virtual ’s” Service activation initiated by user or app (subject to policy) GbE services activated over v/c STS paths on a least cost route Scheduled or on- demand

NORTEL 6 Interacting with the service - management >Function 1: Assign nodes, ports and backbone bandwidth to DRAC DRAC only gets access to selected parts of the network (I-NNI versus NMS) Clear separation from static production services >Function 2: Access management Creation of groups, assigning group managers Policy (allocating ports to groups, resource access limitations) End users are added to groups by group managers >Function 3: Connection control Schedule, query, edit, cancel connection >Function 4: Monitoring State of DRAC-controlled network Looks at DRAC service only => filtering of “state” not a replacement for the network management system Planning view Usage per link (internal => network dimensioning) Usage per port, connections Accounting Logs of usage

NORTEL 7 Interacting with the service - user >Querying feasibility - before a service is established Usable UNI and E-NNI ports List depends on groups user belongs to => AA(A) Ports and bandwidth available at time of service? At what cost parameters can I get the service? Block visibility of the details within the network cloud >Scheduling a service Query => availability of specific connection “cost” and other parameters returned Reserve => confirmation + reference, and guarantee of parameters Establish=> at requested time service is established automatically >Verifying a reservation Status request of a reservation (existing, parameters) Status request of an existing connection (up, down) notification (start, end, failure)

NORTEL 8 End-user GUI snapshot

NORTEL 9 Lessons Learned >Scheduling is important… >And drives a hierarchical architecture >Layered software architecture required to future-proof design >Share the network, but strong isolation required Allocation and segmentation of network resources >User access and policy management Secure, simple user access Flexible resource and group management Delegate authority where it belongs Open enough to stimulate initial uptake >Alarms (‘NOC noise’) >Flexibility in required granularity The heavy lifting involves making this stuff deployable into real networks

NORTEL 10 What’s Next? >Extension to other networking technologies Photonic Packet (beginning with PBT/PBB) wireless >Inter-domain How and what do we standardize? >Workflow integration Sensors Compute resource manager interworking Concept of laxity

NORTEL 11 Summary >Ever-increasing, need to provide network flexibility in addressing diverse applications >Clear role for a mediation device that sits between the network and applications >Nortel is investing in a commercial-grade solution Targeted at production networks Architected to evolve to more sophisticated compute/network models via computing partnerships >SURFnet work has proven invaluable in solving the practical deployment issues around user access, security, billing, alarming etc. >Work is being initiated on inter-domain definition >The cool stuff awaits in workflow engagement and cognitive networks