Hi, Earlier today Mach and I were asking Lada if we could have a config list w/o keys for our use case and he pointed us to this thread.
This is exactly what we need. For some lists we don't need to operate on individual list members. We don't need to inject a member in front of another remember. All we need is to specify a list of entries, which could even be non-unique. For example, we may want to configure a label stack used in a nexthop. The same label value could be used in different positions of the stack so the label itself could not be used as key. Typically we'd want to specify the entire stack from sctrach, and if a change is needed it'd be replaced entirely, or at most we may add/remove a label at the top or bottom of the stack. With the current requirement of a key for a config list, we'd need to assign an artificial ID as the key for the list. That is really cumbersome and does not provide any value. Hope this can be accepted and supported in the tools soon. Thanks. Jeffrey _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
