The counterpart "safe" TLD is part of a much bigger content curation problem that is evolving in the Internet. Some parents out there are not at all OK with Disney content, even, some will want to leave boobs in but head-crushing out, etc, etc. Properly tailoring to people's many shades of content filtering seems like a job for dedicated browser-recognized crypto certificate chains.
This way, different consumers can directly delegate trust to a custom choice of entities that already are engaged in this space (e.g. all the "family focus" agencies), instead of fighting over a centralized TLD committee.
Too bloody right. Here's a helpless girl that needs rescuing by a man to live happily ever after? No thanks.
You don't read the news much, do you? ;)
http://www.cms.kids.us http://www.wired.com/politics/law/news/2002/11/56429
Therefore, wouldn't a counterpart TLD, such as .SAFE, actually make more sense? Companies that target children, such as Walt Disney, could provide a guaranteed safe sub-internet. With wikipedia's new filtering options, they could put a wiki-subset on .SAFE with maximum filtering on.
It would be hugely costly to police, and so probably the most expensive TLD ever. But some companies would surely still be able to profit.