Evan Daniel wrote: >> They only request the successful one, so the squatted ones fall out of >> the network. > > In which case, the KSK isn't actually the SHA of the final data...
Right - it's the SHA1 of the data stored under the KSK. The data stored under the KSK is the key of a redirect to the final data. The inserter can make any number of redirects to the same data, and therefore any number of distict KSKs, until one of them inserts without a collision, at which point the inserter has a KSK to give to the requester. Cheers, Michael
