> On May 21, 2015, at 4:41 AM, John Levine <jo...@taugh.com> wrote: > > I share the concerns about calling .onion a TLD, but I think that's > easily fixable by calling it something like a special purpose > namespace, then going through the document and changing it where > appropriate.
Not to complicate matters, but CA/B-Forum are saying the following: https://cabforum.org/2015/02/18/ballot-144-validation-rules-dot-onion-names/ <https://cabforum.org/2015/02/18/ballot-144-validation-rules-dot-onion-names/> > 5. CAs MUST NOT issue a Certificate that includes a Domain Name where .onion > is in the right-most label of the Domain Name with a validity period longer > than 15 months. Despite Section 9.2.1 of the Baseline Requirements > deprecating the use of Internal Names, a CA MAY issue a Certificate > containing an .onion name with an expiration date later than 1 November 2015 > after (and only if) .onion is officially recognized by the IESG as a reserved > TLD. - my emphasis. It would be a shame for them to nitpick the rules because "special purpose namespace" != "TLD"? - Alec
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
