Hi Ruben, As I think you’ll see from the document, in our seeking classification of “.onion” in the “special use domains registry” under the terms governing that space, I think it’s fair for me to say that NXDOMAIN is pretty much what we’re shooting for.
There are probably some edge cases to the argument which should be clarified by more experienced DNSOP hands than I - Richard? - but overall I think we are in agreement regarding that aspect of the outcome. As for the “alleged” nature of the time-sensitivity, may I please direct your attention to: https://cabforum.org/2015/02/18/ballot-144-validation-rules-dot-onion-names/ …specifically: “Effective 1 October 2016, CAs SHALL revoke all unexpired Certificates whose subjectAlternativeName extension or Subject commonName field contains a Reserved IP Address or Internal Name.” …which I think would best be described as a “concrete” rather than “alleged” time sensitivity. - alec From: Rubens Kuhl <rube...@nic.br<mailto:rube...@nic.br>> Date: Tuesday, March 17, 2015 at 7:15 PM To: Alec Muffett <al...@fb.com<mailto:al...@fb.com>> Cc: dnsop <dnsop@ietf.org<mailto:dnsop@ietf.org>> Subject: Re: [DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-00.txt .onion was already under consideration under other drafts, but now there is a request specifically for .onion alleging time sensitiveness. But on the TLD-level, the only possibility of it becoming a response different from NXDOMAIN is a possible new gTLD round, something that is many years in the future... so the point for a .onion-specific work instead of it becoming part of a larger effort still escapes me.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
