IETF Logo Mail Archive

RE: [Diffserv] Modeling of Policing component.

"Andrew Smith" <ah_smith@acm.org> Mon, 01 July 2002 16:36 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17162 for <diffserv-archive@odin.ietf.org>; Mon, 1 Jul 2002 12:36:03 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA17029 for diffserv-archive@odin.ietf.org; Mon, 1 Jul 2002 12:36:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15684; Mon, 1 Jul 2002 12:29:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15653 for <diffserv@optimus.ietf.org>; Mon, 1 Jul 2002 12:29:23 -0400 (EDT)
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16556 for <diffserv@ietf.org>; Mon, 1 Jul 2002 12:28:35 -0400 (EDT)
Received: from user-vcaurdd.dsl.mindspring.com ([216.175.109.173] helo=ANDREWLAPTOP) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17P42X-00063n-00; Mon, 01 Jul 2002 12:28:37 -0400
From: Andrew Smith <ah_smith@acm.org>
To: 'ravikumarb' <ravikumarb@infosys.com>
Cc: diffserv@ietf.org
Subject: RE: [Diffserv] Modeling of Policing component.
Date: Mon, 01 Jul 2002 09:28:29 -0700
Message-ID: <06a401c2211c$591d2b80$1400000a@SMITH.smith.paloalto.ca.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <56E2573C375A414191118970BDE06A1501C06C59@kecmsg06.ad.infosys.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Diffserv Discussion List <diffserv.ietf.org>
X-BeenThere: diffserv@ietf.org
Content-Transfer-Encoding: 7bit

I disagree: if you follow an Algorithmic Dropper by a Scheduler (there's
an implied Queue in there somewhere), when the Queue starts to get full
due to "excess" traffic (arrival - departure > 0 over appropriate time
intervals), the Dropper will kick in. That is "policing" (it's doing
shaping at the same time of course). 

Meter->AbsoluteDropper is the more conventional way to think about
policing, I agree, but AlgorithmicDropper->Scheduler is also valid.

Andrew Smith


-----Original Message-----
From: diffserv-admin@ietf.org [mailto:diffserv-admin@ietf.org] On Behalf
Of ravikumarb
Sent: Monday, July 01, 2002 6:49 AM
To: Brian E Carpenter
Cc: diffserv@ietf.org
Subject: RE: [Diffserv] Modeling of Policing component.
...
We can have an Algorithmic Dropper as part of Policer, but not a
Scheduler. The moment we have a Scheduler, what we are doing is Shaping
not policing.



_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html

v2.23.0 | Report a Bug | By Email