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

Re: [RDS-WHOIS2-RT] REVIEW NEEDED: ICANN62 Engagement Session Description
by Alan Greenberg May 29, 2018

May 29, 2018

How about ending with: This is your opportunity to provide input to the RDS-WHOIS2 Review Team prior to the finalization of their Draft Report. That emphasizes what stage we are at and supports our request to be removed from the Public Comment. Alan At 29/05/2018 02:06 AM, Cathrin.BAUER-BULST(a)ec.europa.eu wrote: >Dear all, > >Some small edits proposed in the text below (in bold and red) to >clarify 1) the "this" in the second sentence and 2) that this >engagement session is one opportunity to provide feedback (i.e., >there will be more) just to avoid misunderstanding. > >All best >Cathrin > >From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On >Behalf Of Jean-Baptiste Deroulez >Sent: Monday, May 28, 2018 10:15 PM >To: RDS WHOIS2-RT List >Subject: [RDS-WHOIS2-RT] REVIEW NEEDED: ICANN62 Engagement Session Description > >Dear Review Team members, > >Following the action item identified today on plenary call ><https://community.icann.org/x/MgMFBQ>#28, please review the below >updated ICANN62 engagement session description and confirm by >tomorrow, Tuesday 29 May 2018 23:59 UTC whether you have any edits/comments. > >Join a discussion with the Registration Directory Service Review >team (RDS-WHOIS2). > >The Registration Directory Service Review, formerly known as "WHOIS" >(RDS-WHOIS2) is mandated by the ICANN Bylaws., thisThe scope of its >work includes assessing how the recommendations of the first WHOIS >Review were carried out, as well as assessing the effectiveness of >the gTLD registry directory service and whether its implementation >meets the legitimate needs of law enforcement, promoting consumer >trust and safeguarding registrant data. The RDS-WHOIS2 Review Team >will update the community on its findings to date and seek input on >its findings as well as address any questions pertaining to its >scope and work plan. This is your one opportunity for you to provide >input into the RDS-WHOIS2 work. > >For more information, please visit the RDS-WHOIS2 wiki ><https://community.icann.org/display/WHO/RDS-WHOIS2+Review/>https://community.icann.org/display/WHO/RDS-WHOIS2+Review/. > > >Learn more about opportunities to participate in RDS-WHOIS2 work at: ><https://community.icann.org/display/WHO/Observers>https://community.icann.org/display/WHO/Observers. > > > >In absence of comments/edits, the ICANN62 engagement session >description will be considered approved. > >Kind regards, > >Jean-Baptiste >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YTOPR01MB0396;27:HutsYQzWF4ZxT9WvcAM27AphOaNoZT5Whip//g127FwNulBnXxwtZY+wIFVNL7Ec8ysZEM6OBquwJqOGD0H9JFoteKZJw7C8Md8re/Da9nYTobGbsb0l0P8oB7SWLCrD >X-Microsoft-Antispam-Message-Info: > >w622i0WDpmO36HanWTrzNpQqe+roQ4fWuLbxRadl3p7nbno/4IgNM7IoF+bb8rXC5eUbwJNDgxadFkXSyFbOu8yqZPUYaqTbTv2RpmPOliBB4IUik8/twEj55NyCWQk0jced1r9vNl3P7hgQkgUzaKqTpfWkomYX46HoYX0PBBEUjqe7f0cfbnN4WoLLF5fGrvCPDE3Zjuq53NYMFw+AjwBdMuLvgQ032xj6MnzoDHsR2jLR0Odc9wCSsXu+yijspwtF+ByEOO/6lJC0LOL8+eZVEK5D8XDTEuTFtg69BPsQKtUXPw5RVtgOYoL/CwQPWl+M3qNdGz+N71pQVWKnXQSLkZSI2FcgrYgjaaW+wI63v43GD0DGnbWv0quV3vmT7IfA39lVTwqr720g2OoEIsujwmD0imEVIMENWftynEbM8wHih0n6m3rbbvJq2cIXyGK/hQvFLcTCtp7ZwD5tssPbWcFoOOKTmJz0+XqQbi0RX3T5+pEE0Zt+iC9WvIh+ > >_______________________________________________ >RDS-WHOIS2-RT mailing list >RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt

2 1

REVIEW NEEDED: ICANN62 Engagement Session Description
by Jean-Baptiste Deroulez May 29, 2018

May 29, 2018

