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

Re: [RDS-WHOIS2-RT] Plenary #28 | 21 May | 14:00 UTC
by Jean-Baptiste Deroulez May 22, 2018

May 22, 2018

Dear Review Team Members, Attached to this email you will find your meeting report for plenary call #28<https://community.icann.org/x/HAMFBQ>, including identified decisions reached and action items for your review. Archives are available at: https://community.icann.org/x/HAMFBQ. Kind regards, Jean-Baptiste From: RDS-WHOIS2-RT <rds-whois2-rt-bounces(a)icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org> Date: Friday, May 18, 2018 at 8:25 PM To: "rds-whois2-rt(a)icann.org" <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] Plenary #28 | 21 May | 14:00 UTC Dear Review Team Members, In preparation for your call #28 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>, scheduled for Monday 21 May 2018 – 14:00 – 15:30 UTC, please find below the meeting agenda: * Welcome, roll-call, SoI Updates * Short-Term Options to Adjust the Timeline for Specific Reviews * Plenary Call Time * ICANN62 * Face-to-Face Meeting #3 – Brussels | (please fill in the new poll with supplementary dates: https://doodle.com/poll/r762twzaxbw4knuk [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_r762tw…> ) * Subgroups Status Update * A.O.B. * Confirm Decisions Reached and Action Items 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

GoDaddy on In tended State of Play May 25
by Carlton Samuels May 22, 2018

May 22, 2018

..says it will not make all of its WHOIS records 'dark' come Friday. https://domainnamewire.com/2018/05/22/godaddy-will-continue-publishing-most… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

1 0

BY 23:59 UTC - Thursday - Final input on Brussels meeting notes & report
by Alice Jansen May 22, 2018

May 22, 2018

Dear Review Team Members, As agreed on call #28, Thursday – 23:59 UTC, is the final deadline to raise any concerns you may have with the Brussels list of agreements/actions reached and associated meeting report. To date we have received comments from Stephanie on the list of agreements/actions. The documents can be found in the attached. Thanks, Best regards Alice

1 0

FINAL CALL: Plenary Meetings on Mondays @15:00 UTC
by Jean-Baptiste Deroulez May 22, 2018

May 22, 2018

Dear Review Team members, As per discussion on plenary call #28<https://community.icann.org/x/HAMFBQ>, review team members in attendance discussed the possibility to move the plenary call start time to 15:00 UTC on Mondays, and no objections were raised. Unless we hear any objections in reply to this email by Thursday 24 May 23:59 UTC , the plenary meetings will be switched to Mondays @15:00 UTC (90 mins). Kind regards, Jean-Baptiste

1 0

REMINDER: INPUT NEEDED by tomorrow - New Doodle Poll
by Alice Jansen May 21, 2018

May 21, 2018

Dear Review Team Members, This is to kindly remind you to complete the doodle poll https://doodle.com/poll/r762twzaxbw4knuk. Input needed by tomorrow – 23:59 UTC. Thanks Best regards Alice From: Alice Jansen <alice.jansen(a)icann.org> Date: Friday 18 May 2018 at 09:37 To: RDS-WHOIS2-RT <rds-whois2-rt(a)icann.org> Subject: INPUT NEEDED - New Doodle Poll Dear Review Team Members, As requested by the RDS-WHOIS2 leadership, we have suggested supplementary dates for the face-to-face meeting #3 that will be held at the ICANN office in Brussels, Belgium. At your earliest convenience, please complete this new poll https://doodle.com/poll/r762twzaxbw4knuk using the following color code: Green - I can make it in person (1 click) Yellow - I can join remotely (2 clicks) Red – I am not available (0 click) We look forward to reading your input. Thanks, Kind regards Alice

1 0

Plenary #28 | 21 May | 14:00 UTC
by Jean-Baptiste Deroulez May 21, 2018

May 21, 2018

Dear Review Team Members, In preparation for your call #28<https://community.icann.org/x/HAMFBQ>, scheduled for Monday 21 May 2018 – 14:00 – 15:30 UTC, please find below the meeting agenda: * Welcome, roll-call, SoI Updates * Short-Term Options to Adjust the Timeline for Specific Reviews * Plenary Call Time * ICANN62 * Face-to-Face Meeting #3 – Brussels | (please fill in the new poll with supplementary dates: https://doodle.com/poll/r762twzaxbw4knuk ) * Subgroups Status Update * A.O.B. * Confirm Decisions Reached and Action Items 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

4 3

The NTIA Weighs in on GDPR..Again
by Carlton Samuels May 18, 2018

May 18, 2018

