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.
regards Balazs On 2019. 03. 25. 14:19, Juergen Schoenwaelder wrote:
Hi, I am not sure why we have this new section. The notion of backwards compatibility for instance data is somewhat dubious. There text that is there now is potentially even harmful or it needs to be ignored. If I dump datastore content into an instance file, I get what I get. The text that is there may help with maunally edited instance files but this is where it ends. My proposal is to simply drop section 6 again. /js
-- Balazs Lengyel Ericsson Hungary Ltd. Senior Specialist Mobile: +36-70-330-7909 email: balazs.leng...@ericsson.com
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
