(Luis) Issue #6 for draft-ma-opsawg-schedule-yang – How to deal with schedules being received out-of-date.

[luismcontreras]

It can be due to an intentional attack or to the fact of that sender and receiver of the schedule have different time references. A silent discarding at the receiver can be robust for protecting but will not inform the sender about this potential issue.
Maybe a solution could be to assume an initial error message followed by a silent discard for a number of subsequent receptions, and then another error message (a kind of backoff mechanisms).

[boucadair]

This is a good point but we don't have data nodes in the common model.

Do yo have in mind an approach to enforce that in a common model? Thanks.

[danielkinguk]

Thanks for you pitching in her Med, some of this discussion will be documented in the TVR Requirements I-D, as requirements. Having early mechanism to achieve function in our solutions work is great, but we can capture things that are out of scope for our current YANG model(s), but highlight additional work may be required.

[boucadair]

@luismcontreras, @danielkinguk, thanks.

Please see #86 for an attempt to capture some of the inputs.