Re: [Isis-wg] draft-bhatia-manral-crypto-req-isis-01.txt

Jeff,

>> many characters not part of the standard character set and hence 
>> are invisible(so just the same as if they were not there).
>>     
> Fortunately, we don't depend upon people reading the TLVs to spot problems.  
>   
Agree. :) This was the document case which is given as a typical example 
for issues that might occur with hash collisions.
> The question is not how many packets hash to the same value, but 
> "Can you produce a valid, but different packet quickly?" 
Ok, let me clarify the whole thing. Being able to find collisions goes 
against the design of the hash function. There are now programs 
(referenced in the document) that can result in that. Though no known 
attacks are there for protocols currently, but because vulnerabilities 
have been found in the hashing mechanisms, the Security area currently 
does not promote the use of the hash functions. It suggest replacement 
of these hash functions. Infact NIST in the same theme as they developed 
AES have now made an open call for new Hash functions.

Just to clarify HMAC-MD5 and HMAC-SHA-1 do not suffer from collision 
attacks that are suffered by the non-HMAC versions.

The aim of the draft is to bring forward the issues with the current 
hash functions and clearly state the new mechanisms. As Tony said we 
need to clarify that further, so that no confusion results.

Thanks,
Vishwas

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg