Interdomain and end-to- end QoS issues Henning Schulzrinne Columbia University NSF QoS workshop – April 2002

Issues What's hard to scale (and what's not) diversity is good AAA needs a tow truck business models don't work

What's hard to scale (and not) Signaling does not have be hard: one message, on a reliable peering channel or IP router alert option NSIS effort in the IETF? YESSIR: RTCP-based signaling 700 MHz Celeron processor 10,000 flow setups/second  300,000 softstate flows If scaling matters, sink-tree based reservation (BGRP)

Diversity is good Unlike routing, no need for single signaling protocol: multicast is much harder dumb end devices edge "pop-up"  only show up in edge nodes

AAA Signaling can easily be done in ASIC (no harder than IP), but need cryptographic verification of request need interface to Authentication, Authorization, Accounting (AAA) cross-domain authentication  hard, but 3G networks will do it anyway easier if both sides ask their own access router see also: iPass for dial-up, OSP (open settlement protocol)

AAA example AR1AR2 Internet source destination signs request reserves for both directions Cell phone model: both sides pay

Reservation scaling Example: every long-distance call in the US uses VoIP with per-flow resource reservation 2000: billion 10 minutes each  1,800 calls/second single mySQL server can sustain 500— 2,000 queries+updates/second

Business models don't work Most of the time, "tin" service is no worse than "platinum" service can't impress others with platinum AmEx card no frequent flyer bonuses  everybody switches only when the network is in bad shape