On Wed, Mar 23, 2022 at 07:57:23AM +0100, Carsten Bormann wrote: > On 22. Mar 2022, at 21:04, Jürgen Schönwälder > <[email protected]> wrote: > > > > updates are done in a way to maintain backwards compatibility > > (Forward compatibility? > Backward compatibility = old data, new system. > Forward compatibility = new data, old system. > Just saying…) >
The design goal was to ensure that server upgrades do not break existing clients. We commonly call YANG data model changes ensuring that old clients continue to work 'backwards compatible'. This discussion seems to be about a scenario where a server has been upgraded and there are old and new clients talking to the same server, i.e., the problem is a version mix on the client side. Such a scenario is tricky and requires a lot of careful design since clients must be written with the idea in mind that they may have a limited view on the state of the world. /js -- Jürgen Schönwälder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
