2. 1 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS How can QoS be guaranteed/managed in a multi-provider IP environment Michael Smirnov GMD FOKUS COST 263

3. 2 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS COST 263: "Quality of Internet Services" IETF: > 100 short-lived WGs in 5 areas COST: WGs within a long-lived Action IETF: lacks inter-group coordination COST: committed to co-ordination IETF:hard to join with new work items COST:easy to join with new work items

4. 3 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS COST 263 MoU: R&D QoS Engineering for the Internet QoS Enhancements for the Internet protocol stack QoS in Multicast QoS in NG protocolsQoS in Applications Charging for Premium IP Services Liaisons

5. 4 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS About Guarantee... Assurance - n, confidence..., belief and trust..., promise... Guarantee - n, promise or undertaking... that certain conditions agreed to in a transaction will be fulfilled A.S.Hornby, Ed., Oxford Dictionary, 1986

6. 5 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS –Business usage: Virtual Enterprise? –Real-time communication over the Internet? –IETF promises: IntServ, DiffServ, MPLS,... –How in the multi-provider environment? –What’s coming next? What are the promises?

7. 6 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS Multi-provider issues NSF Internet: each hop is a provider Commercial Internet: –Peering –ISP Certification –Roaming –Shared trouble ticketing –Charging and accounting collaboration

8. 7 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS Network Access Point Peering Point No congestion here Add BW on demand Peering Rules

9. 8 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS The only QoS guaranteed communication so far was always connection-oriented: - always only one hop; - QoS set-up at root. QoS assurance in a connectionless world has to repeat the QoS set-up step at each hop: IntServ ~ characterisation point DiffServ ~ PHBs mapping Connection oriented vs Connectionless from the QoS assurance viewpoint

10. 9 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS The Big Picture QoS routing ? ISP L3/L2 Classif.Sched. Capacity QoS set-up Policy IntServ DiffServ

11. 10 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS End-to-end QoS request Achieved QoS Needed QoS Src Dst IntServ’s Characterisation Point

12. 11 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS The IntServ characterisation point is important in a multi-provider environment: –IntServ is not only RSVP –RSVP is complex (or too generic?). The DiffServ reflects the backbone´s needs only –the end-to-end QoS is questionable. What is wrong with IntServ and DiffServ?

13. 12 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS DiffServ is simple but has no end-to-end guarantees: need for the top level control; IntServ guarantees end-to-end but is complex and needs admission controls; The combination (IIS+DS) seems to be OK, however it needs QoS routing support, and qosr has no progress IntServ + DiffServ ?

14. 13 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS VAIP Best Effort Internet QOSR IP/FEC Tunnel (Shortcut) VAIP GW QoS Interworking More than 1 provider

15. 14 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS IN and Internet 1 800 345... codepointbehaviour Service DBase switch Dst IP, TOS,... codepoints behaviours router Routing DBase TOS DBase

16. 15 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS IN and Internet Interworking R R R Sw SCP MG SG MC MG Sw SCP SG MC Sw SCP MG

17. 16 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS The AN paradigm: networks programmable by applications : – are networks ready for this? ( see e.g. IPv6 transition plan for an example ); The needed advances in SW development are missing (component software), however... attempts are numerous (...) What is coming next: Active Networks?

18. 17 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS We should go back to a CO world: – ATM is there with the QoS guarantees; –AAL5´s overhead is minimal. Then the qosr is simply a shortcut management? (we do have solutions for IP and IP multicast over ATM with QoS!) IETF: ION, ISSLL - no integration, MPLS is a solution? What is coming next: Shortcuts !

19. 18 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS MPLS is a solution? R R R R MPLS Trunk RSVP signalling

20. 19 Heidelberg, 14 - 15 October 1998 How can QoS be guaranteed/managed in a multi-provider IP environment QUTE’98 Workshop Michael Smirnov, GMD FOKUS “The Internet has met its enemy and its name is QoS “ ( B. Carpenter, J. Crowcroft ) Integrational approach is needed –protocol co-design, –better integration of L3/L2 issues The issue: who pays, what for and how much? Conclusions