<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rektide</author><text>FWIW this came after a long long period of the DNSOP working group throwing hate and venom on this form of hithertofore non-normative DNS use cases. This was a &lt;i&gt;very&lt;/i&gt; hot topic and it seemed like absolutely no progress was going to be made making this happen for a long time due to the DNSOPS wg.&lt;p&gt;I don&amp;#x27;t have good citations- would love to gather them again- but it was only after other IETF members started questioning the absurd rejectionist behavior of the DNSOP working group that this changed, and the .onion draft was allowed to get due status.&lt;p&gt;I can&amp;#x27;t think of any case in IETF history of a draft being so hotly denied and rejected. Very interesting story, look forward to someone telling it better than I.</text><parent_chain></parent_chain></comment><story><title>The “.onion” Special-Use Domain Name (2015)</title><url>https://tools.ietf.org/html/rfc7686</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>eriknstr</author><text>About time (even though it was in 2015). I was afraid that someone was going to buy .onion and use it to deanonymize people who thought they were on TOR when they were not.</text><parent_chain></parent_chain></comment><story><title>The “.onion” Special-Use Domain Name (2015)</title><url>https://tools.ietf.org/html/rfc7686</url></story>