Subject: [MIB-DOCTORS] YANG life-cycle issues - lessons from SNMP?

From: Andy Bierman <[email-masked]>
Date: Fri, 4 Apr 2014 15:43:35 -0700

Hi,

I am trying to think about NETCONF update procedures.
IMO SNMP mechanisms seem to have worked well
over the years.  The module update rules have not
been a heavy burden like they are becoming for NETCONF/YANG.

Is that just because of configuration vs. monitoring?
A client can easily ignore all new monitoring data but
it cannot easily ignore new input parameters.

Does SMIv2 allow a mandatory column to be added
to a table in a module update? It appears yes.
It would just be a change to the RowStatus description
clause, e.g., "column A, B, and E must be present in order
for this row to be in the active state".

But SNMP Set is not really deployed so maybe that is why
addition of mandatory columns is not visible as a problem.

Andy