Subject: [i2rs] Three characteristics of an operation

From: "Rob (William) Rice" <[email-masked]>
Date: Thu, 14 Mar 2013 20:59:53 +0000

Alia's functional analysis presentation at today's I2RS meeting proposed three characteristics to an operation:

Start-Time (immediate, temporal, triggered)
Persistence across reboots (permanent, ephemeral)
Duration/State-expiration (unbounded, temporal)

I'd like to ask about the option to set a start (and presumably stop) time and the option to specify a duration. I assume the intention is to support these options for every item of I2RS installed state or configuration. I am wondering whether these time-based options are an essential part of the I2RS interface? Could we not simply require the client to install or remove the state/configuration at the desired time, thus eliminating the additional complexity in the I2RS interface itself and moving complexity from the network device to the controller? Are there use cases where the client cannot take action at the desired time?

(I get the reason for triggered events.)

Thanks,

Rob