Sooooooooooooo... How are names going to be assigned? And how will the keys be distributed? With DNS it's relatively simple: The root namespace is divided bet

Sooooooooooooo... How are names going to be assigned? And how will the keys be distributed? With DNS it's relatively simple: The root namespace is divided between TLD registrars. I contact a reseller who buys a domain from the TLD registrars and generally offers a DNS server to administrate it. I then publish the address of my server via that DNS server. Controlling the DNS is sufficient to establish proof of ownership of that domain (set the MX record to an email server where you own the admin@ address) so you can use that to request an SSL certificate from a trusted Certificate Authority - all CAs are trusted for the entire DNS namespace. With NDN, this all goes out of the window. It seems that as of yet there's no plan on how to divide up the root namespace, and no plan how to manage certificates. Since there are no explicit addresses, all packages need to be signed ( or I could just set up a server and start answering request to /google/ ) but how will we know whether the key is trustworthy? How will we deal with expired or compromised certificates? If I let my key expire, will my service go down completely? How do we manage revoked certificates?