<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Cambria">SSC votes: "Yes".<br>
<br>
If we ever have a (language improvement) contest, the one below
should be the best candidate - significant improvement without
changing a single word. Good job!<br>
<br>
Thanks,<br>
M.D.<br>
</font><br>
<div class="moz-cite-prefix">On 5/22/2018 4:47 AM, Ryan Sleevi via
Public wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACvaWvZu=duFoM_4SLdVDsH1yUBqy1t9pGfEVjdmCz49CQY9PA@mail.gmail.com">
<div dir="ltr">Google votes YES.
<div><br>
</div>
<div>Noting, however, that despite the stated purpose of the
ballot, there is the risk that by being a selection of
options, we will have the unfortunately common risk of
misreading it **incorrectly** as:</div>
<div>"Retrieved (1) directly from the Domain Name Registrar or
registry operator via the protocol defined in RFC 3912, (2)
the Registry Data Access Protocol defined in RFC 7482, (3) or
an HTTPS website"<br>
</div>
<div><br>
</div>
<div>rather than the correct reading, which is:</div>
<div>"Retrieved directly from the Domain Name Registrar or
registry operator via (1) the protocol defined in RFC 3912,
(2) the Registry Data Access Protocol defined in RFC 7482, (3)
or an HTTPS website"<br>
</div>
<div><br>
</div>
<div>This would ideally be resolved in a subsequent ballot as
quickly as possible, for the benefit of our non-native English
speaking participants in particular, and to ensure that it is
clear and unambiguous the expectation, despite being plainly
stated in the Purpose as to what the desired interpretation
is. Ideally, such a ballot would not express normative
requirements in definitions, and might otherwise use an
explicit section to explain what process a CA should use for
the determination of this information, but for expediency
sake, clarifying in situ seems desirable.<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 15, 2018 at 3:21 PM,
Wayne Thayer via Public <span dir="ltr"><<a
href="mailto:public@cabforum.org" target="_blank"
moz-do-not-send="true">public@cabforum.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Ballot 224: WHOIS and <span
class="gmail-m_3728026185806746419m_-4056279355100754120gmail-il">RDAP</span><br>
<br>
Purpose of Ballot: The Registry Data Access Protocol (<span
class="gmail-m_3728026185806746419m_-4056279355100754120gmail-il">RDAP</span>)
is the successor to WHOIS, and this ballot adds
explicit support for <span
class="gmail-m_3728026185806746419m_-4056279355100754120gmail-il">RDAP</span>
to the BRs by adding a definition of "WHOIS". The new
definition permits the use of the registry or
registrar's web interface, and requires WHOIS
information to be retrieved directly from the
registrar or registry of the domain name.<br>
<br>
The following motion has been proposed by Wayne Thayer
of Mozilla and endorsed by Tim Hollebeek of DigiCert
and Adriano Santoni of Actalis.<br>
<br>
— MOTION BEGINS –<br>
This ballot modifies the “Baseline Requirements for
the Issuance and Management of Publicly-Trusted
Certificates” as follows, based upon Version 1.5.7:<br>
<br>
In section 1.6.1, add the following definition:<br>
<br>
WHOIS: information retrieved directly from the Domain
Name Registrar or registry operator via the protocol
defined in RFC 3912, the Registry Data Access Protocol
defined in RFC 7482, or an HTTPS website. <br>
<br>
In section 1.6.3, add the following references:<br>
<br>
RFC3912, Request for Comments: 3912, WHOIS Protocol
Specification, Daigle, September 2004. <br>
<br>
RFC7482, Request for Comments: 7482, Registration Data
Access Protocol (<span
class="gmail-m_3728026185806746419m_-4056279355100754120gmail-il">RDAP</span>)
Query Format, Newton, et al, March 2015. <br>
<br>
— MOTION ENDS –<br>
<br>
A comparison of the changes can be found at <a
href="https://github.com/cabforum/documents/compare/Ballot220...wthayer:Ballot224"
target="_blank" moz-do-not-send="true">https://github.com/cabforum/<wbr>documents/compare/Ballot220...<wbr>wthayer:Ballot224</a><br>
<br>
The procedure for approval of this ballot is as
follows:<br>
<br>
Discussion (7+ days)<br>
<br>
Start Time: 2018-05-03 19:00 UTC<br>
<br>
End Time: after 2018-05-15 19:00 UTC<br>
<br>
Vote for approval (7 days)<br>
<br>
Start Time: 2018-05-15 19:00 UTC<br>
<br>
End Time: 2018-05-22 19:00 UTC
<div
class="gmail-m_3728026185806746419m_-4056279355100754120gmail-adL"><br>
</div>
<br>
</div>
<br>
______________________________<wbr>_________________<br>
Public mailing list<br>
<a href="mailto:Public@cabforum.org"
moz-do-not-send="true">Public@cabforum.org</a><br>
<a href="https://cabforum.org/mailman/listinfo/public"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://cabforum.org/mailman/<wbr>listinfo/public</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Public@cabforum.org">Public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a>
</pre>
</blockquote>
<br>
</body>
</html>