call-center agents using a web-based application on a remote server- it is important to prioritize HTTP. We'll use this as an example and assume that all traffic to or from the server (10.10.100.100) on port 80 should be prioritized. The list should now look like this: Voice RTP Voice control Telnet/SSH HTTP to/from 10.10.100.100 ---to be determined--- Everything else (default-best effort) Notice I've kept Telnet/SSH above the call-center traffic. Remember, we're keeping that as our ace in the hole for when there's an outage. Our next consideration is email, which can eat up a lot of bandwidth on a network. In many older (and still used) Microsoft Exchange environments, personal email folders are stored in files called postoffice (.pst) files. You may have users on one end of a link with their .pst files stored on a file server in a remote office. I've run into problems where the execs had 1 GB .pst files that were opened across the WAN. What's more, all the users who were configured this way came in around the same time and requested their huge .pst files at the same time every morning, bringing the network to a crawl. Still, the executives insisted that email should be prioritized, SO in the spirit of giving exec- utives what they want, we'll put it just above the default queue in our scheme: Voice RTP Voice control Telnet/SSH HTTP to/from 10.10.100.100 ---to be determined--- Email (SMTP, POP, IMAP, Exchange) Everything else (default-best effort) In my experience, email problems can usually be attributed to poorly enforced (or even nonexistent) acceptable use policies. For example, one user sending an email message with a 20 MB attachment to everyone in the company can have a significant impact on the network. LLQ Scenario Removing the placeholder, we now have the following final list of protocols, in de- scending order of priority: Voice RTP Voice control Telnet/SSH HTTP to/from 10.10.100.100 Email (SMTP, POP, IMAP, Exchange) Everything else (default-best effort) This list is a good representation of some real