Hi all, I have a doubt about how and when the configured data in the running datastore can be validated.
According to section 5.1.3 of RFC8342: <running> MUST always be a valid configuration data tree, as defined in Section 8.1 of [RFC7950]. In some cases, there are some complex semantic validation rules which cannot be encoded in the rules defined in Section 8.1 of [RFC7950]. In this case the configuration is, from a semantic perspective, invalid and cannot be applied, even if the configuration data tree is valid as defined in Section 8.1 of [RFC7950]. It is not clear to me what is the expected behavior of the system when the client provides such a configuration. One possible option is that the system accepts that configuration but it does not apply it. In this case, the configuration is written in the <running> datastore, but never applied in the <operational> datastore. Another possible option is that the system accepts that configuration, it does not apply it but returns to the client a warning message. Also in this case, the configuration is written in the <running> datastore, but never applied in the <operational> datastore. A third option is that the system rejects that configuration and returns to the client an error message. In this case, the configuration is not written in the <running> datastore and thus never applied in the <operational> datastore. I am wondering whether all these implementation options are allowed or whether there are some standard requirements/restrictions on some of them. Thanks, Italo
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
