[Diffserv-interest] QoS in diffserv network

>> 
>> It is up to the carrier to monitor congestion
periodically to prevent
>> lowest-priority traffic from being too congested. EF
should ALWAYS get
>> through on-time, and AF CIR should always get through,
if somewhat delayed
>> and jittery. The cases when this is NOT true should be
rare and bizarre
>> (earthquakes, major network outages, etc.) unless the
carrier is not doing
>> their job... Which is simply to make sure they engineer
total network
>> bandwidth above the level of peak CIR.
>
>Exactly. Each traffic class (i.e. each queue) needs to be
provisioned for
>the expected load with appropriate over- or
under-provisioning. The new
>thing is that you can over-provision for some traffic and
under-provision
>for other traffic. (New to IP, that is. It's hardly a new
concept.)
>

Can we always assume that a higher service class provides
the same or a better service than any lower service class
in AF? Can the following scenario happen in Diffserv
network?
The gold service was allocated x percent of a links
bandwidth and silver service was allocated x/2 percent of
the links bandwidth, but the traffic intensity of gold
packets was 10 times higher than that of silver packets.

Should the ISP assure that there are not so many gold
packets in service? 

Thanks

Yang 

_______________________________________________
Diffserv-interest mailing list
Diffserv-interest@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv-interest