[cabfpub] Ballot 218: Remove validation methods #1 and #5
sleevi at google.com
Mon Jan 8 02:24:31 MST 2018
On Mon, Jan 8, 2018 at 4:11 AM, Dimitris Zacharopoulos <jimmy at it.auth.gr>
> An example of pre-existing TLD adhering to this is .gov (in the US) - and
> I'm guessing you know of one or more ccTLDs that also fit into this
> The advantage being is that this permits non-gTLDs (i.e. those within the
> ICANN sphere of oversight) to use methods 'equivalent' to WHOIS. The
> disadvantage is that, in the absence of the registry agreements, the level
> of assurance or equivalence of those respective methods is at the
> determination of the ccTLD/TLD operator and the CA, and not uniform in
> assurance or reliability.
> The level of assurance for Domain Contact phone numbers and e-mail
> addresses is pretty much the same in most gTLD, ccTLD cases, that's why I
> proposed that they are combined with methods 22.214.171.124.2 or 126.96.36.199.3.
I don't believe we can simply state this. That is, we can objectively
evaluate, say, the ICANN Registry agreement, and the means in which the
information is provided and maintained, and make a determination on that.
Outside of those cases - legacy TLDs and ccTLDs - it's less clear that we
can objectively reach the same conclusions.
> I am hoping to have the WHOIS "equivalent" methods for all Domains. We are
> talking about Domain Validation methods so I don't think we should use
> "Organization Information" of WHOIS or Domain Registrar records to validate
> Domain ownership.
I wonder, then, if it would resolve your concerns about the removal of
188.8.131.52.1 to update the Domain Contact method - the issues I highlighted on
variability notwithstanding. That is, it sounds like we're in agreement
that 184.108.40.206.1, as worded, is entirely ambiguous as to the level of
assurance provided. The methods of contacting in 220.127.116.11.2/.3 are
acceptable, the only question is how we determine the information. We allow
WHOIS, for example, but as worded, it would preclude RDAP or other forms,
and would preclude the cases (such as .gov) in which direct registry
contact is required.
Domain Contact: The Domain Name Registrant, technical contact, or
administrative contract (or the equivalent under a ccTLD) as provided by
the Domain Registrar or, for TLDs in which the Registry provides
information, the Registry. Acceptable methods of determination include the
WHOIS record of the Base Domain Name, within a DNS SOA record [Note: This
includes the hierarchal tree walking, by virtue of 18.104.22.168's recursion], or
through direct contact with the applicable Domain Name Registrar or Domain
This can then be separately expanded to RDAP, or be moved more formally in
to a section within 3.2 as to acceptable methods for the determination of
the Domain Contact (e.g. moving the normative requirements for validation
outside of the definition).
That seems like it would resolve the issues, right?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Public