1. Lecture 20 Multimedia Networking (cont) CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger slides are modified from Jim Kurose, Keith Ross

2. 7: Multimedia Networking 7-2 SIP: Session Initiation Protocol [RFC 3261] SIP long-term vision: r all telephone calls, video conference calls take place over Internet r people are identified by names or e-mail addresses, rather than by phone numbers r you can reach callee, m no matter where callee roams, m no matter what IP device callee is currently using

3. 7: Multimedia Networking 7-3 SIP Services r Setting up a call, SIP provides mechanisms m for caller to let callee know she wants to establish a call m so caller, callee can agree on media type, encoding m to end call r determine current IP address of callee: m maps mnemonic identifier to current IP address r call management: m add new media streams during call m change encoding during call m invite others m transfer, hold calls

4. 7: Multimedia Networking 7-4 Setting up a call to known IP address  Alice’s SIP invite message indicates her port number, IP address, encoding she prefers to receive (PCM ulaw)  Bob’s 200 OK message indicates his port number, IP address, preferred encoding (GSM)  SIP messages can be sent over TCP or UDP;  here sent over RTP/UDP.  default SIP port number is 5060.

5. 7: Multimedia Networking 7-5 Setting up a call (more) r codec negotiation: m suppose Bob doesn’t have PCM ulaw encoder m Bob will instead reply with 606 Not Acceptable Reply, listing his encoders Alice can then send new INVITE message, advertising different encoder r rejecting a call m Bob can reject with replies “busy,” “gone,” “payment required,” “forbidden” r media can be sent over RTP or some other protocol

6. 7: Multimedia Networking 7-6 Example of SIP message INVITE sip:bob@domain.com SIP/2.0 Via: SIP/2.0/UDP 167.180.112.24 From: sip:alice@hereway.com To: sip:bob@domain.com Call-ID: a2e3a@pigeon.hereway.com Content-Type: application/sdp Content-Length: 885 c=IN IP4 167.180.112.24 m=audio 38060 RTP/AVP 0 Notes: r HTTP message syntax r sdp = session description protocol r Call-ID is unique for every call.  Here we don’t know Bob’s IP address. Intermediate SIP servers needed.  Alice sends, receives SIP messages using SIP default port 506  Alice specifies in Via: header that SIP client sends, receives SIP messages over UDP

7. 7: Multimedia Networking 7-7 Name translation and user locataion r caller wants to call callee, but only has callee’s name or e-mail address. r need to get IP address of callee’s current host: m user moves around m DHCP protocol m user has different IP devices PC, PDA, car device r result can be based on: m time of day work, home m Caller don’t want boss to call you at home m status of callee calls sent to voicemail when callee is already talking to someone Service provided by SIP servers: r SIP registrar server r SIP proxy server

8. 7: Multimedia Networking 7-8 SIP Registrar REGISTER sip:domain.com SIP/2.0 Via: SIP/2.0/UDP 193.64.210.89 From: sip:bob@domain.com To: sip:bob@domain.com Expires: 3600 r when Bob starts SIP client, client sends SIP REGISTER message to Bob’s registrar server r similar function needed by Instant Messaging Register Message:

9. 7: Multimedia Networking 7-9 SIP Proxy r Alice sends invite message to her proxy server m contains address sip:bob@domain.com r proxy responsible for routing SIP messages to callee m possibly through multiple proxies. r callee sends response back through the same set of proxies. r proxy returns SIP response message to Alice m contains Bob’s IP address r proxy analogous to local DNS server

10. 7: Multimedia Networking 7-10 Example Caller jim@umass.edu with places a call to keith@upenn.edu (1) Jim sends INVITE message to umass SIP proxy. (2) Proxy forwards request to upenn registrar server. (3) upenn server returns redirect response, indicating that it should try keith@eurecom.fr (4) umass proxy sends INVITE to eurecom registrar. (5) eurecom registrar forwards INVITE to 197.87.54.21, which is running keith’s SIP client. (6-8) SIP response sent back (9) media sent directly between clients. Note: also a SIP ack message, which is not shown.

11. 7: Multimedia Networking 7-11 Comparison with H.323 r H.323 is another signaling protocol for real-time, interactive r H.323 is a complete, vertically integrated suite of protocols for multimedia conferencing: m signaling, registration, admission control, transport, codecs r SIP is a single component. Works with RTP, but does not mandate it. m Can be combined with other protocols, services r H.323 comes from the ITU (telephony) r SIP comes from IETF: Borrows much of its concepts from HTTP m SIP has Web flavor, whereas H.323 has telephony flavor. r SIP uses the KISS principle: m Keep it simple stupid

12. 7: Multimedia Networking 7-12 Chapter 7 outline 7.1 multimedia networking applications 7.2 streaming stored audio and video 7.3 making the best out of best effort service 7.4 protocols for real-time interactive applications RTP, RTCP, SIP 7.5 providing multiple classes of service 7.6 providing QoS guarantees

