RE: [Diffserv] ifSpeed with DiffServ PIB and Framework PIB [Previ ously Re: draft-ietf-rap-frameworkpib-06]
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Mon, 04 February 2002 11:08 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 GAA18496 for <diffserv-archive@odin.ietf.org>; Mon, 4 Feb 2002 06:08:11 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA24766 for diffserv-archive@odin.ietf.org; Mon, 4 Feb 2002 06:08:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23451; Mon, 4 Feb 2002 05:55:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23427 for <diffserv@optimus.ietf.org>; Mon, 4 Feb 2002 05:55:15 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18244 for <diffserv@ietf.org>; Mon, 4 Feb 2002 05:55:11 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g14Ashr12933 for <diffserv@ietf.org>; Mon, 4 Feb 2002 05:54:43 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21) id <1ACQC4WS>; Mon, 4 Feb 2002 11:54:19 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E69BCAE@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Kwok Ho Chan <khchan@NortelNetworks.com>, rap@ops.ietf.org, diffserv@ietf.org
Cc: saurabh.kapoor@wipro.com, srinivasu.nampelli@wipro.com, ravi.attili@wipro.com, naganna.vydyula@wipro.com, krishna.akkineni@wipro.com
Subject: RE: [Diffserv] ifSpeed with DiffServ PIB and Framework PIB [Previ ously Re: draft-ietf-rap-frameworkpib-06]
Date: Mon, 04 Feb 2002 11:54:18 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
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
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 diffserv@ietf.org https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html
- RE: [Diffserv] ifSpeed with DiffServ PIB and Fram… Wijnen, Bert (Bert)
- RE: [Diffserv] ifSpeed with DiffServ PIB and Fram… Kwok Ho Chan
- RE: [Diffserv] ifSpeed with DiffServ PIB and Fram… Andrew Smith
- RE: [Diffserv] ifSpeed with DiffServ PIB and Fram… Andrew Smith
- RE: [Diffserv] ifSpeed with DiffServ PIB and Fram… Kwok Ho Chan