Re: [Isms] fingerprint TCs and hash types

[Wes Hardaker <wjhns1 at hardakers.net>]

>>>>> On Fri, 11 Sep 2009 20:22:56 +0200, Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de> said:

JS> I thought the MIB objects are there to support SNMP over DTLS so I
JS> consider them relevant for a 6LoWPAN environment. (The message size in
JS> those environments is really small - 127 octets excluding frame
JS> header) and fragmentation is pretty bad and buffer sizes are limited
JS> as well. So from this perspective, it prefer a binary OCTET STRING for
JS> the hash value.

Ahh...  I missed that point.  You want to make sure our objects our
manageable in that environment.  Check.

JS> I prefer a binary OCTET STRING encoding together with a 1x:
JS> DISPLAY-HINT. I have the feeling that an OID is overkill and I prefer
JS> a compact IANA maintained INTEGER TC. Depending on the IANA rules and
JS> if people seriously see a need for enterprise specific hash functions,
JS> I suggest to partition the INTEGER space following the Snmp*Model
JS> textual conventions.

I know of people that use enterprise specific hash functions, so I do
think we need to make room for it one way or another.

Thanks for solidifying your opinion; I understand it clearly now.
-- 
Wes Hardaker
Cobham Analytic Solutions