- RDS-WHOIS2-RT - lists.icann.org

Next possible move related to GDPR
by Alan Greenberg Aug. 30, 2018

Aug. 30, 2018

Not of direct relevance to our work, but perhaps interesting. Alan

2 1

.EU Facing "Radical" Makeover
by Carlton Samuels Aug. 29, 2018

Aug. 29, 2018

Didn't see anything much looking like radical - except for adoption of the VI framework - but then again..... https://www.lexology.com/library/detail.aspx?g=2b2e56e0-5826-458d-a66f-d9b6… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

2 1

REPORT URGENT: Updated draft for final read-through
by Lisa Phifer Aug. 29, 2018

Aug. 29, 2018

Team, Attached please find an updated 28 August draft of the RT's report, in redline and clean versions. This draft reflects the report content adopted during Monday's plenary call. You will find edits corresponding to agreements made in Monday's call marked in the redline with my initials "LAP." This draft also contains three substantive changes proposed by Alan, marked in the redline with his initials "AG." Those changes (1) resolve the Rec2 action item, (2) delete a sentence from R3.1 Implementation, and (3) add a Bylaws paragraph to the Exec Summary. Finally, this draft contains non-substantive copy edits (marked in the redline with "ED") for consistency in acronyms, terminology, format, cross-referencing to sections by number, and so forth. The bibliography appendix has now also been populated from each subgroup's referenced documents list. Those of you wishing to give the draft one last look before it gets submitted for publication, please do so using the attached CLEAN version. If you spot any substantive errors, please send them to the full RT mailing list no later than 29 August 23.59 UTC. Thanks everyone - Lisa

1 0

REPORT URGENT: Action Item Response
by Lisa Phifer Aug. 28, 2018

Aug. 28, 2018

Team, On behalf of Alan, below please find our response to Monday's plenary call action item. We were asked to clarify the Rec 2 subgroup's final question and answer in Section 3.3.3, Analysis and Findings -- see page 24 of the 26 August draft. Proposed alternative text appears below: *4) Finally, the subgroup considered whether the Board’s request <https://www.icann.org/resources/board-material/resolutions-2015-04-26-en#1.f> and process framework for a Next-Generation RDS PDP, using the EWG Final Report as input to (and, if appropriate, a foundation for) a new gTLD policy, was effective in producing the single comprehensive RDS (WHOIS) policy envisioned by the WHOIS1 Review Team.* *It is the RDS-WHOIS2 Review Team's view that, had the plan been executed to completion, a single comprehensive RDS (WHOIS) policy could have emerged. In any event, the ICANN Board-adopted Temporary Specification and the consensus policy expected to result from the Expedited PDP should form the basis for a single RDS (WHOIS) policy. It remains to be seen exactly what additional work, if any, may be need to create a single comprehensive RDS (WHOIS) policy.* Any objections or amendments to this proposed alternative text should be sent to the RT mailing list ASAP but no later than 29 August 23.59 UTC. Regards, Lisa

4 3

Plenary Call #40: Action Items/Decisions Reached
by Jean-Baptiste Deroulez Aug. 27, 2018

Aug. 27, 2018