Seems Uncle Sam is preparing for what looks like the inevitable. For GDPR-specific remarks go down to heading "International Regulations". https://www.ntia.doc.gov/speechtestimony/2018/remarks-assistant-secretary-r… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

1 0

INPUT NEEDED - New Doodle Poll
by Alice Jansen May 18, 2018

May 18, 2018

Dear Review Team Members, As requested by the RDS-WHOIS2 leadership, we have suggested supplementary dates for the face-to-face meeting #3 that will be held at the ICANN office in Brussels, Belgium. At your earliest convenience, please complete this new poll https://doodle.com/poll/r762twzaxbw4knuk using the following color code: Green - I can make it in person (1 click) Yellow - I can join remotely (2 clicks) Red – I am not available (0 click) We look forward to reading your input. Thanks, Kind regards Alice

1 0

ICANN Proposal to adjust scope of RDS-WHOIS2-RT
by Alan Greenberg May 18, 2018

May 18, 2018

I call your attention to a Public Comment (PC) launched yesterday asking for input on alternatives to alter the RDS-WHOIS2-RT Scope and plans (as well possible changes to the not yet started ATRT3) - https://www.icann.org/public-comments/specific-reviews-short-term-timeline-…. I proposes three possible scenarios for our RT: a) Proceeds as planned; b) reduce scope to just an analysis of the WHOIS1-RT Recommendations; c) pause the review entirely for some as yet to be determined time. If recommended by the community, b) and c) would require our agreement. The implications of a community recommendation that we refused to agree with are not known. If there is a pause, it is not clear when the unpause would happen and to what extent it would be the same team moving forward. The PC ends on 06 July 2018 and the report on input received is due on 23 July 2018, a few days before we are currently planning to meet in Brussels to close-to-finalize our report. Although the PC was issues yesterday, neither I nor Susan and Cathrin had any prior knowledge of it and in fact we only heard of it today. We have initiated discussions with MSSI on exactly what this means and will get back when I have a better understanding. Alan

9 13