Dear Review Team members, Following the action item identified today on plenary call #28<https://community.icann.org/x/MgMFBQ>, please review the below updated ICANN62 engagement session description and confirm by tomorrow, Tuesday 29 May 2018 23:59 UTC whether you have any edits/comments. Join a discussion with the Registration Directory Service Review team (RDS-WHOIS2). The Registration Directory Service Review, formerly known as "WHOIS" (RDS-WHOIS2) is mandated by the ICANN Bylaws, this includes assessing how the recommendations of the first WHOIS Review were carried out, as well as assessing the effectiveness of the gTLD registry directory service and whether its implementation meets the legitimate needs of law enforcement, promoting consumer trust and safeguarding registrant data. The RDS-WHOIS2 Review Team will update the community on its findings to date and seek input on its findings as well as address any questions pertaining to its scope and work plan. This is your opportunity to provide input into the RDS-WHOIS2 work. For more information, please visit the RDS-WHOIS2 wiki https://community.icann.org/display/WHO/RDS-WHOIS2+Review/. Learn more about opportunities to participate in RDS-WHOIS2 work at: https://community.icann.org/display/WHO/Observers. In absence of comments/edits, the ICANN62 engagement session description will be considered approved. Kind regards, Jean-Baptiste

6 5

The next battle is on the horizon - e-Privacy EU-style
by Carlton Samuels May 29, 2018

May 29, 2018

Um, well, this is another one that just sidled upon us, just like one of them sneaky Atlantic hurricanes! https://nyti.ms/2sk7lP4 -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

2 1

Public Comment on Short Term Options
by Alan Greenberg May 29, 2018

May 29, 2018

During today's plenary call, the RT decided to accept Theresa Swineheart's offer and request that the RDS-WHOIS2 Review be removed from the Public Comment on Short-Term Options to Adjust the Timeline for Specific Reviews. Although I am not sure that the decision can be viewed as consensus using the rule-of-thumb of 80%, it was definitely a majority decision. The group did consider the issue raised by Chris. Specifically to what extent would we be viewed in a bad light for cutting off comment on our work. There was a strong belief that we are doing this for good reasons and that presuming the team members go back to our home constituencies and explain what we are doing, in balance, this is the right decision. This is not in final form, but and identification of the major points to get review team closure. I am not looking for word-smithing but rather any issues misstated of missing. I would like to have a draft ready by Wednesday, so please review this as soon as possible. ----------- Letter sent to Theresa Swineheart on beheld of the RDS-WHOIS2-RT and also posted to the Public Comment. The rationale that we will use to make this request is based on our belief that once a number of inaccuracies and misrepresentations are corrected, there is little to be gained at this point from altering the scope or pausing the review. There are some review team members and others in the community who believed that this review should have been deferred, or its scope restricted to just a review of the first WHOIS RT's Recommendations. That was thoroughly discussed prior to the review and during the scoping phase. Ultimately, it was decided that the review must continue and should not be restricted. That was many months ago and we cannot turn back the clock but must look at today's situation, and where we will be when the Public Comment (PC) completes in July. = The Review Terms of Reference (ToR) does state that due to GDPR, we MAY defer some aspects of the review which we did not believe would substantially alter our completion target. In fact, we have not deferred anything at this point and now believe that GDPR will have a significant impact on our work. The full implementation of GDPR may or may not be understood by the time we deliver our report, but we will certainly understand the overall direction and that will be a factor in our report. It is clear that the real impact will not be well understood by then nor even a few months later, so the analysis of that will have to wait for a subsequent review. = The document implies that because there are only ten RT members, there are insufficient people to do the work. In fact there are just ten members, but all are working together and the number of active workers may well exceed the number of active workers on previous larger teams. = The PC document says that $460k will be saved in FY19 by restricting the scope of the review and that $590k will be saved by pausing the review. The review team has not been involved in estimating any of these budgets and does not believe that they are accurate. [Financial Analysis here] = The public comment is due to close on 06 July 2018 with the staff report due on 23 Jul7 2018. According to the current Review Team work plan, the Review Team is scheduled to have a face to face meeting 19-20 July 2018. Our intent is that we finalize the content of our draft report at that time. Moreover, unlike some draft reports which are comprised of many questions to the community, we believe that this will really be a draft report looking for community comment before finalizing it. It makes little sense for the group to reduce its scope or completely pause just at the point when it is ready to deliver its draft report. By that time, the bulk of the work will have been done, and to scrap part of it or pause for a year implies much of that work will have to largely be repeated again later. The RT specifically notes that Option C, to have the Review paused in April (a date that had long past when the PC was issued) made no sense whatsoever given that the community input to make that decision would only be available in late July. The Review Team believes that if it had been consulted when this Public Comment was being contemplated and developed, the RDS-WHOIS2 Review would never have been included. Moreover, the Review Team strongly believes that if a RT is to be held accountable for keeping to its "budget" (as is the current practice), the RT MUST be involved in developing that overall budget and the annual FY budgets that it must operationally adhere to.

3 2

Plan & Annual Reports subgroup draft report
by SUN Lili May 29, 2018

May 29, 2018

