1. CSE 30264 Computer Networks Prof. Aaron Striegel Department of Computer Science & Engineering University of Notre Dame Lecture 20 – March 25, 2010

2. Today’s Lecture Project 3 –In-Class Exercise Network Issues –Congestion Avoidance –Quality of Service Spring 2010CSE 302642 Physical Data Network Transport Application

3. Project 3 Ninja C / C++ –Pointers / etc. Discussion / in-class exercise Spring 2010CSE 302643

4. Spring 2009CSE302644 Congestion Control Outline Congestion Avoidance RED TCP Vegas

5. Spring 2009CSE302645 Random Early Detection (RED) Notification is implicit –just drop the packet (TCP will timeout) –could make explicit by marking the packet Early random drop –rather than wait for queue to become full, drop each arriving packet with some drop probability whenever the queue length exceeds some drop level

6. Spring 2009CSE302646 RED Details (cont) Computing probability P TempP = MaxP * (AvgLen - MinThreshold)/ (MaxThreshold - MinThreshold) P = TempP/(1 - count * TempP) Drop Probability Curve

7. Spring 2009CSE302647 Tuning RED Probability of dropping a particular flow’s packet(s) is roughly proportional to the share of the bandwidth that flow is currently getting MaxP is typically set to 0.02, meaning that when the average queue size is halfway between the two thresholds, the gateway drops roughly one out of 50 packets. If traffic is bursty, then MinThreshold should be sufficiently large to allow link utilization to be maintained at an acceptably high level Difference between two thresholds should be larger than the typical increase in the calculated average queue length in one RTT; setting MaxThreshold to twice MinThreshold is reasonable for traffic on today’s Internet

8. Spring 2009CSE302648 TCP Vegas Idea: source watches for some sign that router’s queue is building up and congestion will happen too; e.g., –RTT grows –sending rate flattens

9. Spring 2009CSE302649 Algorithm Let BaseRTT be the minimum of all measured RTTs (commonly the RTT of the first packet) If not overflowing the connection, then ExpectedRate = CongestionWindow/BaseRTT Source calculates sending rate ( ActualRate ) once per RTT Source compares ActualRate with ExpectedRate Diff = ExpectedRate - ActualRate if Diff <  increase CongestionWindow linearly else if Diff >  decrease CongestionWindow linearly else leave CongestionWindow unchanged

10. Spring 2009CSE3026410 Algorithm (cont) Parameters  = 1 packet  = 3 packets

11. Derivation How long will something take via TCP? Derive –ROM – Rough Order of Magnitude Estimates –See in-class notes Spring 2010CSE 3026411

12. Spring 2009CSE3026412 Quality of Service Outline Realtime Applications Integrated Services Differentiated Services

13. Spring 2009CSE3026413 Realtime Applications Require “deliver on time” assurances –must come from inside the network Example application (audio) –sample voice once every 125us –each sample has a playback time –packets experience variable delay in network –add constant factor to playback time: playback point Microphone Speaker Sampler, A D converter Buffer, D A

14. Spring 2009CSE3026414 Playback Buffer Sequence number Packet generation Network delay Buffer Playback Time Packet arrival

15. Spring 2009CSE3026415 Example Distribution of Delays

16. Spring 2009CSE3026416 Taxonomy

17. Spring 2009CSE3026417 Integrated Services Service Classes –guaranteed –controlled-load Mechanisms –resource reservation (signalling) –admission control –policing –packet scheduling

18. Spring 2009CSE3026418 Flowspec Rspec: describes service requested from network –controlled-load: none –guaranteed: delay target Tspec: describes flow’s traffic characteristics –average bandwidth + burstiness: token bucket filter –token rate r –bucket depth B –must have a token to send a byte –must have n tokens to send n bytes –start with no tokens –accumulate tokens at rate of r per second –can accumulate no more than B tokens

19. Spring 2009CSE3026419 Per-Router Mechanisms Admission Control –decide if a new flow can be supported –answer depends on service class –not the same as policing Packet Processing –classification: associate each packet with the appropriate reservation –scheduling: manage queues so each packet receives the requested service

20. Spring 2009CSE3026420 Reservation Protocol Called signalling in ATM Proposed Internet standard: RSVP Consistent with robustness of today’s connectionless model Uses soft state (refresh periodically) Designed to support multicast Receiver-oriented Two messages: PATH and RESV Source transmits PATH messages every 30 seconds Destination responds with RESV message Merge requirements in case of multicast Can specify number of speakers

21. Spring 2009CSE3026421 RSVP Example Sender 1 Sender 2 PATH RESV (merged) RESV Receiver B Receiver A R R R R R

22. Spring 2009CSE3026422 RSVP Associate packet with reservation (classifying): –source address, destination address, protocol number, source port, destination port Manage packets in queues (scheduling).

23. Spring 2009CSE3026423 RSVP versus ATM (Q.2931) RSVP –receiver generates reservation –soft state (refresh/timeout) –separate from route establishment –QoS can change dynamically –receiver heterogeneity ATM –sender generates connection request –hard state (explicit delete) –concurrent with route establishment –QoS is static for life of connection –uniform QoS to all receivers

24. Spring 2009CSE3026424 Differentiated Services Problem with IntServ: scalability Idea: segregate packets into a small number of classes –e.g., premium vs best-effort Packets marked according to class at edge of network Core routers implement some per-hop-behavior (PHB) Example: Expedited Forwarding (EF) –rate-limit EF packets at the edges –PHB implemented with class-based priority queues or WFQ

25. Spring 2009CSE3026425 DiffServ (cont) Assured Forwarding (AF) –customers sign service agreements with ISPs –edge routers mark packets as being “in” or “out” of profile –core routers run RIO: RED with in/out

26. Moment of Zen Spring 2010CSE 3026426