1. OSPF Offloading: The HELLO Protocol A First Step Toward Distributed Heterogeneous Offloading Speaker: Mary Bond

2. Introduction: The Challenge Traditional IP router architecture incorporates single centralized control processor Scalability issues are real Large amount of I/O bandwidth required across backplane

3. The Future of Network Forwarding Devices

4. The Protocol Offload Solution: Long Term Goal Distribute functionality by protocol offloading to forwarding plane blades Design a generalized framework for offloading protocols The Approach: –Examine offloading possibilities of many routing protocols –Use collective results to design offloading framework

5. OSPF: A Brief Overview Link state vector algorithm Distribute data by flooding Amount of data passed reduced via area grouping External data advertised, separate from link state data

6. OSPF: A Brief Overview HELLO packets used to acquire neighbors HELLO protocol elects designated router Link state ads (LSAs) reflect adjacencies LSAs flooded reliably Link state database is collection of LSAs from every router in area

7. OSPF Offloading: The HELLO Protocol Two primary OSPF data structures: –Interfaces –Neighbors Interface algorithms: –HELLO –Designated Router Election Neighbor algorithms: –Database Distribution –Link State Updates –Routing Table Calculation

8. Interface and Neighbor Finite State Machines

9. Communication Between GOSPF and OOSPF Synchronizing Data Structure Fields Starting/Stopping HELLO Timers Instigating FSM Transitions Triggering Link State Advertisements Updating Designated Router (or Backup) Instigating sending of HELLO Packets

10. GOSPF and OOSPF Proxies GOSPF and OOSPF communicate via proxies Remote procedure calls are transparent TCP connection

11. The RPC Class Provides general framework for communication between proxies Child classes inherit from RPC class, one for each remote procedure call Child classes correspond to specific functions (called remotely) between GOSPF and OOSPF

12. Offloaded OSPF, IXP Architecture

13. Conclusions Future control plane processing presents a bottleneck issue Protocol offloading is a possible solution This project was a first step toward studying the offloading of control plane routing protocols.

14. Thank you!