Dear review team members, Following up on today’s plenary call #40, please find below the action items/decisions reached. We also attached the “recommendations prioritization” chart which was projected in Adobe Connect. Status of report: ADOPTED. On Executive Summary Status: Adopted with one edit: * Replace "privacy mechanisms" by "informal privacy/proxy mechanisms" On WHOIS1 Rec #1 - Strategic Priority Status: Adopted with following edits and recommendation priority * Replace "significant concern" with "significant importance" * Add footnote on policy * Add "ICANN did not take any action to address".to address SP10 and tie to relevant section * Agreement for R1.1 - 1.2 to be high priority * Agreement for R1.3 to be medium priority On WHOIS1 Rec #2 - Single WHOIS Policy Status: Adopted with following edits: * Improve readability (SP13) * Lisa/Alan to draft paragraph to address Stephanie's comment SP14 * Sentence "We would expect the affirmed Temporary Specification will exist as a digital artefact and will be the new base for a single documented source of all things pertaining gTLD Registration Data (WHOIS)." will be removed, to address comment SP16. * To address SP17: add footnote noting that there was one objection the Board did not notice in its acceptance. Use Accept instead of adopt. * To address SP18: hopefully instead of likely On WHOIS Rec #3 – Outreach Status: Adopted with following edits: * To address SP19, ICANN org to strike all from introductory sentence in all subgroups' sections * To address SP20, strike phrase pertaining to educate them * The first sentence should end "gTLD domains. The content should be revised..." * Agreement for R3.1 (including two suggested edits) with medium priority * Include after first sentence of the rationale for 3.2: this need was further supported by parts of the ICANN community * Agreement for R3.2 to be high priority On WHOIS1 Rec #4 – Compliance Status: Adopted with following edits: * Insert "contract negotiation or" after "in which case" in Feasibility * Agreement for R4.1 and R4.2 to be high priority On WHOIS Recs# 5-9 - Data Accuracy Status: Adopted with following edit: * Agreement to leave Priority as "To be determined" * Agreement on rec.5.1 On WHOIS 1 Rec#10 - Privacy/Proxy Services Status: Adopted with following edits: * Adjust text to use 31 December 2019 and remove "implementation timeframes notwithstanding" * Agreement for 10.1 and 10.2 to be low priority On WHOIS1 Rec#11 - Common Interface Status: Adopted with following edits: * Agreement for 11.1 to be low priority * Agreement for R11.2 to be high priority On WHOIS1 Recs#12-14 – IDNs Status: Adopted * Agreement for R12.1 to be low priority On WHOIS Recs #15-16 Status: Adopted * Agreement for R15.1 to be medium priority On Subgroup 2 Anything New Status: Adopted On Subgroup 3 Law Enforcement Needs Status: Adopted * Agreement on Rec.LE.1 & LE.2 with high priority * leave recommendation LE.2 as is, adding "on a regular basis" at the end * No objections On Subgroup 4 Consumer Trust Status: Adopted as is with no recommendations On Subgroup 5: Safeguarding Registrant Data Status: Adopted * Agreement on SG.1 with Medium Priority On Subgroup 6: ICANN Contractual Compliance Status: Adopted * CM.1 is accepted as is with priority "High" * CM.2: delete comment and accept as written, with Medium Priority * CM.3: agreed with priority set as "Low" * CM.4: Agreement for recommendation with "Low" priority. Add a footnote * CM5: Accepted. Low priority On ICANN Bylaws: Status: Adopted * Rec.BY.1: Adopted with Medium priority. Next steps Action Item: ICANN org to complete all of the edits listed above. * For any items the review team needs to discuss, review team members to send email with label REPORT URGENT. * If further discussion is needed on a unforeseen item, meeting will be held on Tuesday. Kind regards, Jean-Baptiste Deroulez

1 0

RDS-WHOIS2 Review Team Plenary | 15:00 UTC | 27 August 2018
by Jean-Baptiste Deroulez Aug. 27, 2018

Aug. 27, 2018

