Re: [Cbor] draft-ietf-cbor-tags-oid-00.txt

[[e-mail]]

Carsten Bormann <[e-mail]> writes:
> (Crypto) keys don't have to be much longer, see
> https://tools.ietf.org/html/draft-mattsson-cose-cbor-cert-compress-01#appendix-A
> for a worked example.

I don't know elliptic-curve crypto well enough to follow that, but it
seems to me that you're going to have a hard time putting a 2048 bit key
in less than about 256 octets, and the signature will need a similar
number of octets.  So all overheads should be counted against a minimum
of 512 octets of essentially binary data.

From: Sean Leonard <[e-mail]> writes:
> The most authoritative dotted-decimal OID style definition that I could 
> find is in the LDAP specs, namely <numericoid> in RFC 4512.

There is an OID namespace for URNs which uses dotted-decimal syntax; the
first version is RFC 3001 (Apr 2000), which refers to RFC 1778 section
2.15 (Mar 1995).

Dale