Dear All,
Thanks for the prompt feedback!
Some clarifications:
1) The initial plan was to send the RZERC guideline to the Council a week before our next call and adopt it during the call (and issue a call for volunteers right after that). Can we proceed with the initial plan or you’d prefer to adopt the guideline earlier?
2) This time we do not need to coordinate our selection (nor the full slate) with anyone. Therefore there will be no need for the Selection Committee.
Kind regards,
]{atrina
From: owner-ccnso-council@icann.org [mailto:owner-ccnso-council@
icann.org ] On Behalf Of Ching Chiao
Sent: Thursday, August 04, 2016 5:39 AM
To: Burr, Becky <Becky.Burr@neustar.biz>
Cc: Katrina Sataki <katrina@nic.lv>; ccnso-council@icann.org
Subject: Re: [ccnso-council] FW: Request for Appointment of Representatives to the Root Zone Evolution Review Committee
Agree with Becky.
For formal appointment -- we can utilize the Selection Committee set for CSC as we have not really disband the group.
On Thu, Aug 4, 2016 at 9:53 AM, Burr, Becky <Becky.Burr@neustar.biz> wrote:
I am ok with appointing an interim rep so long as we get the appointment guideline out pretty quickly
J. Beckwith Burr
Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer
1775 Pennsylvania Avenue NW, Washington D.C. 20006
Office: +1.202.533.2932 Mobile: +1.202.352.6367 / neustar.biz
From: Katrina Sataki <katrina@nic.lv>
Date: Wednesday, August 3, 2016 at 1:58 PM
To: "'ccnso-council@icann. org'" <ccnso-council@icann.org>
Subject: [ccnso-council] FW: Request for Appointment of Representatives to the Root Zone Evolution Review Committee
Dear Councillors,
ICANN has issued a request to appoint a representative to the Root Zone Evolution Review Committee (see attachment). As you may remember, in Helsinki when we asked Trang when we need to have our representative for the RZERC she mentioned 30 September. So we relaxed a little, decided to wait for the updated RZERC charter and worked on other more urgent guidelines.
However, in this request you can see that they expect us to appoint our representative by 12 August. This comes totally unexpected. Although the guideline for appointing our representative to the RZERC is almost finished (all we need is to tweak the requirements according to the updated RZERC charter which is not published yet) we won’t be able to find a suitable candidate by 12 August because we need to issue a call for volunteers, weight all the candidates, etc.
How could this happen? It turned out that “The 30 September 2016 date is the date the IANA Functions Contract expires” and "NTIA has asked that ICANN provide an implementation report to NTIA on 12 August and specify what has been completed, and what is left to be done. Based on this report, NTIA will make a determination on whether to extend the contract. Although NTIA understands that all implementation tasks will not be completed by 12 August, it has communicated to ICANN that the more that can be completed by 12 August the better because any items that are not completed would raise questions regarding whether it could be completed in time for the transition.” For this reason, ICANN are asking that the appointing organizations submit their appointments by 12 August. A very unfortunate misunderstanding but there’s nothing we can change now.
There is no way we can run a proper procedure to find the best candidate within such a short timeframe. One of the options discussed by the Guidelines Review Committee to deal with the situation is to appoint an interim representative. It should be noted that there are no term limits for RZERC members and we may choose to replace the appointee at any time, e.g., on 30 September.
This means that we need to agree on an interim representative. As this will be a temporary assignment, it would be good if we could appoint somebody from the Council (if nobody steps forward I will take the blame). Even though there are specific requirements for this position (see below) I doubt anyone will be able to detect the imposter by the end of September:
¤ Must possess general technical knowledge of the DNS in order to consider issues that are brought to the Committee, and to follow/participate/contribute to discussions
¤ Ability to coordinate and consult with their respective organizations and communities to communicate issue under consideration and bring relevant expertise to the Committee
¤ Able to work and communicate in written and spoken English
¤ Effective communication skills.
What do you think? Any other proposals? Thanks!
Kind regards,
]{atrina
From: Trang Nguyen <trang.nguyen@icann.org>
Date: Tuesday 2 August 2016 09:58
To: Jari Arkko <jari.arkko@piuha.net>, "pdiaz@pir.org" <pdiaz@pir.org>, "patrik@frobbit.se" <patrik@frobbit.se>, "oscar@lacnic.net" <oscar@lacnic.net>, Katrina Sataki <katrina@nic.lv>, "tsinha@umd.edu" <tsinha@umd.edu>, "bverd@verisign.com" <bverd@verisign.com>, "dwessels@verisign.com" <dwessels@verisign.com>
Cc: Lise Fuhr <Fuhr@etno.eu>, Jonathan Robinson <jrobinson@afilias.info>, "jbladel@godaddy.com" <jbladel@godaddy.com>, "alan.greenberg@mcgill.ca" <alan.greenberg@mcgill.ca>, David Olive <david.olive@icann.org>, Yuko Green <yuko.green@icann.org>
Subject: Request for Appointment of Representatives to the Root Zone Evolution Review Committee
Dear Chairs, Co-Chairs and Mr. Wessels,
Please see attached a request from ICANN for appointment of representatives to the Root Zone Evolution Review Committee (RZERC).
Warm regards,
Trang Nguyen
Senior Director, Strategic Programs
ICANN
--
Ching Chiao
Founder and CEO
中域国际集团
+886.918.211372 || +86.135.20187032
Beijing . Chengdu . Hangzhou . Hong Kong . Shenzhen. Taipei