[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Agent Capabilities and sysORTable
- To: EOS WG <firstname.lastname@example.org>
- Subject: Agent Capabilities and sysORTable
- From: "Thomas, Steven C (Steve)" <email@example.com>
- Date: Tue, 17 Apr 2001 09:19:36 -0400
- Delivery-date: Tue, 17 Apr 2001 06:20:20 -0700
- Envelope-to: firstname.lastname@example.org
I need some help understanding here...
When I first saw the Charter discussing capabilities, I thought this might
be related to the agent capabilities addressed in the sysORTable. Since
then I understand that this part of the eos charter is referring to protocol
capabilities. However, having the agent document its MIB capabilities would
be desirable also.
My question is: Why don't most agents (I haven't found any so far)
implement or at least populate the sysORTable? Is there some hidden
difficulty in implementing it on the agent side? Or have I misunderstood
the purpose of sysORTable?
My comment is: If the agents don't bother to populate the sysORTable to
document their agent MIB capabilities, why would we expect them to populate
some other MIB documenting protocol capabilities? We need to understand the
dynamics in order to overcome them.
I am not arguing that the protocol capabilities MIB or mechanism isn't
needed, but I am cautious considering my experience so far with sysORTable.