config tracking

[Kent Watsen <KWatsen@netscreen.com>]

Just wondering, is there any provision for getting the timestamp or 
Fingerprint of the device's config?  For instance, if the NetConf 
connection is disrupted and then re-established, the management app 
would need to (quickly) determine if the device's had been modified
and sending the full config is overkill when a simple fingerprint
would do.  Also, is there any provision for provisioning other 
aspects of the device such as its firmware?

My current thinking is that we would have to use BEEP and then create
proprietary channels for these kinds of things...


PS, great to see all the activity, for what its worth:
  - I only believe in the SSL/BEEP binding because it has channels, 
    which is a requirement for me.  I think that SSL/BEEP should be 
    NetConf's mandatory substrate - don't care if optional substrates
    are available.
  - I do believe in a NetConf default port, though it should be
override-able
  - I really support the idea of hooking-up with DMTF

Kent



--

Kent Watsen
Software Architect
NetScreen Technologies


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>