On 14. Sep 2021, at 19:17, Jürgen Schönwälder <j.schoenwael...@jacobs-university.de> wrote: > > If other data models use an extended integer range and -1 to indicate > a special case, then this may be a strong reason to do the same in the > IETF YANG data model.
Any data model based on FORTRAN certainly will do. Most other data modeling languages by now should have nullable/optional/Maybe types. Going from the actual data type, uint16, to int32, just to accommodate the “not present” case, strikes me as a mistake. (Which doesn’t mean that you may not want to do this in an implementation, after having validated the input data.) Grüße, Carsten _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
