<html>
<body>
Before I could contact Katrina, she has sent this message. Since we have
no specific skill we are looking for at the moment, we can presume the
ccNSO will not name anyone to the RT, and I have informed
Katrina.<br><br>
Alan<br><br>
<blockquote type=cite class=cite cite="">From: Katrina Sataki
<katrina@nic.lv><br>
To: 'Alan Greenberg' <alan.greenberg@mcgill.ca><br>
Subject: RDS and ccNSO<br>
Date: Fri, 19 Jan 2018 18:48:31 +0200<br>
<br>
Dear Alan,<br>
<br>
As I noticed, one of the action items is for you to contact me.<br>
Yesterday we had a Council call and I was actually planning to contact
you :-)<br>
<br>
So, the Council discussed our participation in the RDS/WHOIS2 review. The
Council considered the following aspects:<br>
- In its letter to the ICANN
BoD the ccNSO voiced concerns and identified the issues (scope of the
review, GDPR),<br>
- The review team has been
working hard and finalises the ToR – it would be the last moment to
deecide whether the ccNSO wishes to appoint any members to the RT,<br>
- The ccNSO Council could
contact volunteers who seeked endorsement from the ccNSO and see if they
are still interested to participate or we could also run a new call
within the community. The second option would significanlty prolong the
decision and might cause dissatisfaction among the current members of the
RT,<br>
- The ccNSO Council was happy
to note that the the WHOIS2 review moves forward and unlike SSR2 and
ATRT3 does not face problems (mainly thanks to the experienced
leadership, I think).<br>
<br>
I am getting to the point - the Council is leaning towards the opinion
that there is no need to appoint any new members because as it seems the
RT is doing great. So, unless you tell me that you need people with some
specific skillset and the easiest way would be that the ccNSO looks for
some great candidates and proposes them, we will not cause the RT any
disturbance. We would be more than happy to save our volunteers for other
jobs but if you need “new (specific) blood” we will do our best.<br>
<br>
Kind regards,<br>
<br>
]{atrina<br>
<br>
<br>
<br>
<br>
<b>From:</b> RDS-WHOIS2-RT
[<a href="mailto:rds-whois2-rt-bounces@icann.org" eudora="autourl">
mailto:rds-whois2-rt-bounces@icann.org</a>] <b>On Behalf Of
</b>Jean-Baptiste Deroulez<br>
<b>Sent:</b> Friday, January 19, 2018 6:23 PM<br>
<b>To:</b> rds-whois2-rt@icann.org<br>
<b>Subject:</b> Re: [RDS-WHOIS2-RT] AGENDA - Call # 16 - 19 Jan @ 13:30
UTC<br>
<br>
Dear Review Team members,<br>
<br>
Following today’s plenary call, please find below the identified action
items and decisions reached:<br>
<br>
<b>DECISIONS REACHED:</b>
<ul>
<li>Plenary call on 22 January is cancelled.
<li>Compliance subgroup call scheduled on Monday at 14:30 UTC.
</ul> <br>
<b>ACTION ITEMS:<br>
</b> <br>
1) <b>Terms of Reference</b>
<ul>
<li>Alan in conjunction with leadership team to make minor tweaks to
Terms of Reference to reflect the discussion on plenary call.
<li>Alan to contact Katrina Sataki.
</ul> <br>
3) <b>Subgroups Status and Next Steps</b>
<ul>
<li><u>Law Enforcement Needs</u>: Thomas to share latest version of first
past planning doc to the subteam mailing list. ICANN org to post it on
the wiki.
<li><u>Anything New</u>: Stephanie to review background materials and
discuss with subgroup to fill in first pass planning doc.
</ul><b> <br>
</b>5) <b>Request for Written Implementation Briefings</b>
<ul>
<li>ICANN org to provide an estimated delivery date.
</ul> <br>
Kind regards,<br>
<br>
Jean-Baptiste<br>
<br>
<b>From: </b>RDS-WHOIS2-RT
<<a href="mailto:rds-whois2-rt-bounces@icann.org">
rds-whois2-rt-bounces@icann.org</a>> on behalf of Jean-Baptiste
Deroulez
<<a href="mailto:jean-baptiste.deroulez@icann.org">
jean-baptiste.deroulez@icann.org</a>><br>
<b>Date: </b>Friday, January 19, 2018 at 11:59 AM<br>
<b>To: </b>Alice Jansen
<<a href="mailto:alice.jansen@icann.org">alice.jansen@icann.org</a>
>,
"<a href="mailto:rds-whois2-rt@icann.org">rds-whois2-rt@icann.org</a>
"
<<a href="mailto:rds-whois2-rt@icann.org">rds-whois2-rt@icann.org</a>
><br>
<b>Subject: </b>Re: [RDS-WHOIS2-RT] AGENDA - Call # 16 - 19 Jan @ 13:30
UTC<br>
<br>
Dear Review Team Members,<br>
<br>
In preparation for today’s plenary call, please find attached the
slides and latest versions of the work plan and subgroups matrix. <br>
<br>
Kind regards,<br>
<br>
Jean-Baptiste<br>
<br>
<b>From: </b>RDS-WHOIS2-RT
<<a href="mailto:rds-whois2-rt-bounces@icann.org">
rds-whois2-rt-bounces@icann.org</a>> on behalf of Alice Jansen
<<a href="mailto:alice.jansen@icann.org">alice.jansen@icann.org</a>
><br>
<b>Date: </b>Thursday, January 18, 2018 at 11:34 AM<br>
<b>To:
</b>"<a href="mailto:rds-whois2-rt@icann.org">
rds-whois2-rt@icann.org</a>"
<<a href="mailto:rds-whois2-rt@icann.org">rds-whois2-rt@icann.org</a>
><br>
<b>Subject: </b>[RDS-WHOIS2-RT] AGENDA - Call # 16 - 19 Jan @ 13:30
UTC<br>
<br>
Dear Review Team Members,<br>
<br>
In preparation for your call #16, scheduled for tomorrow, Friday, 19
January 2018 – 13:30-15:00 UTC
(<<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.timeanddate.com_worldclock_fixedtime.html-3Fmsg-3DRDS-2DWHOIS2-2BReview-2BTeam-2BMeeting-26iso-3D20180119T1330-26p1-3D1440-26ah-3D1-26am-3D30&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=bjF1m7pvz_Pq9YGwLCvdfR1NTU-WoJot9gEK2iQ2sgE&s=QLFyG461Nhg0lUcVxLwPtMaCu8yUzlwd0pJEjSfLYBU&e=">
time zone converter[timeanddate.com]</a>), please find below the
suggested meeting agenda:<br>
---<br>
<i>1. Welcome, roll-call, SoI updates <br>
<br>
2. Terms of reference & work plan<br>
<u>Note</u>: You are invite to review the updated work plan (see yellow
highlights) in preparation for the call. The revised work plan will be
sent in a separate email prior to the call. <br>
<br>
3. Subgroup status update & next steps <br>
<u>Note</u>: As requested, we have inserted the link to the work plan
wiki page into each subgroup document. Please refer to your dedicated
wiki page for the most recent version of your planning document.
Information will be sent to your subgroup mailing-list shortly.
<br>
<br>
4. Request for written WHOIS1 implementation briefings<br>
<br>
5. Planning for 22 January meeting<br>
</i> <br>
<i>6. A.O.B.</i> <br>
---<br>
You should all have received dial-in details to join this call. If not,
please contact us (off list) at rds-whois2-staff at icann.org. <br>
<br>
As always, feel free to contact us should you have any questions or
concerns.<br>
<br>
Kind regards,<br>
Alice<br>
<br>
<br>
Content-Type: text/plain;<br>
<x-tab> </x-tab>
name="Untitled attachment 00965.txt"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: attachment;<br>
<x-tab> </x-tab>
filename="Untitled attachment 00965.txt"<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;YQXPR0101MB1589;27:oUpOso5cJx0f9f3RbbPefEWmtl8AR3WISjfHD6weUbaXN/jh81LLBC89IxIxXj71nQBuAO+rUJH1jrIbh5zrmW+J5mEfndB71z1LMAshP8I6W2hA/CXUYJpr3PNjOX2L<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
2ckAtq7l198SSQA8B4vEHnxNUdlRCA1q/zAWeVO7IX6svdxgDWUg/CnMho9uV1Ed5krZiRsr0kkFfLl8I75zcyA5dLDHvJ26t3ySezCLXiLGx5hxSF/C1q0BZSFeeGIC/gUkHhEo4tWeCd/PTi8UmQ==<br>
</blockquote></body>
</html>