Re: [Diffserv] parameters section missing from the Diffserv PIB

Kwok Ho Chan <> Fri, 13 September 2002 17:58 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id NAA13917 for <>; Fri, 13 Sep 2002 13:58:06 -0400 (EDT)
Received: (from mailnull@localhost) by (8.11.6/8.11.6) id g8DHxNN06965 for; Fri, 13 Sep 2002 13:59:23 -0400
Received: from (localhost.localdomain []) by (8.11.6/8.11.6) with ESMTP id g8DHm6v06161; Fri, 13 Sep 2002 13:48:06 -0400
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id g8DHNAv04805 for <>; Fri, 13 Sep 2002 13:23:10 -0400
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id NAA12776 for <>; Fri, 13 Sep 2002 13:21:23 -0400 (EDT)
Received: from ( []) by (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8DHLkr13708; Fri, 13 Sep 2002 13:21:46 -0400 (EDT)
Received: from ( []) by with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RPMD3K70; Fri, 13 Sep 2002 13:21:47 -0400
Received: from (TWEEDY []) by with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NSA9N8CR; Fri, 13 Sep 2002 13:20:58 -0400
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Fri, 13 Sep 2002 13:18:46 -0400
To: Yacine El Mghazli <>
From: Kwok Ho Chan <>
Subject: Re: [Diffserv] parameters section missing from the Diffserv PIB
Cc: "Kwok-Ho Chan" <>, "Wijnen, Bert (Bert)" <>, Lemponen Jussi <>,, "" <>
In-Reply-To: <>
References: <> <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: Diffserv Discussion List <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Please see response embedded below.
-- Kwok --

At 09:54 AM 9/13/02 +0200, Yacine El Mghazli wrote:
>Kwok Ho Chan wrote:
>>Yacine, Jussi:
>>The Diffserv PIB already IMPORT Dscp and IfDirection from different 
>>modules of
>>the Diffserv MIB.  So I did not think there is any issue to also reused 
>>the definitions
>ok for reuse but here we're talking about OIDs...
>my question is: what is the signification of MIB-specific OIDs within a PIB ?

These "OBJECT-IDENTITY" are just constant values used to represent a 
parameter (more like a global #define in C).  They are just as if 
is defined in a PIB.  We are thinking of new PIBs reusing technology 
dependent definitions
in either existing PIBs or MIBs, whenever possible.
Hope this answered your concerns.

>in the previous versions of the PIB draft, these were identified by PRIDS, 
>they pointed towards a PRC within the same PIB... how does it work now ?

In DSPIB-06, IfSchedulerCapsServiceDisc and TBParamType were of type
"OBJECT IDENTIFIER", referencing objects of type "OBJECT-IDENTITY",
for example qosTBParamSimpleTokenBucket and qosSchedulerPriority.

Now they are of type "AutonomousType" which are TCs with syntax of
"OBJECT IDENTIFIER", as defined in RFC 2579 (SNMPv2-TC).
Referencing objects of type "OBJECT-IDENTITY", for example 
diffServTBParamSimpleTokenBucket and diffServSchedulerPriority.

Hence there is no change from the compiler point of view, and no change
from a usage point of view.  This is not related to PRIDS.

>>for dsTBParamType and dsIfSchedulerCapsServiceDisc from the Diffserv MIB as
>>advised during IESG review.
>>The Diffserv PIB's references to the Diffserv MIB are clearly specified as:
>>    dsIfSchedulerCapsServiceDisc OBJECT-TYPE
>>        SYNTAX      AutonomousType
>>        STATUS      current
>>          "The scheduling discipline for which the set of capabilities
>>          specified in this object apply. Object identifiers for several
>>          general purpose and well-known scheduling disciplines are
>>          shared with and defined in the Diffserv MIB.
>>          These include diffServSchedulerPriority,
>>          diffServSchedulerWRR, diffServSchedulerWFQ."
>>    dsTBParamType OBJECT-TYPE
>>        SYNTAX       AutonomousType
>>        STATUS       current
>>          "The Metering algorithm associated with the
>>          Token-Bucket parameters.  zeroDotZero indicates this
>>          is unknown.
>>          Standard values for generic algorithms are as follows:
>>          diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate,
>>          diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware,
>>          diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware,
>>          diffServTBParamTswTCM
>>          These are specified in the Diffserv MIB."
>>I believe the above text is clear.
>>Please advise if improvement can be made.
>>-- Kwok --
>>At 09:31 AM 9/12/02 +0200, Yacine El Mghazli wrote:
>>>I was wondering about this point:
>>>how are the OIDs identified in the MIB senseful within the PIB ?
>>>my understanding is that the PIB is an AUTONOMOUS named data 
>>>structure... in this context, what is the meaning of an OID referencing 
>>>nothing in the PIB itself ?
>>>thank you for your explanations,
>>>Wijnen, Bert (Bert) wrote:
>>>>I think they are the parameters that have been sepcified and identified 
>>>>in the diffserv MIB (RFC3289)
>>>>>-----Original Message-----
>>>>>From: Lemponen Jussi []
>>>>>Sent: woensdag 11 september 2002 23:02
>>>>>Subject: [Diffserv] parameters section missing from the Diffserv PIB
>>>>>Reading through draft-ietf-diffserv-pib-09.txt, I noticed that
>>>>>the parameters section in the PIB itself is missing. The descriptions
>>>>>for attributes dsTBParamType and dsIfSchedulerCapsServiceDisc do still
>>>>>imply that some parameter definitions should be there.
>>>>>Jussi Lemponen
>>>>>Tampere University of Technology
>>>>>Institute of Communications Engineering
>>>>>diffserv mailing list
>>>>diffserv mailing list

diffserv mailing list