Balazs Lengyel <[email protected]> writes: > Hello, > > As I understood Andy, it was already agreed that if you advertise > support for a model that defines extensions you MUST support those > extensions. So you effectively advertise support for those extensions.
OK, so let's say a server advertises "ietf-system" (that imports "ietf-netconf-acm") with conformance-type "implement" and "ietf-netconf-acm" with conformance-type "import". Does the server support "nacm:default-deny-*" extensions or not? Moreover, clients don't advertise any modules. > As an example if you claim support for nacm, you MUST support its > extensions. NACM is different in that the nacm:default-deny-* extensions just give auxiliary information - they help NACM-aware clients avoid sending requests that result in access-denied errors. In contrast, a client that doesn't support schema mount cannot be used with a server that does. Lada > > Balazs > > > On 2016-07-29 15:31, Ladislav Lhotka wrote: >> For this approach to work, we would need to change the character of >> extensions, in particular: >> >> - an implementation should be able to signal which extensions are >> supported, >> >> - extensions that change the data model need to be labelled as mandatory >> to support. > > -- > Balazs Lengyel Ericsson Hungary Ltd. > Senior Specialist > Mobile: +36-70-330-7909 email: [email protected] > -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
