August 2017 - RDS-WHOIS2-RT

RDS-WHOIS2 Review Team Plenary Call #2 13 July 2017 - 13:00 UTC
by Jean-Baptiste Deroulez Nov. 26, 2017

Nov. 26, 2017

Dear Review Team Members, In preparation for your call #02<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>, scheduled for Thursday, 13 July – 13:00-14:00 UTC (timezone converter here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=RDS%2FWHOIS2+Revi…>), please find below a suggested agenda: 1. Welcome and opening remarks (Karen Mulberry) 2. ICANN59 Recap (Jean-Baptiste Deroulez) 3. Review Team leadership structure, responsibilities (RDS-WHOIS2-RT members) 4. Plenary call schedule and topics (Karen Mulberry) 5. Consider process and how the Review Team wishes to include Observers (Karen Mulberry) 6. First face-to-face meeting: Dates & Topics (Karen Mulberry) 7. ICANN60 meeting (Karen Mulberry) 8. Board Resolution (RDS-WHOIS2-RT members) (Lisa Phifer) 9. A.O.B Attached to this email you will find slides we invite you to read. 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> and we will make sure to send you a copy. Please feel free to join 20 minutes early to confirm your Adobe Connect and audio connections, if you wish. We would also like to remind you with some key links for your information: * This mailing-list is being publicly archived at: http://mm.icann.org/pipermail/rds-whois2-rt/ * https://community.icann.org/display/WHO/RDS-WHOIS2+Review[community.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> is the URL to your work space, which we have started populating with information. It will be the main repository for your documents and activities. We would like to call your attention to the Background Materials page where we have started compiling documents we would encourage you to read: https://community.icann.org/display/WHO/Background+Materials[community.ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste Deroulez

11 19

Thursday's meeting
by Chris Disspain Aug. 30, 2017

Aug. 30, 2017

All, I expect to be an apology for this meeting. If things change I shall, of course, join the call. Cheers, Chris

1 0

Formation of the RDS-WHOIS2 Board Caucus Group
by Chris Disspain Aug. 29, 2017

Aug. 29, 2017

Greetings All, In line with best practice experience from the Transition-related work, the Board is using Caucus Groups as a mechanism for the Board to provide input to Specific Review Teams on the scope of work, feasibility of recommendations and other key matters. These Caucus Groups are small groups of Board members with expertise and interest in the particular Review-related topics. The goal is to create an interactive environment where the Board can engage with the Review Teams to offer input and observations for Review Teams’ consideration on a timely basis, via the Board Caucus Group. The Board Caucus Group for the RDS-WHOIS2 Review has been formed, and currently consists of Rinalia Abdul Rahim, Cherine Chalaby, Steve Crocker, Markus Kummer, Akinori Maemura, Kaveh Ranjbar and me. It is important to highlight that the formation of the Caucus Groups is the Board’s internal method of conducting their work. All of the final results are seen and reviewed by the full Board so any response or feedback provided to the Review Team by the Caucus Group is on behalf of the full Board. I hope this information is helpful and will be happy to answer any questions you may have. Cheers, Chris

1 0

Apologize for being absent of Plenary Call #6
by SUN Lili Aug. 29, 2017

Aug. 29, 2017

Dear all, I’m writing to apologize my absence for Plenary Call #6 on 31 August as it’s a travel day for me, than you for your understanding. Best regards, Lili SUN *************************************************************************************************** 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] Replacement and Removal of Members
by Alan Greenberg Aug. 28, 2017

Aug. 28, 2017