Dear all, Please refer to attached the revised version of the draft report on Plan & Annual Reports, for your comments. Thanks, Lili *************************************************************************************************** This message, and any attachment contained, are confidential and subject of legal privilege. It may be used solely for the designated police/justice purpose and by the individual or entity to whom it is addressed. The information is not to be disseminated to another agency or third party without the author’s consent, and must not be retained longer than is necessary for the fulfilment of the purpose for which the information is to be used. All practicable steps shall be taken by the recipients to ensure that information is protected against unauthorised access or processing. INTERPOL reserves the right to enquire about the use of the information provided. If you are not the intended recipient, be advised that you have received this message in error. In such a case, you should not print it, copy it, make any use of it or disclose it, but please notify us immediately and delete the message from any computer. *************************************************************************************************

1 0

Re: [RDS-WHOIS2-RT] Public Comment on Short Term Options
by Alan Greenberg May 29, 2018

May 29, 2018

Just a note to say that at the meeting today, we had 9 of the 10 RT members present. Only Dmitry could not attend. Alan At 28/05/2018 10:43 PM, Alan Greenberg wrote: >During today's plenary call, the RT decided to accept Theresa >Swineheart's offer and request that the RDS-WHOIS2 Review be removed >from the Public Comment on Short-Term Options to Adjust the Timeline >for Specific Reviews. Although I am not sure that the decision can >be viewed as consensus using the rule-of-thumb of 80%, it was >definitely a majority decision. > >The group did consider the issue raised by Chris. Specifically to >what extent would we be viewed in a bad light for cutting off >comment on our work. There was a strong belief that we are doing >this for good reasons and that presuming the team members go back to >our home constituencies and explain what we are doing, in balance, >this is the right decision. > >This is not in final form, but and identification of the major >points to get review team closure. I am not looking for >word-smithing but rather any issues misstated of missing. > >I would like to have a draft ready by Wednesday, so please review >this as soon as possible. > >----------- > >Letter sent to Theresa Swineheart on beheld of the RDS-WHOIS2-RT and >also posted to the Public Comment. > >The rationale that we will use to make this request is based on our >belief that once a number of inaccuracies and misrepresentations are >corrected, there is little to be gained at this point from altering >the scope or pausing the review. > >There are some review team members and others in the community who >believed that this review should have been deferred, or its scope >restricted to just a review of the first WHOIS RT's Recommendations. >That was thoroughly discussed prior to the review and during the >scoping phase. Ultimately, it was decided that the review must >continue and should not be restricted. That was many months ago and >we cannot turn back the clock but must look at today's situation, >and where we will be when the Public Comment (PC) completes in July. > >= The Review Terms of Reference (ToR) does state that due to GDPR, >we MAY defer some aspects of the review which we did not believe >would substantially alter our completion target. In fact, we have >not deferred anything at this point and now believe that GDPR will >have a significant impact on our work. The full implementation of >GDPR may or may not be understood by the time we deliver our report, >but we will certainly understand the overall direction and that will >be a factor in our report. It is clear that the real impact will not >be well understood by then nor even a few months later, so the >analysis of that will have to wait for a subsequent review. > >= The document implies that because there are only ten RT members, >there are insufficient people to do the work. In fact there are just >ten members, but all are working together and the number of active >workers may well exceed the number of active workers on previous larger teams. > >= The PC document says that $460k will be saved in FY19 by >restricting the scope of the review and that $590k will be saved by >pausing the review. The review team has not been involved in >estimating any of these budgets and does not believe that they are accurate. > > [Financial Analysis here] > >= The public comment is due to close on 06 July 2018 with the staff >report due on 23 Jul7 2018. According to the current Review Team >work plan, the Review Team is scheduled to have a face to face >meeting 19-20 July 2018. Our intent is that we finalize the content >of our draft report at that time. Moreover, unlike some draft >reports which are comprised of many questions to the community, we >believe that this will really be a draft report looking for >community comment before finalizing it. It makes little sense for >the group to reduce its scope or completely pause just at the point >when it is ready to deliver its draft report. By that time, the bulk >of the work will have been done, and to scrap part of it or pause >for a year implies much of that work will have to largely be >repeated again later. The RT specifically notes that Option C, to >have the Review paused in April (a date that had long past when the >PC was issued) made no sense whatsoever given that the community >input to make that decision would only be available in late July. > >The Review Team believes that if it had been consulted when this >Public Comment was being contemplated and developed, the RDS-WHOIS2 >Review would never have been included. Moreover, the Review Team >strongly believes that if a RT is to be held accountable for keeping >to its "budget" (as is the current practice), the RT MUST be >involved in developing that overall budget and the annual FY budgets >that it must operationally adhere to.

1 0

Re: [RDS-WHOIS2-RT] [registration-issues-wg] The next battle is on the horizon - e-Privacy EU-style
by Carlton Samuels May 28, 2018

