On 09/11/2018 18:35, Andy Bierman wrote:
Hi,
I think the requirements doc should state that
1) there are many more readers, operators, and client developers than
server developers so the solution MUST take into account the numbers
of people affected when finding a balance between client and server
complexity.
OK. So you would like the solution to be weighted towards clients, but
yet you do not want servers to have to implement any sort of version
selection, instead pushing the problem on to the client? :-)
More seriously, I'm looking for a solution where we it up to the market
to decide whether the complexity should be pushed to client, server, or
a 3rd party controller. I think that some sort of version selection
should be able to achieve this.
2) if existing protocol and YANG solutions exist then they MUST be used
in favor of developing new solutions.
If you replace the "MUST" with a "SHOULD" then I sort of think that this
one is obvious. I think that we are only trying to develop next
solutions where the existing ones do not appear to be working well.
There are examples in the earlier text in the requirements draft, and
also draft-clacla-netmod-yang-model-update to provide the background and
justify why we need to do something different than the status quo.
Thanks,
Rob
Andy
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