I will leave the discussion of removal until the meeting, since this seems to be an issue of general dispute in a variety of ways. On reappointing, under the previous rules in the AoC, it was the CEO and Chair of the GAC who made the original selections (from among those endorsed by the AC/SOs and applicants as experts. The AoC was silent on replacements But if a replacement was needed, it was done by the AC/SO that originally had endorsed the person that is leaving. Under the new Bylaws, it is the Chairs of the AC?SO that make the selections and I am proposing that we do not change the method of replacement. There is no precedent from the SSR, the only other review being conducted after the Bylaws, since the ToR is MUCH expanded from the version that they used. As such, it is up to us to make a recommendation and the Board can accept or reject it. I support a minimalist approach. Alan At 28/08/2017 12:44 PM, Carlton Samuels wrote: >I made a few emendations. See them inline. > >One is the matter of appointment, isn't it the >Board that appoints the RT member? If my >understanding is correct, then some changes I >propose shall apply. If not, then strike them. > >-Carlton > > >============================== >Carlton A Samuels >Mobile: <tel:(876)%20818-1799>876-818-1799 >Strategy, Planning, Governance, Assessment & Turnaround >============================= > >On Sat, Aug 26, 2017 at 9:51 PM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >I was asked to propose wording for the section >of the Terms of Reference on Replacement and Removal of Members > >I would like to propose the following wording for the consideration of the RT. > >Alan > >======= > >If a Review Team member is no longer able or >willing to serve, or if an SO/AC withdraws its >endorsement of the member, the SO/AC making the >original endorsement will be requested to >âmake a new endorsement for >the position >.â >. The SO/AC will make the selection according to their own >ârules and â >processes and >âshall > not be bound to consider only those candidates who originally applied >âand â >request >âed > their endorsement. > >If a Review Team member is >âdeemed by the evidence >â >sufficiently inactive or disruptive as to cause at least >â2/3rd > of Review Team members (excluding the member > in question) to request their removal, the member will be asked to >âwithdraw >. If the member fails to >âwithdraw >, the SO/AC that endorsed the member will be >requested to withdraw their endorsement >â and request the member resign. > Should the SO/AC not take action, the member can be >âexcluded from the Review Team > by a 2/3 >ârdâ >majority vote of the remaining Review Team >members. In all cases, the balloting will be >carried out in such a way as to not reveal how individual members voted. > > >_______________________________________________ >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 > > > >Virus-free. ><https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>www.avast.com >

1 0

Replacement and Removal of Members
by Alan Greenberg Aug. 28, 2017

Aug. 28, 2017

I was asked to propose wording for the section of the Terms of Reference on Replacement and Removal of Members I would like to propose the following wording for the consideration of the RT. Alan ======= If a Review Team member is no longer able or willing to serve, or if an SO/AC withdraws its endorsement of the member, the SO/AC making the original endorsement will be requested to refill the position with a replacement member. The SO/AC will make the selection according to their own processes and will not be bound to consider only those candidates who originally applied requesting their endorsement. If a Review Team member is sufficiently inactive or disruptive as to cause at least 50% of Review Team members (excluding the member in question) to request their removal, the member will be asked to resign. If the member fails to resign, the SO/AC that endorsed the member will be requested to withdraw their endorsement and replace the member. Should the SO/AC not take action, the member can be removed by a 2/3 majority vote of the remaining Review Team members. In all cases, the balloting will be carried out in such a way as to not reveal how individual members voted.

6 7

Re: [RDS-WHOIS2-RT] Replacement and Removal of Members
by Alan Greenberg Aug. 28, 2017

Aug. 28, 2017

Hi Erika, To be clear, are you suggesting that we have a higher threshold (70%) to ask an AC/SO to remove their member that we need to do the removal ourselves (presuming we keep the latter power)?? No problem with New vs Replacement. Alan At 27/08/2017 07:36 AM, Erika Mann wrote: >Thank you Alan! > >Two recommendations (see in yellow below) , but I'm supporting the >current text as well if most members are okay with your text. > >Kind regards, >Erika > > >If a Review Team member is no longer able or willing to serve, or if >an SO/AC withdraws its endorsement of the member, the SO/AC making >the original endorsement will be requested to refill the position >with a new (delete = replacement) member. The SO/AC will make the >selection according to their own processes and will not be bound to >consider only those candidates who originally applied requesting >their endorsement. > >If a Review Team member is sufficiently inactive or disruptive as to >cause (delete = at leas) (50%) 70% of Review Team members (excluding >the member in question) to request their removal, the member will be >asked to resign. If the member fails to resign, the SO/AC that >endorsed the member will be requested to withdraw their endorsement >and replace the member. Should the SO/AC not take action, the member >can be removed by a 2/3 majority vote of the remaining Review Team >members. In all cases, the balloting will be carried out in such a >way as to not reveal how individual members voted. > >On Sun, Aug 27, 2017 at 4:51 AM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >I was asked to propose wording for the section of the Terms of >Reference on Replacement and Removal of Members >I would like to propose the following wording for the consideration of the RT. >Alan >======= >If a Review Team member is no longer able or willing to serve, or if >an SO/AC withdraws its endorsement of the member, the SO/AC making >the original endorsement will be requested to refill the position >with a replacement member. The SO/AC will make the selection >according to their own processes and will not be bound to consider >only those candidates who originally applied requesting their endorsement. >If a Review Team member is sufficiently inactive or disruptive as to >cause at least 50% of Review Team members (excluding the member in >question) to request their removal, the member will be asked to >resign. If the member fails to resign, the SO/AC that endorsed the >member will be requested to withdraw their endorsement and replace >the member. Should the SO/AC not take action, the member can be >removed by a 2/3 majority vote of the remaining Review Team members. >In all cases, the balloting will be carried out in such a way as to >not reveal how individual members voted. >_______________________________________________ >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

1 0

Reminders
by Alan Greenberg Aug. 25, 2017

Aug. 25, 2017

Please note that if you have additional thoughts on the scope for our work, please send them to this list well in advance of next week's meeting. Also note that if you have questions for the Subject Matter Experts (SMEs) with respect to the implementation of the recommendations from the first WHOIS Review, please send them in by the end of the month if at all possible. You can find the Summary and Detailed Implementation Reports under item 4 on our Background Materials page (https://community.icann.org/display/WHO/Background+Materials) Alan

1 0

Latest WHOIS Roadmap June2017
by Karen Mulberry Aug. 21, 2017

Aug. 21, 2017

Attached is the latest WHOIS Roadmap that summarizes activities as of June 2017. I thought this might be of interest to the Review Team. Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745

1 0

Scope discussion
by Alan Greenberg Aug. 17, 2017

Aug. 17, 2017

In preparation for our discussion on Scope tomorrow, I have tried to collect all of the issues raised to date in a simple list. If I have missed something, I do apologize, and please raise it tomorrow. The list includes: - Origin of issue and reference to where there may be further information. The two sources so far are the ICANN Bylaws and the document that Karen distributed summarizing earlier e-mails. - A very brief description. - My take on whether it is something we could address - The final decision of the group as to whether to include it or not. (currently all blank) I have also outlined the start of what I think are reasonable principles to guide our work. Alan

3 2