1. Middleware and Management Support for Programmable QoS-Network Architectures Miguel Rio (joint work with Hermann De Meer, Wolfgang Emmerich, Cecilia Mascolo, Nicola Pezzi and Luca Zanolin) Department of Computer Science University College London

2. 2 October 2001, Miguel RioIWAN 2001 Outline Motivation Architecture Overview XML based engine A modular Kernel Conclusions Current Work

3. 2 October 2001, Miguel RioIWAN 2001 Motivation Increase network flexibility Allow the fine-grain update of node configurations Allow the management and reconfiguration of multiple and heterogeneous nodes at the same time Be able to change and configure the packet data path at run-time inside each router Easy inclusion of QoS elements Do not affect performance

4. 2 October 2001, Miguel RioIWAN 2001 A two-level system XML based engine manager mod3mod4mod5 mod mod1mod2 XML Load module XML Rem. module XML Connect module XML Add Rule XML Remove Rule XML … Forwarding Engine kernel

5. 2 October 2001, Miguel RioIWAN 2001 Router Management XML Documents Router 1 Router 3 Router n … Router 2

6. 2 October 2001, Miguel RioIWAN 2001 Why XML ? XML allows us to change the syntax of our configurations at run-time XMLs related technologies allow easy update of configurations Easy addressing and manipulation parts of the XML document Several off-the-shelf XML tools

7. 2 October 2001, Miguel RioIWAN 2001 A two-level system XML based engine manager mod3mod4mod5 mod mod1mod2 XML Load module XML Rem. module XML Connect module XML Add Rule XML Remove Rule XML … Forwarding Engine kernel

8. 2 October 2001, Miguel RioIWAN 2001 DiffServ Example: Module insertion and connection <module fromModuleName="classifier" fromGate="0" toModuleName="dropper" toGate="0"/> <module fromModuleName="dropper" fromGate="0" toModuleName="marker" toGate="0"/>

9. 2 October 2001, Miguel RioIWAN 2001 Rule Insertion <rule IPSource="128.16.6.*" TCPSource=*" IPDest="" TCPDest="22" class="1"/> <rule IPSource="128.16.8.*" TCPSource=*" IPDest="" TCPDest="22" />

10. 2 October 2001, Miguel RioIWAN 2001 XML Schema … …

11. 2 October 2001, Miguel RioIWAN 2001 A two-level system XML based engine manager mod3mod4mod5 mod mod1mod2 XML Load module XML Rem. module XML Connect module XML Add Rule XML Remove Rule XML … Forwarding Engine kernel

12. 2 October 2001, Miguel RioIWAN 2001 A modular kernel Manager Mod 2 1 2 3 Mod 1 Kernel User Space

13. 2 October 2001, Miguel RioIWAN 2001 Updating modules using Netlink manager Netlink kernel User Space

14. 2 October 2001, Miguel RioIWAN 2001 Example: Differentiated Services Forwarding engine marker dropper classif. policer scheduler …

15. 2 October 2001, Miguel RioIWAN 2001 Other applications Firewalls Virtual Private Networks Active Bridging NAT IPv6 migration

16. 2 October 2001, Miguel RioIWAN 2001 Implementation XML based engine is implemented in JAVA. Java provides portability and dynamic update of router management code The Kernel modules are implemented in C to prevent significant efficiency losses.

17. 2 October 2001, Miguel RioIWAN 2001 Conclusions XML allows flexibility defining router behaviour. It is portable and it is a well- known markup language Using XML Schema the behaviour grammar can be defined, checked and modified at run- time Our Architecture allows insertion, removal and (re)configuration of modules inside the active router without traffic disruption

18. 2 October 2001, Miguel RioIWAN 2001 Related Work MITs Click, Router Plugins (Washington): Allow the composition of services at run-time. Plan(Upen) and SafetyNet (Sussex): Strongly typed & O-O specification of network behaviour

19. 2 October 2001, Miguel RioIWAN 2001 Current and Future Work Formal description and validation of router configurations Integration with SNMP/MIB framework Extending the model to configure routing protocol elements running in the user level Transactions and Security Performance Evaluation

20. 2 October 2001, Miguel RioIWAN 2001 Questions ? http://pizza.cs.ucl.ac.uk/promile

21. 2 October 2001, Miguel RioIWAN 2001 Preliminary Evaluation