1 / 31

DiffServ QoS in internet

DiffServ QoS in internet. Elon Rot , Itay Poleg Presentation for ATM Networks course (EE-046992). Why do we need QoS ?. IP revolution - from “IP over everything” to “everything over IP” Current Internet guarantee: Best Effort only . Some applications require more: Guarantee delay, jitter

hadar
Download Presentation

DiffServ QoS in internet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DiffServQoS in internet Elon Rot , Itay Poleg Presentation for ATM Networks course (EE-046992) DiffServ: 26/06/05

  2. Why do we need QoS ? • IP revolution - from “IP over everything” to “everything over IP” • Current Internet guarantee: Best Effort only. • Some applications require more: • Guarantee delay, jitter • Guarantee bandwidth • Guarantee loss rate (VoIP, Conference-Calls, VPN, VOD…) • Although QoS is available in lower layers (ATM, FR, Ethernet) we need a media independent IP QoS DiffServ: 26/06/05

  3. Little History • An 8 bit field in the IP-header • Seems like a good idea for future use. • Lots of initial research in the late 80s and early 90s. • Often takes a telecommunications view of the network. • ATM QoS and Integrated services were developed based on these results (1995). • Focus on per-flow, hard QoS. • Effort was driven by perceived application needs. • In the last years (from 1998), the focus has shifted towards Differentiated services. • Focus is on QoS for flow aggregates, e.g., all the flows belonging to one customer. • From 2000 , you can buy a router that support DiffServ (Cisco) DiffServ: 26/06/05

  4. What is needed to support QoS • Between the network and its clients - Traffic contract • Traffic specification/desired QoS/supported QoS • At network edge: • Signaling and admission control • Packet classification/marking • Traffic shaping • Traffic policing DiffServ: 26/06/05

  5. What is needed to support QoS • At routers: • Classification and scheduling • Smart Routing • Buffer management. • Traffic monitoring • Traffic reshaping DiffServ: 26/06/05

  6. Different QoS approaches • Per flow Vs. aggregate • More groups leads to: more flexibility, more admission, more routers resources • Statistical Vs. Deterministic guarantee • Sometimes statistical are not enough • Deterministic more complex, less utilization • End-to-End Vs. Per-Hope-Behavior • User see E2E • PHB is simpler to implement DiffServ: 26/06/05

  7. IntServ • Per-flow QoS guarantees • Reservation of resources using RSVP • Two service models: • controlled-load service: performance is as good as unloaded network • guaranteed service: firm bound of throughput and delay DiffServ: 26/06/05

  8. IntServ drawbacks • Scalability • RSVP support along the path • Maintaining “soft” reservations • Complexity • Support for each flow • Need to administrate allocations DiffServ: 26/06/05

  9. What is DiffServ? • Aggregate connections flows to different classes • Different demand can be guaranteed to each class • Guarantees implementations are per hop behavior • Each flow gets required services statistically DiffServ: 26/06/05

  10. DiffServ architecture Edge Routers: Usually work at lower rate Therefore can implement more functionality like marking & shaping traffic Core Routers: Usually work at high rate So we want packet handle to be fast and simple (using the classifications) Per-class service

  11. DiffServ architecture • Edge routers • Each flow is handled separately, and each packet is marked according to the SLA • Core routers • Deals with classes (rather then flow) so can be more simple. • Each router still need to manage buffering and scheduling DiffServ: 26/06/05

  12. Traffic Conditioner Block (TCB) Classification: selects a packet in a traffic stream based on the content of some portion of the packet header DiffServ: 26/06/05

  13. Traffic Conditioner Block (TCB) Metering: checks whether the traffic falls within the negotiated profile. DiffServ: 26/06/05

  14. Traffic Conditioner Block (TCB) Marking: marks packet to a particular DS behavior aggregate DiffServ: 26/06/05

  15. Traffic Conditioner Block (TCB) Shaper/Droper: delays if necessary and then forwards or discards the packets . DiffServ: 26/06/05

  16. bit # 0 7 8 15 16 23 24 31 header ToS version total length (in bytes) length D M Identification 0 Fragment offset F F time-to-live (TTL) protocol header checksum source IP address destination IP address options (0 to 40 bytes) (Not used) 4 bytes Classification • How to mark?6 bit it the IP header. • Remainder – IP header • Type Of Service field DiffServ: 26/06/05

  17. ToS field • IP-v4 1 3 5 7 0 2 4 6 0 Precedence Type of Service Priority One hot field for : Delay,cost,throughput, reliability Must be zero • DS-Field 1 3 5 7 0 2 4 6 Class Selector Codepoints Differentiated Services Codepoint (DSCP) Currently Unused DiffServ: 26/06/05

  18. PHB • Externally observable forwarding treatments at a single node • PHB can be described in relative or absolute terms • PHBs are typically implemented by means of buffer management and packet scheduling • All packets with the same DSCP are treated the same, Four types of classes available: • Default • Class-Selector • Expedited Forwarding (EF) • Assured Forwarding (AF) DiffServ: 26/06/05

  19. PHB types • Default PHB: • Traditional best effort treatment. • Must be implemented • Used for unsupported DSCP • Class-Selector PHB • Backward compatibility • Eight possible combinations (including default) The DSCP (6 bit) pattern is: 000000 The DSCP (6 bit) pattern is: xxx000 DiffServ: 26/06/05

  20. PHB types The DSCP (6 bit) pattern is: 101110 • Expedited Forwarding PHB • Providing low loss, low latency, low jitter, assured bandwidth, end-to-end service through DS domains • Implies isolation: guarantee for the EF traffic should not be influenced by the other traffic classes • Non-conformant traffic is dropped or shaped. • Possible service: providing a virtual wire DiffServ: 26/06/05

  21. PHB types • Assured Forwarding (AF): • A method by which Behavior Aggregates can be given different forwarding assurances. • The intent is that it will be used to implement services that differ relative to each other (e.g., gold, silver,…). • AF defines 4 classes with some bandwidth and buffers allocated to them. • Within each class, there are three drop priorities, which affect which packets will get dropped first if there is congestion. • Non-conformant traffic is remarked. DiffServ: 26/06/05

  22. AF table The DSCP (6 bit) pattern is: xyzab0 xyz is the class: 001-class1 ; 010-class2 ; 011-class3 ; 100-class4ab is the drop precedence: 01-low ; 10-medium ; 11-high DiffServ: 26/06/05

  23. Service • A service describes the overall treatment of a customer’s traffic within a DS domain. • Customers see services, not PHBs. • To support a service, many components must work together: • Mapping of service to PHBs, traffic conditioning, network provisioning, PHB-based forwarding. • Services in the DiffServ architecture is defined in the form of Service Level Agreement (SLA). DiffServ: 26/06/05

  24. Putting it all together DiffServ: 26/06/05

  25. Conclusion • Diffserv provides: • Internet Class Of Service: several ToS guaranteed in each DS domain. • Using PHB to achieve the requirements. • Provisioning of network resources according to SLAs DiffServ: 26/06/05

  26. Advantage • Scalability • No dynamic change of stateSaves communication between routers • Can be deployed for specific domain independently • Simple • Relatively low number of statesUsing a stateless approach that minimize the need of nodes to remember anything about flows • Divide load on routers, edge vs. coreedge routers – a few strong and expensive routerscore routers – a lot simple and chip • No signaling • Easily adjustable to SLAs DiffServ: 26/06/05

  27. Disadvantages • Not real end-to-end QoS: • Only PHB – which are not easily map to E2E • Limited number of classes – can’t isolated specific flow. • Inside aggregate each flow get the same (only statistic guarantees) • Routing independent mechanism • Admission control: • Fairly static • Manually or with another mechanism DiffServ: 26/06/05

  28. Diffserv-aware-MPLS • DiffServ enable scalable network design with multiple CoS. • MPLS enable path protection and restoration (create an end-to-end specific path) • Combine those two protocols give us the ability to give strict E2E QoS guarantees while optimizing the use of network resource DiffServ: 26/06/05

  29. Core router (LSR) Support Diffserv and MPLS Ingress node (TCB) With both Diffserv & MPLS support LSP 1 (AF1) LSP 2 (AF3) Incoming Traffic LSP 3 (EF) LSP 4 (default) Diffserv-aware-MPLS DiffServ: 26/06/05

  30. References • Internet Architecture and Protocols EE-046000http://www.ee.technion.ac.il/courses/046000/ • Cisco www.cisco.com/warp/public/cc/pd/iosw/ioft/iofwft/prodlit/difse_wp.htm • QoS -by: ANJALI KULKARNI YI-AN CHENwww.cse.buffalo.edu/~qiao/cse620/present_2000/presentation.ppt • IEFT RFCs 2474, 2475, 2598, 3270 www.ietf.org/rfc.html • MPLS DiffServ-aware Traffic Engineeringhttp://www.juniper.net/solutions/literature/white_papers/200048.pdf DiffServ: 26/06/05

  31. DiffServQoS in internet Elon Rot , Itay Poleg Presentation for ATM Networks course (EE-046992) DiffServ: 26/06/05

More Related