13. 7: Multimedia Networking 7-13 Providing Multiple Classes of Service r thus far: making the best of best effort service m one-size fits all service model r alternative: multiple classes of service m partition traffic into classes m network treats different classes of traffic differently (analogy: VIP service vs regular service) 0111 r granularity: differential service among multiple classes, not among individual connections r history: ToS bits

14. 7: Multimedia Networking 7-14 Multiple classes of service: scenario R1 R2 H1 H2 H3 H4 1.5 Mbps link R1 output interface queue

15. 7: Multimedia Networking 7-15 Scenario 1: mixed FTP and audio r Example: 1Mbps IP phone, FTP share 1.5 Mbps link. m bursts of FTP can congest router, cause audio loss m want to give priority to audio over FTP packet marking needed for router to distinguish between different classes; and new router policy to treat packets accordingly Principle 1 R1 R2

16. 7: Multimedia Networking 7-16 Principles for QOS Guarantees (more) r what if applications misbehave m audio sends higher than declared rate m policing: force source adherence to bandwidth allocations r marking and policing at network edge: m similar to ATM UNI (User Network Interface) provide protection (isolation) for one class from others Principle 2 R1 R2 1.5 Mbps link 1 Mbps phone packet marking and policing

17. 7: Multimedia Networking 7-17 Principles for QOS Guarantees (more) r Allocating fixed (non-sharable) bandwidth to flow: inefficient use of bandwidth if flows doesn’t use its allocation While providing isolation, it is desirable to use resources as efficiently as possible Principle 3 R1 R2 1.5 Mbps link 1 Mbps phone 1 Mbps logical link 0.5 Mbps logical link

18. 7: Multimedia Networking 7-18 Scheduling And Policing Mechanisms r scheduling: choose next packet to send on link r FIFO (first in first out) scheduling: send in order of arrival to queue m real-world example? m discard policy: if packet arrives to full queue: who to discard? Tail drop: drop arriving packet priority: drop/remove on priority basis random: drop/remove randomly

19. 7: Multimedia Networking 7-19 Scheduling Policies: more Priority scheduling: transmit highest priority queued packet r multiple classes, with different priorities m class may depend on marking or other header info, e.g. IP source/dest, port numbers, etc.. m Real world example?

20. 7: Multimedia Networking 7-20 Scheduling Policies: still more round robin scheduling: r multiple classes r cyclically scan class queues, serving one from each class (if available) r real world example?

21. 7: Multimedia Networking 7-21 Scheduling Policies: still more Weighted Fair Queuing: r generalized Round Robin r each class gets weighted amount of service in each cycle r real-world example?

22. 7: Multimedia Networking 7-22 Policing Mechanisms Goal: limit traffic to not exceed declared parameters Three common-used criteria: r (Long term) Average Rate: how many pkts can be sent per unit time (in the long run) m crucial question: what is the interval length: 100 packets per sec or 6000 packets per min have same average! r Peak Rate: e.g., 6000 pkts per min. (ppm) avg.; 1500 ppm peak rate r (Max.) Burst Size: max. number of pkts sent consecutively m with no intervening idle

23. 7: Multimedia Networking 7-23 Policing Mechanisms Token Bucket: limit input to specified Burst Size and Average Rate. r bucket can hold b tokens r tokens generated at rate r token/sec unless bucket full r over interval of length t: number of packets admitted less than or equal to (r t + b).

24. 7: Multimedia Networking 7-24 Policing Mechanisms (more) r token bucket, WFQ combine to provide guaranteed upper bound on delay, m i.e., QoS guarantee! WFQ token rate, r bucket size, b per-flow rate, R D = b/R max arriving traffic

25. 7: Multimedia Networking 7-25 IETF Differentiated Services r want “qualitative” service classes m “behaves like a wire” m relative service distinction: Platinum, Gold, Silver r scalability: simple functions in network core, relatively complex functions at edge routers (or hosts) m signaling, maintaining per-flow router state difficult with large number of flows r don’t define define service classes, m provide functional components to build service classes

26. 7: Multimedia Networking 7-26 Edge router:  per-flow traffic management  marks packets as in-profile and out-profile Core router:  per class traffic management  buffering and scheduling based on marking at edge  preference given to in-profile packets Diffserv Architecture scheduling... r b marking

27. 7: Multimedia Networking 7-27 Edge-router Packet Marking r class-based marking: packets of different classes marked differently r intra-class marking: conforming portion of flow marked differently than non-conforming one r profile: pre-negotiated rate A, bucket size B r packet marking at edge based on per-flow profile Possible usage of marking: User packets Rate A B

28. 7: Multimedia Networking 7-28 Classification and Conditioning r Packet is marked in the Type of Service (TOS) in IPv4, and Traffic Class in IPv6 r 6 bits used for Differentiated Service Code Point (DSCP) and determine PHB that the packet will receive r 2 bits are currently unused

