1. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH Flow Aware Networking Router model lead by prof. dr hab. inż. Andrzej Jajszczyk

2. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 2/232/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

3. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 3/233/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

4. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 4/234/23Jakub Palider Current network quality requirements  Nowadays networks are expected to support a variety of services beyond the best-effort service available today  New applications already rely on the network ability to guarantee such services High speed packet- switched networks Applications requiring bandwidth P2P Networks, Large Databases, Large multimedia files, XBOX Live Applications requiring low latency VoIP, tele- conferencing, UMA, on-line gaming, distance learning

5. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 5/235/23Jakub Palider What is congestion?  Simple definition: congestion occurs when traffic coming into one link exceeds its capacity e.g. motorway  Main reason: lack of bandwidth –Demand bigger than capacity –Suddenly changing demands –Network failures –Changes in routing

6. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 6/236/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

7. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 7/237/23Jakub Palider QoS In streaming traffic type following guarantee an end- user proper:  Packet delay  Mean bit rate  Stream bit rate  Packet loss  Jitter

8. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 8/238/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

9. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 9/239/23Jakub Palider What are the current QoS solutions? Already Implemented:  Integrated Services – IntServ, the first model defining whole concept of QoS  Differentiated Services – DiffServ – later conception, opposite (in majority) to IntServ New Idea: Flow Aware Networking

10. © 2007 Katedra Telekomunikacji AGH 10/23Jakub Palider Traffic conditioning mechanisms

11. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 11/23Jakub Palider IntServ Memory load  High  Low

12. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 12/23Jakub Palider DiffServ Memory load  High  Low

13. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 13/23Jakub Palider How does congestion control is implemented in DiffServ?  Network traffic entering a DiffServ domain is subjected to classification and conditioning  AC realized only in edge routers, controlled by Bandwidth Broker  PHB define packet forwarding properties inside domain QoS Mechanisms Packet level classifier traffic conditioners scheduler Admission level AC (admission control)

14. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 14/23Jakub Palider Main differences between IntServ and DiffServ Bilateral agreementsMultilateral agreementsInter domain deployment Scalable and robustInformation held in each network node – not scalable Scalability Cannot provide low delay and high bandwith guarantee simultaneously Per flow - bandwidth and delay guarantee Quality guarantees Similar to IP networksSimilar to network switching (e.g. phone calls) Network management Based on class usageBased on flow characteristics and QoS requirement Network accounting Limited by number of classes of service Limited by number of flowsClassification of traffic Per hopEnd to endCoordination for service differentation DiffServIntServParameter

15. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 15/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

16. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 16/23Jakub Palider Features of FAN  No reservation  Classification based on flows  2 flow classes - stream (audio, video, real-time) and elastic (digital documents)  Idea of cross-protect router – accurate relation between admission control and scheduling  “Good enough” performance  Cost effectiveness and accountability $$$

17. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 17/23Jakub Palider What DiffServ congestion control ideas have in common with FAN?  The only common mechanisms are admission control and scheduling, but the admission control is realized in different way  Scheduling algorithms may be implemented in FAN  There are many elementary conceptions common to both architectures – but these are mostly basics of QoS idea

18. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 18/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

19. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 19/23Jakub Palider Measurement Based Admission Control (MBAC)

20. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 20/23Jakub Palider Cross-protection in FAN router Incoming packets Outgoing packets

21. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 21/23Jakub Palider Outline  Transmission requirements  QoS  Existing architectures (IntServ, DiffServ)  FAN mechanisms  Cross-protection: MBAC  Conclusion

22. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 22/23Jakub Palider FAN – pros and cons… AdvantagesDisadvantages  Good scalability  Ease of admission control in each network node (MBAC)  Only small amounts of data stored in network node memory  No strict guarantees of network performance  Not implemented yet

23. Flow Aware Networking © 2007 Katedra Telekomunikacji AGH 23/23Jakub Palider Thank you for attention! to be continued…