[Diffserv-interest] QoS in diffserv network

"Feng Y" <feng6@uwindsor.ca> Thu, 06 November 2003 18:17 UTC

Received: from optimus.ietf.org ([]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21248 for <diffserv-interest-archive@odin.ietf.org>; Thu, 6 Nov 2003 13:17:00 -0500 (EST)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHogV-0007qN-Cv for diffserv-interest-archive@odin.ietf.org; Thu, 06 Nov 2003 13:16:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6IGhuk030137 for diffserv-interest-archive@odin.ietf.org; Thu, 6 Nov 2003 13:16:43 -0500
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHofq-0007nA-1N; Thu, 06 Nov 2003 13:16:02 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHofJ-0007mW-0s for diffserv-interest@optimus.ietf.org; Thu, 06 Nov 2003 13:15:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21197 for <diffserv-interest@ietf.org>; Thu, 6 Nov 2003 13:15:15 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1AHofH-0005H3-00 for diffserv-interest@ietf.org; Thu, 06 Nov 2003 13:15:27 -0500
Received: from firewall2.uwindsor.ca ([] helo=internet2.uwindsor.ca) by ietf-mx with smtp (Exim 4.12) id 1AHofG-0005Gz-00 for diffserv-interest@ietf.org; Thu, 06 Nov 2003 13:15:26 -0500
Received: id LAA29572; Thu, 6 Nov 2003 11:29:02 -0500
Received: by gateway id 29474620 for <diffserv-interest@ietf.org>; Thu, 06 Nov 2003 11:29:01 -0500
From: "Feng Y" <feng6@uwindsor.ca>
To: diffserv-interest@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.4.0.6
Date: Thu, 06 Nov 2003 11:29:01 -0500
Message-ID: <web-29474620@uwindsor.ca>
In-Reply-To: <3F9F9F56.2917A11A@zurich.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id NAA21198
Subject: [Diffserv-interest] QoS in diffserv network
Sender: diffserv-interest-admin@ietf.org
Errors-To: diffserv-interest-admin@ietf.org
X-BeenThere: diffserv-interest@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=unsubscribe>
List-Id: Differentiated services general discussion <diffserv-interest.ietf.org>
List-Post: <mailto:diffserv-interest@ietf.org>
List-Help: <mailto:diffserv-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

>> 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
>for other traffic. (New to IP, that is. It's hardly a new

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
The gold service was allocated x percent of a link’s
bandwidth and silver service was allocated x/2 percent of
the link’s 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? 



Diffserv-interest mailing list