<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all- <div class=""><br class=""></div><div class="">I know I’m an alternate for this group and we’re not supposed to email, however I have some personal experience in this area that even ICANN Compliance might not know (or remember) regarding Alan’s question 4 below.</div><div class=""><br class=""></div><div class="">I led ICANN Compliance’s 2013 RAA compliance program. Our team reviewed the RAA for changes from the 2009 and 2001 versions, identified potential compliance areas, created outreach materials for registrars and the public, and built compliance processes for enforcing the RAA. Generally this was pretty straightforward (e.g. “Check to see if abuse contact info is on registrar’s website” for Section 3.18.1), however the Whois Accuracy Program Specification (WAPS) was a nightmare. Creating a flowchart of the WAPS obligations was difficult. We had to create processes for what was in the RAA, and not what made logical sense. </div><div class=""><br class=""></div><div class="">So yes, Alan is completely correct in that Section 4 of WAPS requires inaccurate info to be corrected and then the email address has to be verified. Even if the incorrect info is a telephone number or the postal address… the email gets verified (not the corrected information). Registrars must have evidence to support the corrected info such as using the credit card billing address on file or the customer shows a copy of the phone bill for the phone number, but the registrar does not have to call the number or check to see that the postal address is deliverable through some type of verification process. They just need to verify the email address (the choice to verify email/phone is in Section 1.f, but not Section 4). No other fields are ever required to be verified by the RAA- only validated (in large part due to the cost of verifying them). </div><div class=""><br class=""></div><div class="">There is an explanation how this wording appeared in the RAA. While I was at ICANN, one of the registrars who was on the drafting team (I think I know who it was but am not 100% sure so I don’t want to name them) told me that WAPS was something that was part of the final negotiations of the RAA. They had worked out the big changes in the main RAA, then had other miscellaneous items which were included in the various additional sections. WAPS was done sequentially. The agreed on Section 1, then 2, etc. When they discussed 4, they included the example of the bounced WDRP email, which when corrected they intended to verify the email after. Later modifications to Section 4 included covering all inaccuracies (not just bounced email) but they left in/neglected to update the email verification requirement for corrected data. So while it was unintentional, and does not make any logical sense, it is what is in the RAA and is thus what is enforced by ICANN. </div><div class=""><br class=""></div><div class="">Hopefully this provides some more clarify on the quirks of the RAA. I can complain about other sections at the lobby bar in The Hague. </div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Owen<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 25, 2022, at 10:48, Roger D Carney via GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st@icann.org" class="">gnso-accuracy-st@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<style type="text/css" style="display:none;" class=""> P {margin-top:0;margin-bottom:0;} </style>
<div dir="ltr" class="">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Good Afternoon,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Thanks for the clarity, Alan. I am not looking to approve and if someone wants to send questions to Org on their own, so be it, but I think that if we submit questions from the Scoping Team, that the questions should be vetted by the Scoping Team. Someone from
the Scoping Team might have some useful updates, or would like to add to the proposed questions, either way I think knowing the context (via discussion as we did with the first set of questions) of the questions is important and will help when reviewing the
responses.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Again, thanks for the clarification.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Thank<br class="">
Roger</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div id="appendonsend" class=""></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<hr tabindex="-1" style="display:inline-block; width:98%" class="">
<div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" class="">alan.greenberg@mcgill.ca</a>><br class="">
<b class="">Sent:</b> Friday, February 25, 2022 12:29 PM<br class="">
<b class="">To:</b> Roger D Carney <<a href="mailto:rcarney@godaddy.com" class="">rcarney@godaddy.com</a>>; Roger D Carney via GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st@icann.org" class="">gnso-accuracy-st@icann.org</a>>; Accuracy Scoping Team <<a href="mailto:gnso-accuracy-st@icann.org" class="">gnso-accuracy-st@icann.org</a>><br class="">
<b class="">Subject:</b> Re: [GNSO-Accuracy-ST] Additional questions for ICANN Org</font>
<div class=""> </div>
</div>
<div dir="ltr" class="">
<div style="background-color:#f2dede; padding-left:.5cm; border-left-width:5px; border-left-style:solid; border-left-color:#b94a48" class="">
<span style="font-size:11pt; line-height:16pt; font-family:Tahoma,Verdana,Segoe,sans-serif; color:#b94a48" class="">Caution:</span>
<span style="font-size:11pt; line-height:16pt; font-family:Tahoma,Verdana,Segoe,sans-serif; color:#b94a48" class="">
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span></div><p style="margin-top: 0px; margin-bottom: 0px;" class=""> </p>
<div class="">Roger, <br class="">
<br class="">
My first sentence was less than clear.<br class="">
<br class="">
I am submitting these questions to the scoping team for forwarding to ICANN Org.<br class="">
<br class="">
I did raise the first questions in a meeting and was asked to put them in writing.<br class="">
<br class="">
Earlier when we submitted questions to ICANN Org, we were assured that additional questions could later be submitted. My understanding is that our practice has been that the questions did not first need to be approved by the entire team.<br class="">
<br class="">
Alan<br class="">
<br class="">
<div class="x_gmail_quote">On February 25, 2022 11:55:20 a.m. EST, Roger D Carney via GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st@icann.org" class="">gnso-accuracy-st@icann.org</a>> wrote:
<blockquote class="x_gmail_quote" style="margin:0pt 0pt 0pt 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Good Morning,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="background-color:rgb(255,255,255); display:inline!important" class="">As I don't think recall these questions being discussed by the Scoping Team, </span>I assume Alan, that you are sending these to ICANN Compliance in your own capacity and not from the
Accuracy Scoping Team? </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Thanks</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
Roger</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div id="x_appendonsend" class=""></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<hr tabindex="-1" style="display:inline-block; width:98%" class="">
<div id="x_divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> GNSO-Accuracy-ST <<a href="mailto:gnso-accuracy-st-bounces@icann.org" class="">gnso-accuracy-st-bounces@icann.org</a>> on behalf of Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" class="">alan.greenberg@mcgill.ca</a>><br class="">
<b class="">Sent:</b> Thursday, February 24, 2022 11:08 PM<br class="">
<b class="">To:</b> Accuracy Scoping Team <<a href="mailto:gnso-accuracy-st@icann.org" class="">gnso-accuracy-st@icann.org</a>><br class="">
<b class="">Subject:</b> [GNSO-Accuracy-ST] Additional questions for ICANN Org</font>
<div class=""> </div>
</div>
<div class="">
<div style="background-color:#f2dede; padding-left:.5cm; border-left-width:5px; border-left-style:solid; border-left-color:#b94a48" class="">
<span style="font-size:11pt; line-height:16pt; font-family:Tahoma,Verdana,Segoe,sans-serif; color:#b94a48" class="">Caution:</span>
<span style="font-size:11pt; line-height:16pt; font-family:Tahoma,Verdana,Segoe,sans-serif; color:#b94a48" class="">
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span></div><p style="margin-top: 0px; margin-bottom: 0px;" class=""> </p>
<div class="">I am submitting the following five questions to ICANN Compliance.<br class="">
<br class="">
Alan Greenberg, Member representing the ALAC<br class="">
The 2013 RAA Whois Accuracy Program Specification section 4 requires a <br class="">
Registrar take certain actions if it has any information that specific RDDS <br class="">
fields are wrong (fields references are any of the name, postal address, <br class="">
e-mail address, voice telephone number, and (where available) fax number).<br class="">
<br class="">
The example given in section 4 of having such information is: “Registrar <br class="">
receiving a bounced email notification or non-delivery notification message <br class="">
in connection with compliance with ICANN's Whois Data Reminder Policy or <br class="">
otherwise”.<br class="">
<br class="">
Question 1: In the view of ICANN Compliance, does this example apply only <br class="">
to Registrars who happen to monitor such email bounce or non-delivery <br class="">
notifications, or are Registrars obliged to do such monitoring?<br class="">
<br class="">
Question 2: If a Registrar is obliged to monitor such email notification <br class="">
of non-delivery, are they similarly required to monitor other delivery <br class="">
methods (such as postal mail failure to deliver, or a message to through <br class="">
the Registrar’s domain management portal never being viewed)?<br class="">
<br class="">
Question 3: If a Registrar is obliged to do such monitoring, does ICANN <br class="">
Compliance audit this requirement?<br class="">
<br class="">
<br class="">
<br class="">
Section 4 goes on to require that “Registrar must verify or re-verify, as <br class="">
applicable, the email address(es) as described in Section 1.f…”<br class="">
<br class="">
Question 4: With respect to the reference to “email address(es)”, since <br class="">
the information about inaccuracy may be about any of the name, postal <br class="">
address, e-mail address, voice telephone number, and (where available) fax <br class="">
number, is the Registrar only required to verify or re-verify the email <br class="">
addresses (even if the inaccuracy was in respect to one of the other <br class="">
fields)? If other fields are included, please be specific as to what fields <br class="">
must be verified or re-verified.<br class="">
<br class="">
<br class="">
Question 5: The ICANN Org comments on the RrSG definition of accuracy <br class="">
saying that accuracy requirements are not limited to syntactical and <br class="">
operational accuracy implies that it may also include the requirement that <br class="">
the field contents are in fact associated with the RNH, and lacking such <br class="">
association, they may be deemed inaccurate. Is this an accurate reading of <br class="">
the ICANN Org comment, and if not, please explain just what the <br class="">
characteristics are that might make such fields inaccurate (in cases which <br class="">
are not as blatant as Mickey Mouse residing on Main Street of Disneyland)?</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">GNSO-Accuracy-ST mailing list<br class=""><a href="mailto:GNSO-Accuracy-ST@icann.org" class="">GNSO-Accuracy-ST@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-accuracy-st<br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></body></html>