[ntpwg] [ntp:hackers] MS-SNTP

[David L. Mills]

Luke,

Note the pivot partions on the basis of value, not assigned bit fields. 
This is done specificatlly to give Autokey a large fraction of the 
space. Walling of the space seperately by fields would defeat that purpose.

I don't understand your comment about zero and endian. A little endian 
zero is identical to a big endian zero.

Dave

Luke Howard wrote:

>> You bring up a most interesting point. My fear is a violent trainwreck
>> between the Autokey key space and what I have been told the MS-SNTP  key
>> space. Because on Autokey pseudo-random key generation and hash  chains,
>> shrinking the key ID space much would create crippling collisions. On
>> the other hand, I understand the RID space is in the order of 500,  
>> which
>> is far below the symmetric key pivot of 65535. If the MS-SNTP key ID
>> space could fit below the pivot, that problem would disappear
>> completely. On the other hand, MS-SNTP key space might work if the  
>> pivot
>> point were increased from 2^16 to 2^18.
>
>
>
> Yes, but because of endian-ness issues, MS-SNTP key 0 is actually  
> 2^32-1.
>
> My original patch supported configurable partitioning of key space.
>
> -- Luke
>
>
> -- 
> www.padl.com | www.fghr.net
>