Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

2018-07-24 Thread Andy Bierman
On Tue, Jul 24, 2018 at 8:32 AM, Robert Wilton wrote: > > > On 24/07/2018 16:11, Andy Bierman wrote: > > > > On Tue, Jul 24, 2018 at 2:29 AM, Juergen Schoenwaelder < > j.schoenwael...@jacobs-university.de> wrote: > >> On Sat, Jul 21, 2018 at 05:47:45PM -0400, Christian Hopps wrote: >> >> > There

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

2018-07-24 Thread Robert Wilton
On 24/07/2018 16:11, Andy Bierman wrote: On Tue, Jul 24, 2018 at 2:29 AM, Juergen Schoenwaelder > wrote: On Sat, Jul 21, 2018 at 05:47:45PM -0400, Christian Hopps wrote: > There are actual instances where small perhaps non-disruptive

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

2018-07-24 Thread Andy Bierman
On Tue, Jul 24, 2018 at 2:29 AM, Juergen Schoenwaelder < j.schoenwael...@jacobs-university.de> wrote: > On Sat, Jul 21, 2018 at 05:47:45PM -0400, Christian Hopps wrote: > > > There are actual instances where small perhaps non-disruptive but > > incompatible changes are required. The example given

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

2018-07-24 Thread Juergen Schoenwaelder
On Sat, Jul 21, 2018 at 05:47:45PM -0400, Christian Hopps wrote: > There are actual instances where small perhaps non-disruptive but > incompatible changes are required. The example given to me for this > type of change was when the original specification had an obvious > bug (e.g., a range was