Andy wrote: > A server can support a module without any protocol-accessible objects in 3 > ways > - implement the module with no features supported > - implement the module with features supported > - import the module without implementing it > > To Martin's point, it is not clear that a client is harmed because a server > lists a module in > the 'module' list instead of the 'import-only-module' list. > > > Andy
I just want to attest to the real world harm it causes when a server lists a module M in the modules list when it doesn't actually support it. The client then has to believe it is reasonable to issue a get-config request for the contents of module M. But when it does, the server then responds with an error, and the automation breaks down. The problem is cured by the server listing the non-implemented module M as an import-only-module. /Jan
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