Dear review team members, In preparation for your plenary call, scheduled for Monday, 27 August at 15:00-17:00 UTC, please find below the proposed meeting agenda: 1. Welcome, roll-call, SoI 2. Review of Draft Report Sections - Resolve substantive comments raised and finalize consensus/objections to recommendations in on each section (1,30hrs) * Executive Summary (5 min) * WHOIS1 Rec #1 – Strategic Priority (5 min) * WHOIS1 Rec #2 – Single WHOIS Policy (5 min) * WHOIS1 Rec #3 – Outreach (5 min) * WHOIS1 Rec #4 – Compliance (5min) * WHOIS1 Rec #5-9 – Data Accuracy (5min) * WHOIS1 Rec #10 – Privacy-Proxy Services (5min) * WHOIS1 Rec #11 – Common Interface (5min) * WHOIS1 Rec #12-14 – Internationalized Domain Names (5min) * WHOIS1 Rec #15-16 – Plan & Annual Reports (5min) * Objective 2 – Anything New (5min) * Objective 3 – Law Enforcement Needs (5min) * Objective 4 – Consumer Trust (5min) * Objective 5: Safeguarding Registrant Data (5min) * Objective 6: ICANN Contractual Compliance Actions, Structure and Processes (5min) * ICANN Bylaws (5 min) 1. Recommendations prioritization (15 min) 2. Adoption of the report (10 min) 3. Roadmap reminder (1min) 4. A.O.B. (2min) 5. Confirm action items and decisions reached (2min) As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

1 1

PLEASE READ: Process going for
by Alan Greenberg Aug. 27, 2018

Aug. 27, 2018

Next Monday, we will have the plenary meeting to finalize the draft report contents and in particular the recommendations. The meeting is scheduled for 2 hours. The deadline for submitting objections to be discussed during the meeting is 23:59 UTC on Sunday, 26 August 2018. On Monday we will review any objections or alternate language and determine the level of consensus for each recommendation. There are a lot of sections and recommendations to cover so we will have to be brief and specific. We will also establish priority level for the recommendations. Although we will strive for full (unanimous consensus), it is not required and our ToR gives guidelines for this. Anyone who is not on the call and has not explicitly identified an issue is deemed to be in agreement with the current text. If any written statement of objection or dissenting opinions are to be included in the published draft report, they must be submitted no later that 23:59 UTC on Wednesday, 29 August 2018. Please be on time (or early!) for the meeting so that we can begin on the hour. Alan

2 3

Draft Report for Plenary Call
by Lisa Phifer Aug. 27, 2018

Aug. 27, 2018

Dear all, Attached please find the latest draft report for review in our 27 August plenary call, in both Word and PDF formats. This draft includes all comments and redlined edits received as of the 26 August 23.59 UTC deadline. Where comments affected text that had already been revised or could be easily addressed through copy-edits, that has been noted. In preparing for the plenary call, you may wish to focus on Section 1.2, Recommendations, and the redlined edits/comments therein, as any substantive objections on those draft Recommendations must be raised in this plenary call. Jean-Baptiste will be distributing call slides separately. For the agenda, see: https://mm.icann.org/pipermail/rds-whois2-rt/2018-August/000884.html Regards, Lisa

1 0

Review of recommendations
by Alan Greenberg Aug. 25, 2018

Aug. 25, 2018

I have reviewed the recommendations and have a number of comments and suggestions. R5.1 - Phrase in BLUE added for clarification Specifically added: The ICANN Board should direct the ICANN Organization to look for potentially-anomalous ARS results (e.g., 40% of ARS-generated tickets closed with no action because the RDS (WHOIS) record changed between the time the ARS report was generated and the time the registration was reviewed by Contractual Compliance) to determine the underlying cause and take appropriate action to reduce anomalies. ====== R10.1 - PP deadline: By the time the Board accepts these recommendations (ie about July 2019) or 31 Dec 2019. ====== R10.2 - Should this be "RDS (WHOIS) review team" instead of "RDS-WHOIS review team"? ====== R11.2 - Strongly believe that the recommendation should be focused on results and not methodology for achieving that. And particularly should not focus on the methodologies which my be unable to predice desired results. Therefore remove reference to Port 43. Also, clarify why two versions may be needed. Suggested re-wording: The ICANN Board should direct the ICANN Organization to continue to maintain the common interface to keep up to date with new policy developments or contractual changes for contracted parties to ensure that the common interface will display all publicly-available RDS (WHOIS) output for each gTLD domain name registration available from contracted parties, i.e., when they differ, both the registry and registrar RDS (WHOIS) output could be shown in parallel. ====== CM.2 - I know I raised the is of whether this covered MISSING or does not meet current verification standards, but do not recall the result. ====== CM.4 - Perhaps too late to bring this up now, but do we want to consider a footnote saying we are considering expanding the Rec to include a Rec that CC consider different, more efficient methodology in analyzing bulk data submissions where such data identifies patterns of problems. ====== The specific changes to R5.1 and R11.2 are in the attached redline. Alan

