From: Wes H. <har...@us...> - 2004-11-24 16:55:33
|
>>>>> On Wed, 24 Nov 2004 15:32:31 +0000, Dave Shield <D.T...@cs...> said: Robert> notReady is only used during row creation Dave> Where does it say that? My guess is that Dave is right, but it should rarely happen. You could put a row into notInService and then it could transition from there. EG for Robert: consider the SPD MIB filter table. take a row off line, add a bit saying you want to filter by port number but fail to include the port number in the set that turned on the bit... the only choice would be for either the set to be disallowed or for it to go to a notReady state. Robert> If want operational status, it needs it's own column. Dave> Why? I've got a perfectly serviceable column object which can do Dave> that job? Why clutter the MIB up with another (unnecessary) one? It's been long debated in the IETF as well. The general consensus (it was never 100%) was that a second column is a better way to go. -- Wes Hardaker Sparta |