On 27.6.2015 20.23, Steven Barth wrote:
Profile recommendations section in dncp recommends sha-256.
Er... -06 recommends the leading 8 octets of MD-5. Section 3.
DNCP recommends sha256 for profiles. HNCP uses what you mentioned.
1. simply copy the has received from the originator, no questions
asked;
2. hash the raw data received from the originator;
3. hash data that I've formatted from my internal data structures.
Since dncp mandates the canonical order this essentially means 2 and 3 are
identical. I personally don't believe in supporting buggy clients as in
clients violating MUST statements since at some point it just breaks.
Actually, I do not think it does anymore mandate _internal
implementation_ in dncp-06 (it used to earlier). However, on the wire,
there is canonical ordering of TLVs etc.
Anyway, [2] is correct, [3] is obviously impossible to interoperate
with, and [1] a bad idea.
Cheers,
-Markus
_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
