ENS name: dutch.eth

My reasons for wanting to be a delegate: I'm an early adopter in ENS and believe in the need for a decentralized naming service.

My view on each section of the proposed ENS Constitution

• Name ownership shall not be infringed: (Agree/Disagree/Comment) - Disagree. I think we need to be open to revoking ownership in certain illegal use cases (terrorism, child porn, drug markets, etc). We also might consider revoking ownership in clear trademark squatting cases (JoshHart.eth, Cocacola.eth, etc). We all want an open, decentralized, censorship-resistant internet, but I don't think that means we have to allow the tools we build to be used in highly immoral and illegal ways.
• Fees are primarily an incentive mechanism: (Agree/Disagree/Comment) Disagree. I believe the secondary goal outlined in the ENS proposed Constitution (i.e. funding the DAO and ENS development) is the more important reason to have registration/renewal fees. I believe the current ENS team has always been strangely pre-occupied with discouraging speculation and holding ENS names as an investment, and this view is misguided. Regardless, imposing a registration fee doesn't really do much to discourage speculation - it just is baked into the secondary sales. We need only look at DNS as an example of how this doesn't really work to discourage scalpers and squatters.
• Income funds ENS and other public goods: (Agree/Disagree/Comment) Agree.
• ENS Integrates with the global namespace: (Agree/Disagree/Comment) Mixed - I think we should try to work with ICANN and the existing DNS - especially to integrate resolution of the .eth extension in all browsers and email servers. But I believe we should be open to expanding suffixes besides .eth. The proposed constitution states as an example: "ENS governance must not create new top-level domains unless those domains have been granted to ENS by a DNS authority." I don't agree with that. I believe our goal should be that eventually ENS replaces DNS, not that it is absorbed into DNS. We shouldn't be asking permission from ICANN to release new ENS extensions.

My web3 qualifications / skills: I'm a licensed attorney with a lot of domain name experience. I've been coding for more than 25 years. I've done a bit of solidity and have coded and deployed a React site onto IPFS resolving to an ENS name.