<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=Windows-1252">
<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;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Calibri Light","sans-serif";
color:#2E74B5;}
span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
mso-style-link:"Comment Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle29
{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="color:#1F497D">Milton,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Speaking just in my personal capacity, I think that will have to be decided when we develop accountability mechanisms. And I expect that ccTLD community members will have a lot to say about that because they
understand their world a lot better than I do.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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""> Milton L Mueller [mailto:mueller@syr.edu]
<br>
<b>Sent:</b> Thursday, November 06, 2014 9:17 AM<br>
<b>To:</b> Gomes, Chuck; 'Marika Konings'; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Great, that answers one of my questions. You see, it was worth asking. As for what question I was asking it was stated very clearly in the original message:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">are we considering the “principles and guidelines” provided by GAC and CCNSO to be “</span><span style="color:#1F4E79">criteria that must be followed by the IANA functions operator” or not?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The information below tells us that it _is_ considered a “source of policy”
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gomes, Chuck <a href="mailto:[mailto:cgomes@verisign.com]">
[mailto:cgomes@verisign.com]</a> <br>
<b>Sent:</b> Thursday, November 6, 2014 9:03 AM<br>
<b>To:</b> Milton L Mueller; 'Marika Konings'; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Milton,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Here is some other information relating to this thread that was brought to my attention.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">On the GAC Principles thing they are formally referred to in the NTIA contract as follows:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">C.2.9.2.c Delegation and Redelegation of a Country Code Top Level-Domain (ccTLD) --The Contractor shall apply existing policy frameworks in processing requests related
to the delegation and redelegation of a ccTLD, such as RFC 1591 Domain Name System Structure and Delegation, the Governmental Advisory Committee (GAC) Principles And Guidelines For The Delegation And Administration Of Country Code Top Level Domains, and any
further clarification of these policies by interested and affected parties as enumerated in Section C.1.3. If a policy framework does not exist to cover a specific instance, the Contractor will consult with the interested and affected parties, as enumerated
in Section C.1.3; relevant public authorities; and governments on any recommendation that is not within or consistent with an existing policy framework. In making its recommendations, the Contractor shall also take into account the relevant national frameworks
and applicable laws of the jurisdiction that the TLD registry serves. The Contractor shall submit its recommendations to the COR via a Delegation and Redelegation Report.</span></i><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">As such this refers to two main sources of policy for the delegation and re-delegation of ccTLDs which were not developed in the ICANN bottom-up policy dev. model.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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""> Gomes, Chuck
<br>
<b>Sent:</b> Thursday, November 06, 2014 8:29 AM<br>
<b>To:</b> 'Milton L Mueller'; 'Marika Konings'; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks Milton. Please see my responses below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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""> Milton L Mueller
</span><a href="mailto:[mailto:mueller@syr.edu]"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">[mailto:mueller@syr.edu]</span></a><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<br>
<b>Sent:</b> Thursday, November 06, 2014 12:20 AM<br>
<b>To:</b> Gomes, Chuck; 'Marika Konings'; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi, Chuck, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">we are not at the level of specific edits yet, though a few of my comments cold be translated into those and I will do that at an appropriate time.
<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] I have two questions: 1) Who is ‘we’?; 2) why are we not at the level of specific edits yet?</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I am asking more fundamental questions about approach. Most importantly, are we considering the “principles and guidelines” provided by GAC and CCNSO to be “</span><span style="color:#1F4E79">criteria that must
be followed by the IANA functions operator” or not? <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] I cannot answer that because I think that is an issue for ccTLDs. I would encourage those from the ccTLD community to respond. Besides serving as the coordinator for this subgroup, I have
primarily contributed to the gTLD side and tried to rely and respect the expertise of those from the ccTLD community.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">If not, then we can describe them as part of the policy process. If you do, then we can leave it as it.</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] Could you make specific suggestions regarding how you would do this? This is an example where redline changes would make it much easier for staff to respond and for the rest of us to evaluate
the changes. Because there are such a large number of people in the CWG (and that is good), managing the edits to documents could become an excessively challenging process for the few people who are responsible for that.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">Similarly, I just want to ask why we are including the IANA contract as a source of policy from the names community.
<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] It is not being included as a source of policy. That is just one example of why we changed the section title. Another example is the GAC principles. I understand that in a normal business
environment that respondents would not change the wording from an RFP but I don’t think that we are a normal business environment. More importantly, it is my impression that the ICG with good intentions tried to create an RFP as a one size fits all for all
three of the areas that need to respond. But in the case of names, the source of policy is much more complex, and that may be even more the case for ccTLDs. It was our belief that to present just pure sources of policy would be incomplete. The ICG could
decide that we are wrong on that. At this stage, the CWG needs to evaluate our approach and recommend changes if they think they are needed.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">I’m open to support or opposition to those points, but it makes no sense for me to dip into the document and change things unless we have agreement on those points.</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] Agreement in the CWG is what we are currently trying to get. If changes need to be made to get agreement, then we need specific suggestions as to what changes are proposed and then discussion
in the CWG to see if we have consensus on the changes.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gomes, Chuck <a href="mailto:[mailto:cgomes@verisign.com]">
[mailto:cgomes@verisign.com]</a> <br>
<b>Sent:</b> Wednesday, November 5, 2014 5:40 PM<br>
<b>To:</b> Milton L Mueller; 'Marika Konings'; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for reviewing the document Milton. I will ask you to do what I asked all CWG participants to do earlier today: Please provide any edits you want to suggest in a redlined version of the Proposal and the
subgroup and entire CWG will consider them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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""> Milton L Mueller [</span><a href="mailto:mueller@syr.edu"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:mueller@syr.edu</span></a><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<br>
<b>Sent:</b> Wednesday, November 05, 2014 4:43 PM<br>
<b>To:</b> 'Marika Konings'; Gomes, Chuck; 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] IANA Stewardship Transition CWG RFP Section 2A Proposal 3 November 2014 Draft<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hello,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Have looked over this table. Perhaps this is an intermediate-level document that is designed to prepare the response to II.A, and if so some of my comments may not apply. But if this is intended to be a draft
response for II.A I am concerned about the extent to which it actually conforms to the ICG’s RFP.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Section 2A of the RFP is entitled “Policy sources” and asks for “the specific source(s) of policy that must be followed by the IANA functions operator in its conduct of the services or activities described [in
Section 1] above. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So someone has re-labeled the response as
</span><span style="color:#1F4E79">“Policy, Principles and Guidelines” and the comment says it was “changed here because some of the information provided is not actually policy but it relevant to policy and should therefore be included.”
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">I do not think I agree with this approach, at least not on first review. Organizations responding to an RFP typically don’t change the RFP. Let’s not rewrite the RFP. The ICG is asking for the sources of policy
or policy development. IF the GAC “principles and guidelines” or the CCNSO documents establish criteria that “must be followed by the IANA functions operator” then include it; if they are not guiding factors but merely suggestions that may or may not be followed
in any particular instance, we don’t include them. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">If you are concerned about blurry lines between what is policy and what is only an important factor shaping policy, GAC’s Advisory role in policy development might more properly be dealt with in a “description
of how policy is developed” (bullet point 2 in the RFP) than by citing particular documents GAC has produced. It is really GAC’s role as defined in the ICANN bylaws, and not any specific document of GAC, that are most relevant here.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">I agree with Marika’s comment that the information about GNSO policy development process should be current, there is no need to reference obsolete versions.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">I note that this document does not deal with bullet point 3 (how disputes about policy are resolved) – is that an oversight or just that we are not there yet? Obviously we would need to reference the Independent
Review Process, the Reconsideration Request and the Ombudsman. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">I also note that this document does not map the policy sources to the specific IANA functions that are affected. The RFP requires us to do that.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79">Finally, it seems strange to me to include the IANA contract in this list. In one very important sense, of course it is a key source of policy for the performance of the IANA functions. The problem is that the
IANA contract does not come from the GNSO, the CCNSO, the GAC, the ALAC or any other part or grouping of the names community. It comes from the U.S. government. So while I understand why you put it in there, I do not think it quite belongs. The RFP as I understand
it is asking for the ways in which the DNS community sets policy for the IANA. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F4E79"><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>