Re: [Netconf] issues with processing onboarding information (zerotouch)

[Martin Bjorklund <[e-mail]>]

Kent Watsen <[e-mail]> wrote:
> 
> > Do you mean that each script takes some kind of (conceptual) input
> > parameter that tells it to clean up the state produced by the previous
> > invocation?
> 
> Yes, exactly, it would be written as such, so implementations can choose
> how to do it.
> 
> 
> > Could we instead leave this to implementations?  In some environments
> > the server might be able to do the cleanup itself (which would be less
> > error prone).  In some other environments the scripts might not even
> > create any state.
> 
> Perhaps.  The text could just say "the device must, on error, exit the
> bootstrapping sequence leaving behind no state".

But even this might not be necessary in some environments.  I think
this whole notion of dealing with state associated with script
execution should be left to implementations to deal with.  It would be
ok if this document had some kind of Implementation Notes where things
like this could be discussed (w/o any 2119 language though).

> It would be good, I
> believe, to mention that some implementations may achieve this thru 
> infrastructure, whereas others may require scripts to 1) leave behind
> no state on error, and 2) provide a conceptual "clean up" parameter 
> for when an error occurs after a script had executed successfully.
> 
> What do you think?
>
> Kent


/martin