On Fri, Sep 15, 2017 at 5:39 PM, Phil Shafer <[email protected]> wrote:
> Andy Bierman writes: > >But this means if any clients use the disable-node feature then all > clients > >need to know about the feature as well, or they will mistake these nodes > >for enabled nodes (i.e., plain configuration according to the standard) . > > The alternative would be removing inactive config from normal > <get-data> results, which means that a save/restore would be > discarding inactive config, which isn't acceptable. Better to give > all data than to risk discarding anything. > > It might get set to "active" if the client preserves the special attribute it doesn't know about. This looks like 1 issue where each client cannot opt-in when ready. Too bad it can't be standardized, even in a simplified form. > Thanks, > Phil > Andy
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
