August 2018 - RDS-WHOIS2-RT

REPORT URGENT: Implementation paragraph for R3.1
by Lisa Phifer Aug. 31, 2018

Aug. 31, 2018

Team, On behalf of Alan, please be advised that the implementation timeframe for R3.1 has been clarified as follows. *Implementation:* *This recommendation should ideally be implemented post-GDPR implementation, but no later than [TBD months] after the recommendation is adopted. The implementation should begin once it is moderately clear how GDPR will be addressed with relation to gTLD RDS (WHOIS). Should the implementation of this recommendation be deferred past FY2020, the then existing RDS (WHOIS)-related parts of the ICANN web site must be amended to cross-link the various sections on the RDS (WHOIS) portal, ICANN Contractual Compliance, Registrar and ICANN Learn.* During copy edits, it was noticed that the first sentence still contained a placeholder [TBD months] and could be seen as duplicating and perhaps even conflicting with the second sentence. To resolve this, Alan has proposed deleting the first sentence and letting the second sentence alone address implementation timeframe. Because this is more substantive than a copy edit, Alan asked that the RT be advised of this change. Any objection to this change should be raised to the RT list ASAP but no later than 29 August 23.59 UTC. Regards, Lisa

8 15

Re: [RDS-WHOIS2-RT] ICANN News Alert -- ICANN Releases its Second Report on Global Legislative and Regulatory Developments
by Carlton Samuels Aug. 31, 2018

Aug. 31, 2018

Apropos.... On Thu, 30 Aug 2018, 6:46 pm ICANN News Alert, <no-reply(a)external.icann.org> wrote: > [image: ICANN] <http://www.icann.org/> News Alert > > https://www.icann.org/news/announcement-2018-08-30-en > ------------------------------ > ICANN Releases its Second Report on Global Legislative and Regulatory > Developments > > 30 August 2018 > > ISTANBUL - 30 August 2018 - The Internet Corporation for Assigned Names > and Numbers (ICANN) published today the second report > <https://www.icann.org/en/system/files/files/legislative-regulatory-fy18-28a…> > [PDF, 214 KB] l highlighting a limited list of recent and pending > legislative and regulatory initiatives on privacy/data protection and > cybersecurity across the world. The report is a continuation of the > initiative launched earlier this April, to identify legislative efforts > across the globe early-on to raise awareness within ICANN and consider > potential impacts, including how these legislative initiatives may have > unintended consequences, which may be avoided. > > As a result of the community discussions over the past year or so leading > up to the GDPR going into full effect, ICANN CEO and President Göran Marby > committed to identify key legislative efforts around the globe while in > their earlier stages. To this end, ICANN org initiated > <https://www.icann.org/news/blog/improving-our-planning-and-preparation> > reporting efforts on global legislative and regulatory developments during > the third quarter of FY18. The first report > <https://www.icann.org/en/system/files/files/legislative-regulatory-fy18-23a…> > [PDF, 97 KB] was a limited list of some recent legislative and regulatory > initiatives around the world that relate to privacy/data protection and > cybersecurity issues and that could impact ICANN's mission, operations or > issues within ICANN's remit. It was the first product of a realization that > ICANN, as both an org and a community, must pay closer attention to > potential legislative efforts of interest across the world. > > The initial report received wide attention with a viewership of over six > hundred unique visits. The community feedback on the report was positive, > which paved the way for the continuation of the report on a quarterly > basis. We would like to take this opportunity to thank everyone who has > reviewed and provided feedback on the first report. > > We look forward to hearing from you about any high-impact developments in > the e-privacy and cybersecurity ecosystem that should be tracked in future > reports. You can send your comments and/or information about new > developments in your region to trackingfeedback(a)icann.org. > About ICANN > > ICANN's mission is to help ensure a stable, secure and unified global > Internet. To reach another person on the Internet, you have to type an > address into your computer - a name or a number. That address has to be > unique, so computers know where to find each other. ICANN helps coordinate > and support these unique identifiers across the world. ICANN was formed in > 1998 as a not-for-profit public-benefit corporation and a community with > participants from all over the world. > Manage Your Subscription > <http://app.icontact.com/icp/mmail-mprofile.php?r=22552788&l=6333&s=60BX&m=1…> > This message was sent to *carlton.samuels(a)gmail.com > <carlton.samuels(a)gmail.com>* from *no-reply(a)external.icann.org > <no-reply(a)external.icann.org>* > > ICANN News Alert > ICANN > 12025 Waterfront DriveSuite 300 > Los Angeles, CA 90094-2536 > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > [image: iContact - Try it for FREE] > <https://www.icontact.com/signup-trial?utm_medium=poweredby&utm_source=foote…> > >

1 0

Draft report - to be submitted for publication
by Lisa Phifer Aug. 31, 2018

Aug. 31, 2018

Team, Attached please find an updated 30 August draft of the RT's report, in redline and clean versions. As compared to the draft you received two days ago, this draft contains non-substantive copy edits agreed during today's leadership call, and updated versions of two appendices. Watch also for a separate email from Alan regarding the resolution he reached with Volker regarding the implementation timeline for R3.1. The plan is to submit this draft report tomorrow for publication. Your will likely see the report, along with the associated announcement and comment form, publicly posted early next week. Once again, thanks everyone for your hard work on this report, and for making it possible to reach this challenging end-of-month deadline. All the best, Lisa

1 0

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