On Mon, Mar 25, 2019 at 09:59:43PM +0000, Balázs Lengyel wrote: > Hello Jurgen, > > You are right that this is important mostly for instance data prepared as a > design/implementation activity; while not relevant for data coming from the > node. > I will add it. > > However in the first case it is vital! > > For config files, and also for file documenting server capabilities we have > had MANY problems with people changing the key values/identities of list > entries. > They think it is a nice idea to provide better, more meaningful key values; > however the NMS designers use these key values to detect changes; also > during an upgrade process if a default configuration file is loaded again > with slightly changed key values, then e.g. access control rules become > duplicated. >
The conditions under which it is meaningful to change keys and when it is not appropriate are very application specific. You may have specific use cases at Ericsson where you want internal regulations but I do not think this leads to meaningful rules outside your specific application scenario. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
