[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Last Call: Remote Network Monitoring Management Information Base for High Capacity Networks to Proposed Standard
- To: rmonmib@ietf.org
- Subject: Re: Last Call: Remote Network Monitoring Management Information Base for High Capacity Networks to Proposed Standard
- From: Bill Fenner <fenner@research.att.com>
- Date: Thu, 11 Oct 2001 09:29:59 -0700
- Cc: mibs@ops.ietf.org
- Versions: dmail (solaris) 2.2j/makemail 2.9b
The following groups are unconditionally optional, due to their omission
from any MODULE-COMPLIANCE statements:
etherStatsHighCapacityGroup
etherHistoryHighCapacityGroup
hostHighCapacityGroup
hostTopNHighCapacityGroup
matrixHighCapacityGroup
captureBufferHighCapacityGroup
Although RFC 2580 makes it clear that groups that are defined but not
referenced are unconditionally optional, IMHO it's better to include
all groups in a MODULE-COMPLIANCE statement to give the author a chance
to describe under what circumstances they're optional.
Bill