Re: [Isms] fingerprint TCs and hash types

["Joseph Salowey (jsalowey)" <jsalowey at cisco.com>]

> -----Original Message-----
> From: isms-bounces at ietf.org [mailto:isms-bounces at ietf.org] On 
> Behalf Of Wes Hardaker
> Sent: Thursday, September 10, 2009 1:49 PM
> To: isms at ietf.org
> Subject: [Isms] fingerprint TCs and hash types
> 
> 
> After doing research about what other fingerprinting / hash 
> textual conventions were out there, I found none.  Which 
> surprised me.  The end result was there was nothing to reuse, 
> so we do need to define our own.
> 
> The -00 version of the document defines 2 TCs for "fingerprints"
> (FingerprintType and FingerprintValue).  These are worded 
> generically so they can be reused elsewhere easily.
> 
>
>
> The biggest question, as I was defining the TCs, was what 
> type of data the FingerprintType should be.  Originally in 
> the personal versions of the draft, it was an integer.  But 
> it's highly likely that many other hashing algorithms will be 
> defined in the future, especially with the NIST hashing 
> algorithm "contest" going on right now.  So we certainly need 
> something with agility.  In the end, I changed the 
> FingerprintType to a OID instead.
> 
[Joe] I haven't had a chance to look at your document yet, but I guess
it depends on what you want specified in FingerprintType.  If you are
just looking for hashes there probably are already OIDs for this defined
for PKIX,PKCS,X509 etc.  In addition for Syslog TLS, RFC 5425, the
fingerprint support references the names for hash functions defined in
IANA registry "Hash Function Textual Names" allocated in RFC4572.  If
you are looking for something that is specifying hash and encoding then
I'm not sure there is anything formally defined.  It would be nice if
things lined up in some useful way with RFC 5425.  

> Note that in our MIBs at least, it's not being used as an 
> index so we don't have issues with the length restrictions it 
> would impose on MIB objects.  I could easily see other MIBs 
> wanting to put it in an INDEX though.
> 
> Feedback on these resulting TCs is greatly appreciated.
> 
> --
> Wes Hardaker
> Cobham Analytic Solutions
> _______________________________________________
> Isms mailing list
> Isms at ietf.org
> https://www.ietf.org/mailman/listinfo/isms
>