<html>
<body>
I have now reviewed the transcript.<br><br>
I'm not sure this will be considered to be "criteria", but it
does set forward what the expectations are for RZERC Members. The RZERC
is composed of people from a number of very diverse communities and they
are there to ensure that THEIR aspect of the RZ is addressed in any
changes. Although all of the members are expected to have an strong
overall of the RZ, they will each bring their particular expertise into
the group.<br><br>
<blockquote type=cite class=cite cite="">The RZERC is the group that will
be reviewing and recommending the architecture and operational systems
for the the DNS Root Zone as it evolves, ensuring the integrity, security
and stability of the root zone. <br><br>
Appointees to the RZERC must have a strong overall understanding of the
RZ, and must be able fully represent their appointing organization's
particular interest in the root zone.</blockquote><br><br>
Alan<br><br>
<br>
At 15/07/2016 10:31 AM, Trang Nguyen wrote:<br>
<blockquote type=cite class=cite cite="">Hi Alan,<br><br>
Do you have any suggestions for reframing the first two
criteria?<br><br>
Regards,<br><br>
Trang<br><br>
From:
<<a href="mailto:iotf-bounces@icann.org">iotf-bounces@icann.org</a>
> on behalf of Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
><br>
Date: Thursday, July 14, 2016 at 7:35 PM<br>
To: Yuko Green
<<a href="mailto:yuko.green@icann.org">yuko.green@icann.org</a>>,
"<a href="mailto:iotf@icann.org">iotf@icann.org</a>"
<<a href="mailto:iotf@icann.org">iotf@icann.org</a>><br>
Subject: Re: [IOTF] RZERC member qualification criteria<br><br>
I could not attend this meeting, and the transcript is not yet posted, so
perhaps I am taking this out of context, but I find the criteria,
particularly the two first ones, close to insulting to the communities
that will be contributing members to the RZERC.<br><br>
The concept that a "general technical knowledge of the DNS" is
sufficient seems to ignore that this is THE group that will be ensuring
the integrity, security and stability of the root zone if and when it
evolves, and the idea that the groups contributing people would not put
their best on the RZERC, or that these people would not implicitly be
charged with involving others as necessary is pretty scary.<br><br>
Alan<br><br>
<br><br>
<br><br>
At 13/07/2016 06:00 PM, Yuko Green wrote:<br><br>
<blockquote type=cite class=cite cite="">Dear members of the IOTF,<br>
<br>
As discussed during today¡¯s IOTF call #15, I am circulating the RZERC
member qualification criteria to the list. <br>
<br>
¡è 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<br>
¡è Ability to coordinate and consult with their respective
organizations and communities to communicate issue under consideration
and bring relevant expertise to the Committee<br>
¡è Able to work and communicate in written and spoken English<br>
¡è Effective communication skills<br>
<br>
Given that these are based from the published Charter, we will move
forward with these qualifications unless there are any objections by this
Friday, 15 July. <br>
<br>
Regards,<br>
<br>
<b>Yuko Green<br>
</b>Strategic Programs Manager<br>
Global Domains Division<br>
Internet Corporation for Assigned Names and Numbers (ICANN)<br>
<br>
Direct Line: +1 310 578 8693<br>
Mobile: +1 310 745 1517<br>
E-mail:
<a href="mailto:yuko.green@icann.org">yuko.green@icann.org</a><br>
<a href="http://www.icann.org/" eudora="autourl">www.icann.org</a><br>
<br>
Content-Type: application/pkcs7-signature;
name="smime.p7s"<br>
Content-Disposition: attachment; filename="smime.p7s"<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;SN1PR0301MB2030;9:q/tUl4aaz6nhP2kc6sLANfE3LfdGBcaxfHssUYQb73mqyi8dhy9piCLgzPM7ayvxE5l+5LQTqrx5EluDg50n2BktiNUtTSwPMd3Z3xtw3DDNt9T/3C/mO6qWCBj1CQpuhIo9UlQTb16A/k39bEMq0pOyQgHR30bvBCoqi+90wl50zFIxQmADgcakHRIgmGmeo8Xu2JXBvg2v0BkKkGxHRA==<br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;SN1PR0301MB2030;9:q/tUl4aaz6nhP2kc6sLANfE3LfdGBcaxfHssUYQb73mqyi8dhy9piCLgzPM7ayvxE5l+5LQTqrx5EluDg50n2BktiNUtTSwPMd3Z3xtw3DDNt9T/3C/mO6qWCBj1CQpuhIo9UlQTb16A/k39bEMq0pOyQgHR30bvBCoqi+90wl50zFIxQmADgcakHRIgmGmeo8Xu2JXBvg2v0BkKkGxHRA==<br>
<br>
_______________________________________________<br>
IOTF mailing list<br>
<a href="mailto:IOTF@icann.org">IOTF@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iotf" eudora="autourl">
https://mm.icann.org/mailman/listinfo/iotf</a></blockquote></blockquote>
</body>
</html>