[RDS-WHOIS2-RT-Leadership_Staff] Checkpoint

Alan Greenberg alan.greenberg at mcgill.ca
Thu Feb 21 15:43:07 UTC 2019 

Realized Leadership was not copied on this.

In addition, for R11.1 - Common Interface. This Rec is not about Compliance (although it is possible that documenting outcomes might lead to noticing a compliance issue.

Alan

At 14/02/2019 09:46 AM, Alan Greenberg wrote:
At 13/02/2019 03:28 PM, you wrote:
Dear Alan, dear leaders,

Thank you for your email. See my replies below.

Also, would it be possible to move the leadership call to 16:00 UTC tomorrow (instead of 16:30 UTC)? Is there any topic you would like to add to the agenda? Thanks in advance for your confirmation.


  *   List of outstanding issues


Compliance
Action item: Susan to clarify that ICANN will not go on fact-finding missions, but use the information they currently have on hand (input received).
Susan to clarify that Compliance enforces Registrars to enforce data accuracy for registrants.
Action item: Stephanie to provide language update on Paragraph on "Possible Impact of GDPR and Other Applicable Laws "

Common Interface
Common interface recommendations do not seem to have taken into account the concerns around its implementation: “On recommendation 11.1 (common interface), based on the review team’s suggested implementation, it appears that the metrics and SLAs asked for in the recommendation are intended for use by ICANN org as mechanisms to proactively identify compliance issues. ICANN org would like to note that there are multiple reasons queries could return blank fields, or no results. It is not possible programmatically to determine the causes of these results. Additionally, per the Temporary Specification, gTLD registration data results could differ between registry and registrar outputs. Therefore, inconsistencies in registrar and registry gTLD registration data outputs are not necessarily compliance issues. ICANN org would also like to inform the RDS-WHOIS2 review team that the existing WHOIS look-up tool at whois.icann.org will be updated in the coming months with a new tool built on RDAP. It is possible and intended that the new tool would function in such a way that no data would be collected by ICANN org.”

It is understood that not all causes can be determined. However, that should not stop collecting statistics and when possible, determining cause (and possibly trying to ameliorate it). The three messages mentioned in the report are examples of symptoms/causes that are known.

It is understood that GDPR may cause different Ry/Rr output. That is the reason for R11.2.

I do not understand how the use of RDAP alters the basic issue.


Law Enforcement Needs
P5: Several edits from Cathrin, can they be incorporated?
P6: Open comment from Cathrin.

LE.1: Bring the above and survey questions to the EPDP (Alan) and GAC (Cathrin). Can you please confirm when this was completed?

MSSI to estimate number of hours spent on the LE survey in response to NCSG request for estimated cost associated with conducting the survey.

Objective 6: ICANN Contractual Compliance Actions, Structure and Processes
P8: One comment is still open.  The Registrar Working Group is reviewing the criteria from ICANN Org that will be used to determine whether any solution exists in the marketplace that is technically and commercially viable. The working group is expected to respond by 31 July 2018.

For the priority level definitions add in text "Implementation to begin once any preconditions are met."

Action item: Susan to update Objective 6 section based on operational input received.

Appendix H: Public Comments
Section needs to be populated to reflect this Bylaw requirement: “ICANN Bylaws, 4.6 (a)(vii)(B): “The final report should include an explanation of how public comments were considered as well as a summary of changes made in response to public comments.”

Where is this section? - not on Google Docs


Appendix I: Relevant Research Links
Access has been provided to Alan & Susan for updates on Privacy/Proxy Services section. Comments need to be resolved if no need for the review team to approve changes.


  *   Recommendations Consensus Call


Reminder was sent, please note that Erika had already confirmed (on list) approval of all recommendations, but also your input on Consumer Trust.


  *   Status of integrating Google Docs


I’ve started to incorporate the sections which are final. Thank you for noticing the issue with bullets and hyperlinks, I will do this last and believe this will need further review.

Kind regards,
Jean-Baptiste

On 2/13/19, 4:07 AM, "RDS-WHOIS2-RT-Leadership_Staff on behalf of Alan Greenberg" <rds-whois2-rt-leadership_staff-bounces at icann.org on behalf of alan.greenberg at mcgill.ca> wrote:

    Hi Jean-Baptiste,

    Can you please:

    - provide a checklist of any outstanding issues for me, Cathrin and Susan

    - Since I have not heard otherwise, I presume we are still awaiting
    confirmation of Recommendation agreement from Volker, Stephanie,
    Erika, Thomas and Chris. I will check on Chris. I presume that he has
    already received at least one reminder. If so, do not bother going to
    him again. Since he has not actively participated, it is probably
    better if he does not submit his position on the Recs. Please send
    messages to the other three asking for immediate response.

    - What is the status of integrating the Google Docs into a WORD docs
    (presumably one for the report itself and one for the Appendices).

    I have fixed the research section for P/P. The bullets are the wrong
    type but presume that will be fixed on the WORD Import. IWhile doing
    this, I noticed that in the original report, indented bulleted items
    had both the high-level and 2nd level bullets. I fixed these but the
    same problem may occur in other sections.

    I also noticed that the same problem  (missing hyperlinked text)
    occurred in the following section on common interface. I have run out
    of time to work on this now (EPDP!). Hopefully someone else can do a
    cut/paste from the original WORD doc to fix this.

    Alan

    _______________________________________________
    RDS-WHOIS2-RT-Leadership_Staff mailing list
    RDS-WHOIS2-RT-Leadership_Staff at icann.org
    https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt-leadership_staff/attachments/20190221/01fec890/attachment.html>

More information about the RDS-WHOIS2-RT-Leadership_Staff mailing list