On Tue, Apr 5, 2022 at 12:02 PM Jürgen Schönwälder < [email protected]> wrote:
> On Tue, Apr 05, 2022 at 10:03:25AM -0700, Andy Bierman wrote: > > > > > > The best outcome would be to fix ip-address to not include the zone, > > > introduce ip-address-zone, and deprecate ip-address-no-zone. My take > all > > > the is that all the existing usages do not require zone and this would > be a > > > fix as opposed to a change. > > > > > > > > I don't think this will harm our implementations. > > The type is still string. The pattern will change but that is handled by > a > > library. > > Whatever pattern is used will get handled the same way. > > Either a zone is allowed to be present or it is not, this does make a > difference, its not a cosmetic change. > True. The code will probably accept the pattern then fail trying to use the string. If the client sends the form with a zone. > > > The same problem exists for 'date' and 'date-no-zone' types, > > but they are not used very much. > > Perhaps we should call types a, b, c, and so on - this may force > people to read the descriptions. ;-) > For some reason, the smarter the person, the less likely they are to read any of the documentation before using some software. I call it the "it should work the way I would design it" phenomenon :-) You have to admit that Acee's suggestion is more intuitive than the current definitions. Clearly an NBC change. IMO it is more useful to put some YANG extension magic in these specific typedefs than just bumping a major revision number. This is a great use-case for the version DT. There probably is no solution path where nobody has to change any YANG or any code and everything still works. > > /js > > Andy > -- > 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
