This seems like a really good design, and one that CBOR was specifically
designed for. This design is a bit complicated, but that complication
directly matches one of the main design goals: "a format that has a
relatively low overhead to produce and minimizes the requirement for
further potentially costly compression". It would be good if that design
goal was all the way up in the Abstract or the beginning of the
Introduction, not buried at the end of Section 3.
Two small questions on the format itself:
- Why isn't everything in BlockTables optional?
- It feels like combining both class and type into ClassType might be
over-optimization. Since Class will almost always be IN, why not just
have this as its own object member?
--Paul Hoffman
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
