<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Me too. Nice job Trang.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> iotf-bounces@icann.org [mailto:iotf-bounces@icann.org]
<b>On Behalf Of </b>Alan Greenberg<br>
<b>Sent:</b> Tuesday, July 19, 2016 6:27 PM<br>
<b>To:</b> Trang Nguyen; Yuko Green; iotf@icann.org<br>
<b>Subject:</b> Re: [IOTF] RZERC member qualification criteria<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Looks good to me. Alan<br>
<br>
At 19/07/2016 12:20 PM, Trang Nguyen wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Hi Alan,<br>
<br>
Thank you for the suggested language. If I may make some suggestions for minor edits to the drafted language below:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">The RZERC is the group that will be reviewing <span style="color:red">
issues relating to <s>and recommending </s></span>the architecture and operational systems for
<s><span style="color:red">the </span></s>the DNS Root Zone as it evolves, <span style="color:red">
and providing recommendations to the ICANN Board to </span>ensur<span style="color:red">e<s>ing</s></span> the
<s><span style="color:red">integrity, </span></s>security<span style="color:red">,<s> and</s></span> stability<span style="color:red">, and resiliency</span> of the root zone.
<br>
<br>
Appointees to the RZERC must have a strong overall understanding of the R<span style="color:red">oot
</span>Z<span style="color:red">one</span>, and must be able fully represent their appointing organization's particular interest in the root zone.<o:p></o:p></p>
<p class="MsoNormal">Trang<br>
<br>
From: Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a> ><br>
Date: Monday, July 18, 2016 at 7:19 PM<br>
To: Trang Nguyen <<a href="mailto:trang.nguyen@icann.org">trang.nguyen@icann.org</a> >, 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 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>
<br>
<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
Alan<br>
<br>
<br>
At 15/07/2016 10:31 AM, Trang Nguyen wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">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>
<br>
<o:p></o:p></p>
<p class="MsoNormal">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/">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>
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>
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">https://mm.icann.org/mailman/listinfo/iotf</a><o:p></o:p></p>
</div>
</body>
</html>