One answer to a slightly more general version of this question (why is OK for the clients to do nothing while the servers do the work) is that the client developers are often the server developers customers, they pay the bills.
Also in general there is a one to many mapping from a server to it's clients, the overall cost of updating a server and of it supporting multiple versions or transforming or whatever is much less than the overall cost of all the users of that server updating their client software. I'm not advocating for clients never updating, but I think it's unreasonable to think that clients will be updating as fast as servers, or to design a versioning scheme that assumes anything like that. Thanks, Chris. > On Jul 24, 2018, at 11:11 AM, Andy Bierman <[email protected]> wrote: > > Why is it OK for the client developer to decide "we are sticking with the > defective version of the module and not going to upgrade to > the fixed version like the server developers have done." >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
