Re: draft-ietf-vrrp-unified-mib-07 - deprecatingvrrpTrapNewMaster

Thanks Joan. I deprecated vrrpTrapNewMaster in favor of vrrpStateChange
notification.

>>
>> Will it be useful to include a previous state in the notification?
>>
>
>If the NMS missed one notification (i.e. a state change) then this
>might be useful, but if more than one notification (i.e. few 
>state changes) 
>were
>missed, then this might be more confusing.
>
>The alternative is that informs be used instead of 
>notifications, or that 
>the NMS
>poll for the info, or that the NMS be smart enough to deal 
>with missed state 
>change within the
>its correlation (which it probably needs to do even if using 
>informs or 
>polling).
>
>So, I would say sending the previous state doesn't hurt, but 
>may not help 
>too much.

I agree, previous state may not be useful. 
I will send a separate email regarding VRRPstateChangeReason that should
be included in the notification.

Thanks
Kalyan
_______________________________________________
vrrp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/vrrp