On 2021-02-19, at 17:55, Juergen Schoenwaelder <[email protected]> wrote: > > Hi, > > can I safely replace > > leaf foo { > type int8 { range "0..100"; }; > } > > with > > leaf foo { > type uint8 { range "0..100"; }; > } > > or with > > leaf foo { > type int32 { range "0..100"; }; > } > > or are these a non-backwards compatible changes?
I don’t have an answer to that, but would like to point you to the table at the top of page 14 in draft-ietf-core-comi-11.txt [1], which would make the first replacement a non-backwards compatible change in the way we build URIs from that. [1]: https://tools.ietf.org/html/draft-ietf-core-comi-11#page-14 > Note that the value > set is always the same, however the underlying base type changes. Did > we ever define type equivalence? The way unions are handled in YANG gives me the impression that as long as the sets of XML representations generated by the two types are the same, they are equivalent. Grüße, Carsten _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
