[cabfpub] FW: Extension of period allowing .onion certificates
sleevi at google.com
Mon Nov 23 18:07:59 UTC 2015
On Mon, Nov 23, 2015 at 9:39 AM, kirk_hall at trendmicro.com <
kirk_hall at trendmicro.com> wrote:
> Our existing rule only allows .onion certs to be issued “after (and only
> if) .onion is officially recognized by the IESG as a reserved TLD.”
> Here is what IETF did – the RFC makes it pretty clear how the .onion
> domain may be used.
> However, it is a “special-use” domain. They also have “Policy Reserved
> I know at least one CA was of the opinion that it can no longer issue
> .onion certs.
> Maybe we should add an amendment to a future uncontroversial ballot
> (unless someone objects) to clear this up.
I'm not sure a ballot is necessary. This seems solely based on a
misunderstanding of the role of various SDOs and how the IANA process
works. This is no different than a member misunderstanding RFC 5280 -
that's not something we generally ballot to 'explain' how RFC 5280 works,
no more than we ballot to explain RFC 2119 language.
IANA reserved domains encompasses "Example Domains", "Test IDN top-level
domains", "Policy-reserved domains", and "Other Special-Use Domains". These
are all categories of reserved domains.
As you note, the IANA-managed registry is managed under the terms of RFC
6761 - which spells out somewhat unambiguously what it is:
"This document describes what it means to say that a Domain Name (DNS name)
is reserved for special use, when reserving such a name is appropriate, and
the procedure for doing so. It establishes an IANA registry for such
domain names, and seeds it with entries for some of the already established
special domain names."
If any such ballot is put forward, I think it would be extremely important,
if not necessary, for the CA you allude to to step forward and explain the
reasoning and source of confusion. Otherwise, this feels like dealing with
an abstract hypothetical, and any changes - positive or negative - will
merely be debated in the abstract, which would end up taking far longer
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Public