in ietf-hardware [1] there are notifications defined that include leafrefs 
pointing to state data leaves. When the notification is generated, it is 
validated with regard to the current state data and if successful, the 
notification is then stored for possible future replay. Now, what happens when 
a client actually asks for notification replay including this notification? A 
server is no longer capable of validating it before sending because the state 
data changed. The same goes for the client, it is unable to validate 
notifications received from replay. Was this intentional, should the validation 
be simply skipped in this case?


[1] https://tools.ietf.org/html/draft-ietf-netmod-entity-08#page-29

netmod mailing list

Reply via email to