In the spirit of true "net neutrality", I have a policy-map on our border router that strips almost all QoS bits regardless of source. Netflix like to send all their stuff with the AF41 DSCP bit set, for example, and that one gets terminated with extreme prejudice. I do try to at least consider the VoIP stuff that is supposed to be set with DCSP EF and will reapply that bit as necessary, but everything else gets categorized as DCSP 00, meaning it's all the same. And if it gets dropped, it gets dropped.
-- Ron Marosko, Jr. . . . . . . . . . . . . . . . . . . . . . . . . . . CCIE No. 4526 (R/S), NN5DX Senior Network Engineer DirectBytes, LLC. 1108 West Dickinson Blvd, Suite A Fort Stockton, TX 79735 USA o: +1 432 336 5600 x115 c: +1 432 290 6344 e: [email protected] pgp pubkey: 0x58AB8B5C "To know me is to fly with me." -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 7:45 PM To: [email protected] Subject: Re: [AFMUG] Limelight Networks and TCP congestion control What about lowering the priority of stuff coming from LLNW? bp <part15sbs{at}gmail{dot}com> On 7/8/2015 5:15 PM, George Skorup wrote: > Is this only from LLNW? I swear I've seen it from other CDNs as well. > I don't see any way around this other than throwing bandwidth at it. > And as you mention, this means upstream bandwidth and backhaul links > between towers. > > On 7/8/2015 5:50 PM, Ken Hohhof wrote: >> This has been discussed in previous threads, but I just got off a >> call with a customer where I was able to identify what content was >> being distributed via LLNW and causing problems. Customer had bought >> a new Xbox and it was downloading game updates. He was complaining >> that the game update seemed stuck getting to 100%, plus Internet on >> his other devices was painfully slow. >> >> LLNW seems to aim for 50% packet loss. I always seem to see almost >> exactly 2X the customer's rate limit hitting our border router. Of >> course this causes all traffic to that customer to experience random >> 50% packet loss, which few applications can tolerate. It is also >> consuming our upstream and backhaul bandwidth beyond what the >> customer has subscribed to, since we do rate limiting at the tower >> router. >> >> Other than getting a Procera box and setting up some kind of rule to >> catch this at the border (plus maybe a penalty for LLNW being such >> dicks), I don't know what to do about this, but it pisses me off. >> >
