CBOR does this pretty well: <http://tools.ietf.org/html/draft-bormann-cbor-09>
On Tue, Oct 15, 2013 at 4:18 PM, Phillip Hallam-Baker <[email protected]>wrote: > > > > On Tue, Oct 15, 2013 at 5:18 AM, Paul Bakker <[email protected]>wrote: > >> On Oct 15, 2013 Phillip Hallam-Baker wrote: >> >> > As for getting rid of Assanine 1, I would love to get rid of it >> completely. But as >> > a pragmatic matter, there is just too much ASN.1 already. I have even >> had >> to >> > reluctantly write a key signing format in Assanine.1 because having the >> cert >> > and key signing in different syntaxes is just too confusing. >> >> While I do understand the reluctance for ASN.1, in an embedded >> environment I >> really prefer it over text parsing and buffer duplication that is required >> for JSON parsing.. >> > > There are real problems there for embedded apps and for cryptography. But > extending the JSON approach modestly to incorporate fixed length strings > and binary blobs solves 95% of them: > > https://datatracker.ietf.org/doc/draft-hallambaker-jsonbcd/ > > > Having to remember whether an object is implicit or explicit or vague is > just too much hassle. > > -- > Website: http://hallambaker.com/ >
_______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
