To be smart or not to be?

19
To be smart or not to be? Siva Subramanian Polaris R&D Lab, RTP Tal Lavian OPENET Lab, Santa Clara

description

State of the network Plenty of bandwidth Optical core Increasing demand for services Gateways Network Service nodes Content Switches Network Caches Evolving network

Transcript of To be smart or not to be?

Page 1: To be smart or not to be?

To be smart or not to be?Siva Subramanian Polaris R&D Lab, RTP

Tal Lavian OPENET Lab, Santa Clara

Page 2: To be smart or not to be?

State of the network

• Plenty of bandwidth–Optical core

• Increasing demand for services–Gateways–Network Service nodes–Content Switches–Network Caches

• Evolving network

Page 3: To be smart or not to be?

Evolution of the networkVirus

Scanning

Bridging

Routing

QoS

NetworkMonitoring

Firewall

VPN

IntrusionDetection

LoadBalancing

Instructions per Packet

Co

mp

lexi

ty

Core EdgeEdge

C C

Core EdgeEdge

Page 4: To be smart or not to be?

Current Mode of Operation

• Application specific solutions• Hardware/Software design and

deployment cycles takes years• Ad-hoc solutions create complex

networks• Multiple network management

solutions

Page 5: To be smart or not to be?

Answer – Part I

• Flexibility

• Programmability (open interfaces)

Page 6: To be smart or not to be?

Processing Requirements

Bridging

Routing

QoS

NetworkMonitoring

Firewall

VPNIntrusionDetection

VirusScanning

LoadBalancing

100 2000+Instructions per Packet

Co

mp

lexi

ty

Page 7: To be smart or not to be?

Need for Power

• Computational Complexity

• 32-bit Processor @ 500 MIPS

• How much can you do with it?

• Need for high performance computing

technology deeper in the network

100BaseT

OC48

Time/Word # Insts

320ns 16013ns 7

Page 8: To be smart or not to be?

Answer – Part II

• High Performance Computing

Technologies –Configurable Computing

–Parallel Processing

Page 9: To be smart or not to be?

Configurable Computing

• Configurable Computing: Programmable logic ( FPGA ) coupled to Processor ( P )

• Customized for each application

ApplicationP

ASIC

PTasks

FPGAP

CC

Page 10: To be smart or not to be?

How does CC work?

• Customised hardware operations

• Concurrent operations

float D, I, K, R;int A = 100; . . . while ( A != 0 ) { temp = I * K; D = R + temp; A - - ; }

I

K +*R

D

FPGA

Page 11: To be smart or not to be?

The power of CC

• DCT implementation–Xilinx FPGA 180 times faster than 32-

bit processor @ 266MHz

• Vector computations–50MHz FPGA roughly 10 times faster

than 300MHz Pentium CPU

Page 12: To be smart or not to be?

Evolution of routers – Phase I

Centralized Centralized CPU-based RouterCPU-based Router

Control + ForwardingControl + Forwardingfunctions combinedfunctions combined

CPU

Routing Software

Slow

Forwarding ProcessorForwarding Processor based Routerbased Router

Control separatedControl separatedfrom Forwardingfrom Forwarding

CPU

Control Plane

Forwarding Processor

Wire-Speed

Forwarding Processor

Page 13: To be smart or not to be?

Forward Plane

Control Plane

Traffic Packets

Towards Open NetworkingTowards Open Networking

Switching Fabric

CPU System

ForwardingProcessor

Forwarding

Rules ForwardingProcessor

Forwarding

Rules ForwardingProcessor

Forwarding

Rules

. . .

Java Runtime Support

Java-based Network Services

Forward API

Page 14: To be smart or not to be?

Node Architecture

Control Plane

Forward Plane

Compute Plane

Forward APICompute API

Network ServicesCompute Services

Page 15: To be smart or not to be?

Evolution of Routers – Phase II

• Control, Compute and Forward planes• Forward-only flows are not seen by

Compute plane• Control plane can modify behavior of

Compute and Forward planes

ForwardCo

ntr

ol

CPU

ASICASICASIC

Compute

NPUCCCPU

Page 16: To be smart or not to be?

Open Networking

• Abstract Compute & Forward Plane interfaces

• Technology reuse over a range of NORTEL platforms

Control Plane

Forward Plane

Compute Plane

ForwardAPI

ComputeAPI

Network ServicesCompute Services

Page 17: To be smart or not to be?

Work in progress…

• NORTEL R&D activities–POLARIS lab–OPENET lab

• Research Target–“Smart” node architectures–Open architectures–High Performance Computing

technologies

Page 18: To be smart or not to be?

Summary

• Future network node architecture– Open networking– Programmable networking– High performance computing

• Benefits to NORTEL– Rapid service deployment– Third-party value-added services– Increased market penetration

Page 19: To be smart or not to be?

To learn more …

• http://www.openetlab.org/

• http://www.ieee-pin.org/

• http://comet.columbia.edu/openarch

• http://comet.columbia.edu/opensig

• http://www.cpixforum.org/