Re: [lmap] draft-ietf-lmap-information-model-05: Controller timeout

[Juergen Schoenwaelder <[e-mail]>]

On Tue, May 12, 2015 at 11:58:34AM +0000, Carey, Timothy (Timothy) wrote:
> Juergen,
> 
> So then we are saying that schedules (I think you mean scheduled tasks?) are operationally disabled and are reenabled with the controller is contacted.
> 
> We that would mean all scheduled tasks that are not related to controller communication - right? Since everything is a scheduled task now?

Yes, if in your implementation the communication with the controller
runs as a scheduled task, you better do not disable it. I have added:

  Note that this will not affect the execution of actions that are
  essential to establish contact with the controller or that perform
  critical housekeeping functions
 
> As to the int vs unsignedInt - I don't necessarily care except that one might ask what a meaning is for negative values unless you use lower threshold constraint of 0. Also you lose have the range of the timeout. What is the size of the int - 32 or 64-bit? My point is that if it is 32bit you its timeout would be limited to like 9+ hours (32767 seconds)
>

We address these questions in the YANG data model but I was hoping we
can leave out this level of detail in the information model. The YANG
model has this:

      leaf controller-lost-timeout {
        type uint32;
        units "seconds";
        description
	  "...";
      }

Note that 2^32-1 = 4294967295 seconds (which is approx. 136
years). You are calculating with 15 bits.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>