Hey thanks for the Qs. Full disclosure, I'm not a security professional, more of a "make things happen in the DNS professional" but will answer as best I can.

Hey thanks for the Qs. Full disclosure, I'm not a security professional, more of a "make things happen in the DNS professional" but will answer as best I can. 1) I think DOH and the relatively recently announced ODOH are good for user privacy. I have real concerns about the concentration of that data in a few browsers (though ODOH helps that), and I have real concerns that IP interests are going to begin going after DNS resolvers not just for user data, but to prevent resolution. Like, what happens when someone sues Google for resolving Pirate Bay through chrome. Does the Pirate Bay just stop existing for people in that browser? 2) I think the DNS and its institutions (ICANN, IANA, etc) are going to be around for quite a while yet. Both blockchain and the DNS are methods of maintaining global uniqueness, and while there is LOTS of clunkiness and weird legacy choices in the DNS, it's so embedded in how everything from protocols to hardware work that migrating away from it is a decades long project. 3) Our focus at the DNS Abuse Institute is going to be on Phishing, Malware, Botnets, and Pharming. The volume of phishing and malware, and how they impact individuals sure feels like it adds up to something like Solarwinds. These things cause a LOT of harm and erode trust. 4) The answer to this is long, complicated, and contextual. Most Registrars and Registries are very averse to addressing issues of content at the DNS layer, with the exception of some universally illegal things like CSAM. There is however a growing awareness that Governments aren't capable of regulating in the way that they probably should. Most Registrar terms of service are going to let them do whatever they want, and there really isn't anything in their contracts with ICANN that's going to prevent that. Registrant protections is a topic we're likely to address at the DNS Abuse Institute, but around technical abuse issues, and not transgressive content issues.