This is how I view it as well...only provide QoS to the MPLS VPN since
all the traffic stays on your network. I think what the Sales &
Marketing folk are seeing this as, "well our dedicated internet
customers pay more than the burst low speed customers so we should be
able to guarantee their traffic in times of congestion." It's always
about the $$$.
Jose
William Byrd wrote:
If it helps we only offer QoS to customers with MPLS VPN. Our QoS
product is very similar to what you're talking about. (Gold, Silver,
and Bronze) It doesn't make sense to us to prioritize Internet traffic
as it is all BE once it leaves our network. When we originally turned
all of this up the reasoning to marketing folks was that speed vs.
Bandwidth was usually confusing enough to customers and trying to
explain why end to end QoS across the Internet won't work would be
hell for our support teams.
Basically the way we broke down our QoS was:
Bronze - best effort
Silver - premium data for customers
Gold - customer voip / video
I guess you could call our gold queue the real time queue.
--
Will Collier-Byrd
On Nov 26, 2009, at 9:08 AM, Lobo <[email protected]> wrote:
We're in the early stages of planning a QoS rollout for our MPLS
enabled network and while we have in mind to offer about 4 different
classes (Real Time, Gold, Silver, Bronze/Best Effort), we were told
by Marketing that they wish to differentiate between different types
of Internet customers. Originally and like most standard practices,
any internet customer's traffic would normally be put in the BE
queue. Now we're getting requests to have say the low, bursty
internet customers (1.5Mbps - 3.0Mbps) get put into the BE queue
while a dedicated 20Mbps should go into the silver or even gold queue.
I have many problems with this like how would you be able to put the
20M customer's traffic in to the gold queue for traffic coming in
from the Internet? The only way I can think of is to match on their
IP space on each of our gateway routers but this would destroy our
gateways since they're already running hot enough. Another issue
is, what happens if that customer gets DDoS'd? This would mean that
we're guaranteeing that at least 20Mbps of DoS traffic would be able
to go through our network and to the customer's site. Oh and at the
same time probably affecting the data customers who would be using
the gold/silver queues for their services.
Do you guys have any advice whether it's more ammunition for me to
say no way or some kind of design/configuration that would possibly
work?
Thanks in advance.
Jose
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
