RE: [Diffserv] ifSpeed with DiffServ PIB and Framework PIB [Previ ously Re: draft-ietf-rap-frameworkpib-06]

[Kwok Ho Chan <khchan@NortelNetworks.com>]

Bert:
Please see response inline.
-- Kwok --

At 11:54 AM 2/4/02 +0100, Wijnen, Bert (Bert) wrote:
>Kwok writes:
> >
> > An alternative to the treatment of ifSpeed by the DiffServ PIB is to
> > add an attribute qosIfSchedulerCapsIfSpeed to qosIfSchedulerCapsEntry
> > to indicate the bit rate that can "sink" the output of the Scheduler
> > Data Path Element.  This will allow the DiffServ PIB to not
> > rely on the Interface MIB.
> >
>So to me that sounds as "duplicating" information.
>How does this new field get filled out by the PEP?

The "ifSpeed" being discussed is the information required for the PDP
to formulate the correct scheduling policy parameters based on network
wide policies.  May be we should not use the term "ifSpeed" and allow
the scheduling policy parameter be not tightly coupled to interface.
This field should be filled out by the PEP as it sees what it needs to be
controlled by policy, and this is not necessarily an interface.

>What if that field conflicts with ifSpeed?

The scheduling policy parameter here may be totally different from
ifSpeed in the IF-MIB.  So I don't think the notion of conflict exists.


>Would any network device not have the IF-MIB implemented anyway,
>so the fact that you remove the dependency from the PIB, does not
>mean that the IF-MIB does not have to be implemented in the device,
>does it?

The removal of this dependency from the PIB does not say anything about
implementation of the IF-MIB at all.  It is up to the implementation what it
wants/needs to do.


>Bert