On Tue, Jul 07, 2020 at 04:24:03PM +0200, Ladislav Lhotka wrote: > > > ASN.1 had INTEGER, a type of unlimited precision. In the early SNMP > > days things started to fail to interoperate when you hit the 16-bit > > limit. JSON (much newer) has numbers that start to become interesting > > when you need more precision, a simple 64-bit counter starts falls > > apart in JSON. > > If you mean "counter64" in the ietf-yang-types module, then it doesn't > fall apart in JSON, provided that the rules of RFC 7951 are followed. >
I was alluding to plain JSON where you encode a number as a number until you realize that some numbers must be encoded as strings to avoid surprises. RFC 7951 does this for YANG defined data. /js -- Juergen Schoenwaelder 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