Re: [RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT
by Alan Greenberg May 17, 2018

May 17, 2018

I don't think it is a Bylaws problem because they do add that we have to agree. Although I suspect we would agree, although with a lot of bad feelings, but I did ask Larisa what wuld happen if we did NOT agree. Would we still have funding and support to continue? And she said they had not thought about that... I agree that this is a diversion that we could have done without and it will take resources, at least at the leadership level. Alan At 17/05/2018 09:09 AM, Cathrin.BAUER-BULST(a)ec.europa.eu wrote: >I think this raises a bylaws point. This is a >review mandated by the Bylaws, which even set a >time frame for its regular occurrence. Now >putting it up for Community discussion whether >we're having this review, whether it should >change its scope or whether it should stop for a >while, essentially puts the bylaws requirement >up for Community discussion. We as individuals >may serve "at the pleasure of the community" but >the process itself is not at the disposal of any >public consultation, so I believe this whole >exercise is legally on not very sound footing. > >And this idea that we then agree or disagree >with the outcome of the public consultation >seems courageous to me, in the "Yes Minister" >sense so what is the point off the exercise if >we then just get to ignore the Community view if >we so please? To help us make an informed >decision on options that we never thought of >ourselves or were invited to have a say in in >the first place but that someone has >benevolently designed in an effort to reduce our >workload? I think we should participate in the >webinar (we may be the only ones given that >other RDS/WHOIS mess) and explain this. > >But I should be working on surveys instead of >commenting on this mess that much for workload reduction. > >Best regards >Cathrin > > > >From: RDS-WHOIS2-RT >[mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of Dmitry Belyavsky >Sent: Thursday, May 17, 2018 11:25 AM >To: Alan Greenberg >Cc: RDS WHOIS2-RT List >Subject: Re: [RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT > >Dear Alan, > >I think we should continue our work as planned. > >I agree with Chris that the RT should respond to >the call to the comments ASAP. > >On Wed, May 16, 2018 at 8:54 PM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >I presume then that you and others are willing >to keep working and meet our deadline of a draft >report at or soon after the July F2F. > >Alan > > >At 16/05/2018 10:23 AM, Volker Greimann wrote: > > >Hi Alan, > >I absolutely agree that it is strange that ICANN >seems to want to pause this without consulting >us first. But as this is the cards we have been >dealt, we need to figure out how to play them >and in this case I vote for following the community consensus, if any. > >As for Monday, it is a public holiday that I will be travelling on. > >Best, > >Volker > >Am 16.05.2018 um 16:08 schrieb Alan Greenberg: > >Volker, > >Of course we serve at the pleasure of the community. > >The question is process and timing. That this >was done with no consultation with us, I find >strange. But the really difficult part is that >we are being told to keep on working (and I have >confirmed that this is the intent) with a target >of having a draft report complete just after the >July F2F, and at THAT point, we may be told to >scrap part of what we have been working on >between now an then, or put the entire project >on hold for some indeterminate time, and when it >resumes it may be with a different team and much >of the work will have to be redone. > >We will discuss this further at the Monday >meeting, and for those who will not be there, >your input is appreciated ahead of time. > >Susan has suggested that we go back to our appointing groups for their input. > >Alan > > > > >At 16/05/2018 06:03 AM, Volker Greimann wrote: > > > > > >We serve at the pleasure of > >the community, so I would not object to any > >consensus position either way. While a) is the most logical choice, > >preserving most of our work efforts so far, the others also have some > >merit due to the changes ahead. And as ICANN has just thrown another > >curve-ball in the form of the proposed temporary specification, more > >change seems to be on the horizon, which could further outdate our work > >product. > > > >Best, > > > >Volker > > > > > >Am 16.05.2018 um 04:30 schrieb Alan Greenberg: > > > I call your attention to a Public Comment (PC) launched yesterday > > > asking for input on alternatives to alter the RDS-WHOIS2-RT Scope > >and > > > plans (as well possible changes to the not yet started ATRT3) - > > > > > > > > ><https://www.icann.org/public-comments/specific-reviews-short-term-timeline-…>https://www.icann.org/public-comments/specific-reviews-short-term-timeline-… > ><https://www.icann.org/public-comments/specific-reviews-short-term-timeline-…>. > > > > > > I proposes three possible scenarios for our RT: > > > > > > a) Proceeds as planned; > > > > > > b) reduce scope to just an analysis of the WHOIS1-RT > >Recommendations; > > > > > > c) pause the review entirely for some as yet to be determined time. > > > > > > If recommended by the community, b) and c) would require our > > > agreement. The implications of a community recommendation that we > > > refused to agree with are not known. If there is a pause, it is not > > > clear when the unpause would happen and to what extent it would be > >the > > > same team moving forward. > > > > > > The PC ends on 06 July 2018 and the report on input received is due > >on > > > 23 July 2018, a few days before we are currently planning to meet in > > > Brussels to close-to-finalize our report. > > > > > > Although the PC was issues yesterday, neither I nor Susan and > >Cathrin > > > had any prior knowledge of it and in fact we only heard of it > >today. > > > > > > We have initiated discussions with MSSI on exactly what this means > >and > > > will get back when I have a better understanding. > > > > > > Alan > > > > > > _______________________________________________ > > > RDS-WHOIS2-RT mailing list > > > > > > ><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>RDS-WHOIS2-RT >at icann.org > > > > > > > > >https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > > >-- > >Bei weiteren Fragen stehen wir Ihnen gerne zur VerfÃ¼gung. > > > >Mit freundlichen GrÃ¼Ãen, > > > >Volker A. Greimann > >- Rechtsabteilung - > > > >Key-Systems GmbH > >Im Oberen Werk 1 > >66386 St. Ingbert > >Tel.: +49 (0) 6894 - 9396 901 > >Fax.: +49 (0) 6894 - 9396 851 > >Email: > ><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>vgreimann > ><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>at key-systems.net > > > >Web: > > > > > ><http://www.key-systems.net/>www.key-systems.net / > >www.RRPproxy.net > > > > > ><http://www.domaindiscount24.com/>www.domaindiscount24.com / > > > > > >www.BrandShelter.com > > > >Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: > > > > > ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems > > > > > >www.twitter.com/key_systems > > > >GeschÃ¤ftsfÃ¼hrer: Alexander Siffrin > >Handelsregister Nr.: HR B 18835 - Saarbruecken > >Umsatzsteuer ID.: DE211006534 > > > >Member of the KEYDRIVE GROUP > ><http://www.keydrive.lu/>www.keydrive.lu > > > >Der Inhalt dieser Nachricht ist vertraulich und nur fÃ¼r den angegebenen > >EmpfÃ¤nger bestimmt. Jede Form der Kenntnisgabe, VerÃ¶ffentlichung oder >Weitergabe an Dritte durch den EmpfÃ¤nger ist unzulÃ¤ssig. Sollte diese > >Nachricht nicht fÃ¼r Sie bestimmt sein, so bitten wir Sie, sich mit uns > >per E-Mail oder telefonisch in Verbindung zu setzen. > > > >-------------------------------------------- > > > >Should you have any further questions, please do not hesitate to contact > >us. > > > >Best regards, > > > >Volker A. Greimann > >- legal department - > > > >Key-Systems GmbH > >Im Oberen Werk 1 > >66386 St. Ingbert > >Tel.: +49 (0) 6894 - 9396 901 > >Fax.: +49 (0) 6894 - 9396 851 > >Email: > ><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>vgreimann > ><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>at key-systems.net > > > >Web: > > > > > ><http://www.key-systems.net/>www.key-systems.net / > >www.RRPproxy.net > > > > > ><http://www.domaindiscount24.com/>www.domaindiscount24.com / > > > > > >www.BrandShelter.com > > > >Follow us on Twitter or join our fan community on Facebook and stay > >updated: > > > > > ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems > > > > > >www.twitter.com/key_systems > > > >CEO: Alexander Siffrin > >Registration No.: HR B 18835 - Saarbruecken > >V.A.T. ID.: DE211006534 > > > >Member of the KEYDRIVE GROUP > ><http://www.keydrive.lu/>www.keydrive.lu > > > >This e-mail and its attachments is intended only for the person to whom > >it is addressed. Furthermore it is not permitted to publish any content > >of this email. You must not use, disclose, copy, print or rely on this > >e-mail. If an addressing or transmission error has misdirected this > >e-mail, kindly notify the author by replying to this e-mail or > >contacting > >us by telephone. > > >-- > >Bei weiteren Fragen stehen wir Ihnen gerne zur VerfÃ¼gung. > > > >Mit freundlichen GrÃ¼Ãen, > > > >Volker A. Greimann > >- Rechtsabteilung - > > > >Key-Systems GmbH > >Im Oberen Werk 1 > >66386 St. Ingbert > >Tel.: +49 (0) 6894 - 9396 901 > >Fax.: +49 (0) 6894 - 9396 851 > >Email: > ><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > > > >Web: <http://www.key-systems.net>www.key-systems.net / > >www.RRPproxy.net > ><http://www.domaindiscount24.com>www.domaindiscount24.com / > > > >www.BrandShelter.com > > > >Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: > > > ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems > > > >www.twitter.com/key_systems > > > >GeschÃ¤ftsfÃ¼hrer: Alexander Siffrin > >Handelsregister Nr.: HR B 18835 - Saarbruecken > >Umsatzsteuer ID.: DE211006534 > > > >Member of the KEYDRIVE GROUP > ><http://www.keydrive.lu>www.keydrive.lu > > > >Der Inhalt dieser Nachricht ist vertraulich und nur fÃ¼r den angegebenen > >EmpfÃ¤nger bestimmt. Jede Form der Kenntnisgabe, VerÃ¶ffentlichung oder > >Weitergabe an Dritte durch den EmpfÃ¤nger ist unzulÃ¤ssig. Sollte diese > >Nachricht nicht fÃ¼r Sie bestimmt sein, so bitten wir Sie, sich mit uns > >per E-Mail oder telefonisch in Verbindung zu setzen. > > > >-------------------------------------------- > > > >Should you have any further questions, please do not hesitate to contact > >us. > > > >Best regards, > > > >Volker A. Greimann > >- legal department - > > > >Key-Systems GmbH > >Im Oberen Werk 1 > >66386 St. Ingbert > >Tel.: +49 (0) 6894 - 9396 901 > >Fax.: +49 (0) 6894 - 9396 851 > >Email: > ><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > > > >Web: <http://www.key-systems.net>www.key-systems.net / > >www.RRPproxy.net > ><http://www.domaindiscount24.com>www.domaindiscount24.com / > > > >www.BrandShelter.com > > > >Follow us on Twitter or join our fan community on Facebook and stay > >updated: > > > ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems > > > >www.twitter.com/key_systems > > > >CEO: Alexander Siffrin > >Registration No.: HR B 18835 - Saarbruecken > >V.A.T. ID.: DE211006534 > > >Member of the KEYDRIVE GROUP > ><http://www.keydrive.lu>www.keydrive.lu > > > >This e-mail and its attachments is intended only for the person to whom > >it is addressed. Furthermore it is not permitted to publish any content > >of this email. You must not use, disclose, copy, print or rely on this > >e-mail. If an addressing or transmission error has misdirected this > >e-mail, kindly notify the author by replying to this e-mail or contacting > >us by telephone. > > > > > > > >_______________________________________________RDS-WHOIS2-RT mailing list ><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > > >-- >SY, Dmitry Belyavsky

1 0