[Diffserv] Modeling of Policing component.

"ravikumarb" <ravikumarb@infosys.com> Sun, 30 June 2002 09:06 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 FAA26075 for <diffserv-archive@odin.ietf.org>; Sun, 30 Jun 2002 05:06:24 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id FAA16049 for diffserv-archive@odin.ietf.org; Sun, 30 Jun 2002 05:07:10 -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 EAA15020; Sun, 30 Jun 2002 04:56:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA14989 for <diffserv@optimus.ietf.org>; Sun, 30 Jun 2002 04:56:38 -0400 (EDT)
Received: from bosvwl01.infy.com (bosvwl01.infy.com [216.52.49.35]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA25853 for <diffserv@ietf.org>; Sun, 30 Jun 2002 04:55:51 -0400 (EDT)
Received: from 192.168.200.83 by bosvwl01.infy.com (InterScan E-Mail VirusWall NT); Sun, 30 Jun 2002 04:50:33 -0400
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS03.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Sun, 30 Jun 2002 14:26:25 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.4905); Sun, 30 Jun 2002 14:26:25 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Date: Sun, 30 Jun 2002 14:26:24 +0530
Message-ID: <56E2573C375A414191118970BDE06A1501C06C53@kecmsg06.ad.infosys.com>
Thread-Topic: Modeling of Policing component.
Thread-Index: AcIgFANv/ZAVvSfKSBelLji+cZpWJg==
From: ravikumarb <ravikumarb@infosys.com>
To: diffserv@ietf.org
X-OriginalArrivalTime: 30 Jun 2002 08:56:25.0180 (UTC) FILETIME=[039C39C0:01C22014]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA14990
Subject: [Diffserv] Modeling of Policing component.
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: 8bit

Hi,

I have a question on the difference between "policing" and "shaping".

According to my understanding following is the difference between them:

[1] Policing: Process of checking whether a packet is in-profile or out-of-profile. If it is out-of-profile, it will be dropped.
[2] Shaping: Process of conditioning the traffic stream so that it stays in-profile.

But acording to RFC 3290 in section 3.3, it says that policing can be modeled as a concatenation of an Algorithmic Dropper with a Scheduler. But I guess this should be the model for shaping rather than for policing.

Am I missing something here?

Thanks,

- Ravi


_______________________________________________
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