[Ndn-interest] Describe the HMAC algorithm in SignatureHmacWithSha256?
shijunxiao at email.arizona.edu
Wed May 27 05:10:25 PDT 2015
Details about HMAC algorithm, or any other crypto algorithm, SHOULD NOT
appear in NDN Packet Format spec.
Instead, the implementer should be referred to RFC.
Those details are duplication of RFC, and they would make the spec
They also increase the probability of incorrect implementations because the
implementer is unsure whether it's exactly same as what she/he has in the
library, and would have to implement it again.
"don't have HMAC in their crypto library" is not a valid argument - it's
easier to find an RFC-compliant library or snippet for most languages than
to implement according to the (duplicate of RFC in) spec.
On Mon, May 18, 2015 at 4:00 PM, Thompson, Jeff <jefft0 at remap.ucla.edu>
> The proposed SignatureHmacWithSha256 spec (below) repeats the details of
> the HMAC algorithm from RFC 2104. But should the details be removed and
> just refer to RFC 2104? Arguments for keeping the details are that it
> provides details for the discussion of creating the KeyDIgest and also
> because some applications don't have HMAC in their crypto library and need
> to implement it directly. An argument against keeping the details is that
> the info is in RFC 2104 so an application writer can read the RFC if
> needed, and that we don't repeat the details of other algorithms like
> Any opinions on removing the algorithm details?
> - Jeff T
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest