Hi, a good use of applied configuration could be to formalize the concept of system-controlled entries as defined in RFC 7223, routing-cfg, and probably elsewhere, too.
My idea is that system-controlled interfaces or other entries would appear in applied configuration, but not in intended configuration until something needs to be really configured. We could then permit leafrefs from intended configuration to refer to leafs in applied configuration. One case where this would be useful is the ACL module, where match conditions refering to interfaces currently have to use plain strings as references to interface names. However, the above idea seems to be at odds with requirement 1D in opstate-reqs-02. I wonder: could that requirement be relaxed or removed so that the above use case can be supported? Thanks, Lada -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