May 28, 2018

Yeah. Just like GDPR. The reference to the Atlantic hurricane was for those of us in my neck of the woods. We know its coming from it formed off West Africa, weeks before it hits. However, folks who live on the banks of rivers still get washed away. -Carlton On Mon, 28 May 2018, 8:18 am Michele Neylon - Blacknight, < michele(a)blacknight.com> wrote: > Hardly > > It was announced a very long time ago > > > > > > -- > > Mr Michele Neylon > > Blacknight Solutions > > Hosting, Colocation & Domains > > https://www.blacknight.com/ > > http://blacknight.blog/ > > Intl. +353 (0) 59 9183072 > > Direct Dial: +353 (0)59 9183090 > > Personal blog: https://michele.blog/ > > Some thoughts: https://ceo.hosting/ > > ------------------------------- > > Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty > > Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 > > > > *From: *registration-issues-wg < > registration-issues-wg-bounces(a)atlarge-lists.icann.org> on behalf of > Carlton Samuels <carlton.samuels(a)gmail.com> > *Date: *Monday 28 May 2018 at 14:14 > *To: *Charla Shambley via CCT-Review <cct-review(a)icann.org>, " > registration-issues-wg(a)atlarge-lists.icann.org" < > registration-issues-wg(a)atlarge-lists.icann.org>, RDS WHOIS2-RT List < > rds-whois2-rt(a)icann.org>, "lac-discuss-en(a)atlarge-lists.icann.org" < > lac-discuss-en(a)atlarge-lists.icann.org> > *Subject: *[registration-issues-wg] The next battle is on the horizon - > e-Privacy EU-style > > > > Um, well, this is another one that just sidled upon us, just like one of > them sneaky Atlantic hurricanes! > > > > https://nyti.ms/2sk7lP4 > > > > -Carlton > > > ============================== > *Carlton A Samuels* > > *Mobile: 876-818-1799 Strategy, Process, Governance, Assessment & > Turnaround* > ============================= >

1 0

Re: [RDS-WHOIS2-RT] [Zip Removed] Fwd: CONSUMER SUB-GROUP UPDATE
by Jean-Baptiste Deroulez May 28, 2018

May 28, 2018

Dear Erika, It seems there is an issue with your zip file (which was removed by the mail server), would it be possible to send your report in its original format (not **.zip). Many thanks in advance, Kind regards, Jean-Baptiste From: RDS-WHOIS2-RT <rds-whois2-rt-bounces(a)icann.org> on behalf of Erika Mann <erika(a)erikamann.com> Date: Monday, May 28, 2018 at 2:49 PM To: RDS WHOIS2-RT List <rds-whois2-rt(a)icann.org> Subject: [Zip Removed] [RDS-WHOIS2-RT] Fwd: CONSUMER SUB-GROUP UPDATE SENDING THIS EMAIL AGAIN BECAUSE APPARENTLY THE ATTACHMENT WAS MISSING! ---------- Forwarded message ---------- From: Erika Mann <erika(a)erikamann.com<mailto:erika@erikamann.com>> Date: Mon, May 28, 2018 at 12:52 PM Subject: CONSUMER SUB-GROUP UPDATE To: RDS WHOIS2-RT List <rds-whois2-rt(a)icann.org<mailto:rds-whois2-rt@icann.org>> Dear All - Sorry for the late submission. The attached version incorporates the discussion of 2nd F2F meeting in Brussels and further investigation of the reseller problematic. Apologies to my sub-group members for not having been able to consult with them. Thanks goes to Lisa for helping with the update! Thanks, Erika Erika Mann +32 498 121354

2 2

REMINDER: Meeting Change of Time
by Alan Greenberg May 27, 2018

May 27, 2018

A reminder that the RDS-WHOIS2-RT weekly meeting is now being held for 90 minutes on Mondays at 15:00 UTC, an hour later than previously. If you cannot attend, please send apologies ahead of time. Alan

1 0

Plenary #29 | 28 May | 15:00 UTC
by Jean-Baptiste Deroulez May 25, 2018

May 25, 2018

Dear Review Team Members, In preparation for your call #29<https://community.icann.org/x/MgMFBQ> scheduled for Monday 28 May 2018 – 15:00 – 16:30 UTC, please find below the meeting agenda: * Welcome, roll-call, SoI Updates * Short-Term Options to Adjust the Timeline for Specific Reviews * ICANN62 * Face-to-Face Meeting #3 – Brussels * Subgroups Status Update * A.O.B. * Confirm Decisions Reached and Action Items As per discussion on plenary call #28 and as no objections were raised, the plenary call start time has been moved to 15:00 UTC on Mondays. You should all have received dial-in details to join this call. If not, please contact us (off list) at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

1 0