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

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Mon, 4 Feb 2002 11:54:18 +0100

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?
What if that field conflicts with ifSpeed?

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?

Bert

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