[core] draft-ietf-core-links-json

[Jim Schaad <[e-mail]>]

While I realize this document is with the IESG, I was trying to work on my
link format implementation so I decided to read this document to see if I
could get it implemented for CBOR at the same time.  While doing this I came
up with the following:

1.  I believe that it would be worthwhile to say why the decision not to
encode items which match the "Cardinal" rule are not using the CBOR integer
types.  If I made a guess I would guess it is because JSON does not handle
integers correctly but I do not know that for a fact.  If this was used then
the encoding would be smaller.

2.  I would like to verify that the following was intended.  In the CDDL,
value appears to be able to support an array that contains both strings and
Booleans mixed together.  That seems to be a strange source and I don't know
it is real.

Jim