29. 7: Multimedia Networking 7-29 Classification and Conditioning may be desirable to limit traffic injection rate of some class: r user declares traffic profile (e.g., rate, burst size) r traffic metered, shaped if non-conforming

30. 7: Multimedia Networking 7-30 Forwarding (PHB) r PHB result in a different observable (measurable) forwarding performance behavior r PHB does not specify what mechanisms to use to ensure required PHB performance behavior r Examples: m Class A gets x% of outgoing link bandwidth over time intervals of a specified length m Class A packets leave first before packets from class B

31. 7: Multimedia Networking 7-31 Forwarding (PHB) PHBs being developed: r Expedited Forwarding: pkt departure rate of a class equals or exceeds specified rate m logical link with a minimum guaranteed rate r Assured Forwarding: 4 classes of traffic m each guaranteed minimum amount of bandwidth m each with three drop preference partitions

32. 7: Multimedia Networking 7-32 Chapter 7 outline 7.1 multimedia networking applications 7.2 streaming stored audio and video 7.3 making the best out of best effort service 7.4 protocols for real-time interactive applications RTP, RTCP, SIP 7.5 providing multiple classes of service 7.6 providing QoS guarantees

33. 7: Multimedia Networking 7-33 Principles for QOS Guarantees (more) r Basic fact of life: can not support traffic demands beyond link capacity Call Admission: flow declares its needs, network may block call (e.g., busy signal) if it cannot meet needs Principle 4 R1 R2 1.5 Mbps link 1 Mbps phone 1 Mbps phone

34. 7: Multimedia Networking 7-34 QoS guarantee scenario r Resource reservation m call setup, signaling (RSVP) m traffic, QoS declaration m per-element admission control m QoS-sensitive scheduling (e.g., WFQ) request/ reply

35. 7: Multimedia Networking 7-35 IETF Integrated Services r architecture for providing QOS guarantees in IP networks for individual application sessions r resource reservation: routers maintain state info (a la VC) of allocated resources, QoS req’s r admit/deny new call setup requests: Question: can newly arriving flow be admitted with performance guarantees while not violated QoS guarantees made to already admitted flows?

36. 7: Multimedia Networking 7-36 Call Admission Arriving session must : r declare its QOS requirement m R-spec: defines the QOS being requested r characterize traffic it will send into network m T-spec: defines traffic characteristics r signaling protocol: needed to carry R-spec and T- spec to routers (where reservation is required) m RSVP

37. 7: Multimedia Networking 7-37 Intserv QoS: Service models [rfc2211, rfc 2212] Guaranteed service: r worst case traffic arrival: leaky-bucket-policed source r simple (mathematically provable) bound on delay Controlled load service: r "a quality of service closely approximating the QoS that same flow would receive from an unloaded network element." WFQ token rate, r bucket size, b per-flow rate, R D = b/R max arriving traffic

38. 7: Multimedia Networking 7-38 Signaling in the Internet connectionless (stateless) forwarding by IP routers best effort service no network signaling protocols in initial IP design + = r New requirement: reserve resources along end-to-end path (end system, routers) for QoS for multimedia applications r RSVP: Resource Reservation Protocol [RFC 2205] m “ … allow users to communicate requirements to network in robust and efficient way.” i.e., signaling ! r earlier Internet Signaling protocol: ST-II [RFC 1819]

39. 7: Multimedia Networking 7-39 RSVP Design Goals 1. accommodate heterogeneous receivers m different bandwidth along paths 2. accommodate different applications with different resource requirements 3. make multicast a first class service, m with adaptation to multicast group membership 4. leverage existing multicast/unicast routing, m with adaptation to changes in underlying unicast, multicast routes 5. control protocol overhead to grow (at worst) linear in # receivers 6. modular design for heterogeneous underlying technologies

40. 7: Multimedia Networking 7-40 RSVP: does not… r specify how resources are to be reserved r rather: a mechanism for communicating needs r determine routes packets will take r that’s the job of routing protocols r signaling decoupled from routing r interact with forwarding of packets r separation of control (signaling) and data (forwarding) planes

41. 7: Multimedia Networking 7-41 RSVP: overview of operation r senders, receiver join a multicast group m done outside of RSVP m senders need not join group r sender-to-network signaling m path message: make sender presence known to routers m path teardown: delete sender’s path state from routers r receiver-to-network signaling m reservation message: reserve resources from sender(s) to receiver m reservation teardown: remove receiver reservations r network-to-end-system signaling m path error m reservation error

42. 7: Multimedia Networking 7-42 Chapter 7: Summary Principles r classify multimedia applications r identify network services applications need r making the best of best effort service Protocols and Architectures r specific protocols for best-effort r mechanisms for providing QoS r architectures for QoS m multiple classes of service m QoS guarantees, admission control