The current CHKs, SSKs, USKs etc aren't very friendly for passing around - they need to be escaped in URLs, they're case sensitive, and they're rather long. KSKs and personal name->key directories can't be guaranteed to agree about which file corresponds to a given name.
Can we create short, secure, readable keys? How about a key that's simply the hash of an unencrypted redirect containing another key - a CHK, SSK or USK? The key would only need to be 128 bits (truncated SHA-1), the same length as a public key fingerprint or an IPv6 address. 128 bits translates to 32 characters in hex: 1dab-5a37-4c02-8d44-2a4a-9e3d-ea0d-a52c Hex can be made more readable (and even memorable) by converting each block of 4 digits into a word using the following table, inserting u, v or y as necessary to make words easier to pronounce: 0123456789ABCDEF OINMTSGLRPABCDEF 1dab 5a31 4c0m 8d44 2a4a 9e3d ea0d a53c idab sami tucom rudytut nata pemud eyavod asmuc Not exactly catchy, but easy enough to read out over the phone or write on a napkin. Cheers, Michael