1 0

Fwd: [New post] How to import your Whois data into Watch My Domains
by Carlton Samuels Aug. 24, 2018

Aug. 24, 2018

From: Carlton Samuels <carlton.samuels(a)gmail.com> Date: Fri, 24 Aug 2018, 5:22 am Subject: Re: [New post] How to import your Whois data into Watch My Domains To: Domain Name Wire | Domain Name News & Website Stuff < donotreply(a)wordpress.com> Hmmmm. On Thu, 23 Aug 2018, 12:55 pm Domain Name Wire | Domain Name News & Website Stuff, <donotreply(a)wordpress.com> wrote: > Andrew Allemann posted: "Even with Port 43 limits and GDPR, you can still > download your Whois info from select registrars. A lot of domain name > investors use Watch My Domains Pro to manage their domain name portfolio. > But as domain name registrars limit access to Whois in the " > > New post on *Domain Name Wire | Domain Name News & Website Stuff* > <https://domainnamewire.com/?author=706> How to import your Whois data > into Watch My Domains > <https://domainnamewire.com/2018/08/23/how-to-import-your-whois-data-into-wa…> by > Andrew Allemann <https://domainnamewire.com/?author=706> > > *Even with Port 43 limits and GDPR, you can still download your Whois info > from select registrars.* > > A lot of domain name investors use Watch My Domains Pro > <https://domainpunch.com/wmdpro/> to manage their domain name portfolio. > But as domain name registrars limit access to Whois in the GDPR era, it has > become difficult for domain owners to download their own Whois data into > the program. > > There's now a way to download all of your Whois data into the program > without running into rate limits and other issues. It's accomplished using > registrar APIs. And before you dismiss this because you aren't technical, I > was able to set this up in 5 minutes with no technical skills. > > Here's the process: > > 1. Get your API key and secret from your registrar. > > Watch My Domains currently supports ResellerClub, GoDaddy, Namecheap, > Internet.bs and Dynadot. I got my GoDaddy API information by logging in and > going to developer.godaddy.com/keys. > > 2. Input your API info in Watch My Domains. > > Click on the API configuration icon and enter your info in the box that > pops up. > > 3. Import your data. > > The first step is to import your domains by clicking the Import button in > Watch My Domains. > > After downloading all of your domains you'll be able to do Whois lookups > on them that pull data through GoDaddy's API rather than Port 43 (which > doesn't return valuable information). > > Presto. > *Andrew Allemann <https://domainnamewire.com/?author=706>* | August 23, > 2018 at 12:55 pm | Tags: api > <https://domainnamewire.com/?taxonomy=post_tag&term=api>, gdpr > <https://domainnamewire.com/?taxonomy=post_tag&term=gdpr> | URL: > https://domainnamewire.com/?p=57257 > > Comment > <https://domainnamewire.com/2018/08/23/how-to-import-your-whois-data-into-wa…> > See all comments > <https://domainnamewire.com/2018/08/23/how-to-import-your-whois-data-into-wa…> > > Unsubscribe > <https://subscribe.wordpress.com/?key=75388cd2c16c1edb5a8b29d1a78fcb39&email…> > to no longer receive posts from Domain Name Wire | Domain Name News & > Website Stuff. > Change your email settings at Manage Subscriptions > <https://subscribe.wordpress.com/?key=75388cd2c16c1edb5a8b29d1a78fcb39&email…>. > > > *Trouble clicking?* Copy and paste this URL into your browser: > > https://domainnamewire.com/2018/08/23/how-to-import-your-whois-data-into-wa… > >

2 1