The Content (Cryptographic?) Hash Key is the workhorse on which other
key types build. Every document has a corresponding hash value that serves as it’s key. Two equal documents have equal hashes, so if different people insert the same document, this yields the same CHK. At the same time the hash function is built so that two different documents are very very unlikely to have the same hash (and therefore CHK). For all practical purposes, there is a one-to-one correspondence of CHKs to documents. Example: CHK@wQYjaBkpulyIBq4sbvyDL2NZ7ToPAwI,qW4hMEc6NWsx-T-etpfPAg All the other key types usually redirect to a CHK. So fundamentally, all real content is behind a CHK. KSK: These are fully free-form, so can be used to tag nice, descriptive names to content. By loose convention they are seen as a hierarchic system, with levelseparateded by slashes. When you request a KSK, the CryptographicHash of the keyword is computed. The CHK corresponding to this hash is retrieved, and the data pointed to by that CHK is another CHK to which you’re being redirected. Example:
