<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<![if !supportAnnotations]><style id="dynCom" type="text/css"><!-- --></style><script language="JavaScript"><!--
function msoCommentShow(anchor_id, com_id)
{
if(msoBrowserCheck())
{
c = document.all(com_id);
a = document.all(anchor_id);
if (null != c && null == c.length && null != a && null == a.length)
{
var cw = c.offsetWidth;
var ch = c.offsetHeight;
var aw = a.offsetWidth;
var ah = a.offsetHeight;
var x = a.offsetLeft;
var y = a.offsetTop;
var el = a;
while (el.tagName != "BODY")
{
el = el.offsetParent;
x = x + el.offsetLeft;
y = y + el.offsetTop;
}
var bw = document.body.clientWidth;
var bh = document.body.clientHeight;
var bsl = document.body.scrollLeft;
var bst = document.body.scrollTop;
if (x + cw + ah / 2 > bw + bsl && x + aw - ah / 2 - cw >= bsl )
{ c.style.left = x + aw - ah / 2 - cw; }
else
{ c.style.left = x + ah / 2; }
if (y + ch + ah / 2 > bh + bst && y + ah / 2 - ch >= bst )
{ c.style.top = y + ah / 2 - ch; }
else
{ c.style.top = y + ah / 2; }
c.style.visibility = "visible";
} } }
function msoCommentHide(com_id)
{
if(msoBrowserCheck())
{
c = document.all(com_id);
if (null != c && null == c.length)
{
c.style.visibility = "hidden";
c.style.left = -1000;
c.style.top = -1000;
} }
}
function msoBrowserCheck()
{
ms = navigator.appVersion.indexOf("MSIE");
vers = navigator.appVersion.substring(ms + 5, ms + 6);
ie4 = (ms > 0) && (parseInt(vers) >= 4);
return ie4;
}
if (msoBrowserCheck())
{
document.styleSheets.dynCom.addRule(".msocomanchor","background: infobackground");
document.styleSheets.dynCom.addRule(".msocomoff","display: none");
document.styleSheets.dynCom.addRule(".msocomtxt","visibility: hidden");
document.styleSheets.dynCom.addRule(".msocomtxt","position: absolute");
document.styleSheets.dynCom.addRule(".msocomtxt","top: -1000");
document.styleSheets.dynCom.addRule(".msocomtxt","left: -1000");
document.styleSheets.dynCom.addRule(".msocomtxt","width: 33%");
document.styleSheets.dynCom.addRule(".msocomtxt","background: infobackground");
document.styleSheets.dynCom.addRule(".msocomtxt","color: infotext");
document.styleSheets.dynCom.addRule(".msocomtxt","border-top: 1pt solid threedlightshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-right: 2pt solid threedshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-bottom: 2pt solid threedshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-left: 1pt solid threedlightshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","padding: 3pt 3pt 3pt 3pt");
document.styleSheets.dynCom.addRule(".msocomtxt","z-index: 100");
}
// --></script><![endif]><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-CA;}
span.MsoCommentReference
{mso-style-priority:99;}
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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
mso-style-link:"Comment Text";
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-CA;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">Thanks Marika. My feedback is provided here. Note that the page numbers I used refer to the redline version.<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">It is probably not a big issue but I wonder if we should define the terms ‘ccTLD’ and ‘gTLD’ early in the document, maybe in Section 1.A. From what I can tell
in the IANA Functions Contract, a gTLD appears to be defined as anything that is not a ccTLD except for .int, which appears to be treated separately. Is .arpa a gTLD, or is it a special case like .int. The reason I raise this is that in Section II.B several
edits were made changing ‘all gTLDs’ to ‘most gTLDs’. Without a specific definition of a gTLD, it is not clear what the exceptions are. Another way to handle this would be to add a footnote where we say ‘most gTLDs’ that lists the exceptions.<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">I think the first sentence of III.a on page 15 would be clearer if ‘</span>addressing these effects<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">’
is deleted at the end: “</span>The sections below describe how the transition will affect each of the naming functions identified and what changes, if any, the CWG-Stewardship recommends addressing these effects.<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I definitely think we need a glossary somewhere in the document that provides an easy place for readers to find the definitions of key terms, especially for
new terms and acronyms, e.g., PTI, IANA Functions Operator, CSC, IANA Review Team. I suspect that it will be difficult for those who have not been actively involved in the CWG to keep track of the definitions.<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">We need to make sure that the first time an acronym is used that we spell it out. For example, in section III.A.ii on page 20, ‘CSC’ is used (I think for the
first time). This issue may be corrected in some cases when the sections are reordered. For example, if what is now Section III.A.iii is moved ahead of section III.A.ii, then CSC would have already been defined.<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">In the second paragraph of section III.A.ii on page 20, we say: “</span>The members of the IANA Function Review Team would be selected by the Supporting Organizations
and Advisory Committees and would include several liaisons from other operational communities.<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">” What do we mean by operational communities? Do we really intend to restrict it
to operational communities? If so, we should define what we mean. If not, we probably should delete ‘operational’.<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">In Section III.A.iii (CSC) we say: “</span>The primary customers of the naming services are top level domain registry operators, but also include root server
operators and other non-root zone functions.<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">” This is a decision for DT-C, not me, but the last part of this sentence is not consistent with the charter. We need to make it consistent
with the composition section of the charter in Annex I starting on page 70 that includes the option for liaisons from ACs and SOs, etc. In the case of the RSSAC, it is treated the same as other ACs.
<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">Will the second bullet in section III.B on page 33 be deleted per the recommendations of DT-B: “</span><a name="_Toc289425735"><span style="color:#0B0B0B">Appeal
Mechanism for ccTLD Delegations / Redelegations – [DT-B]</span></a><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On pages 39-40, why was the text deleted for the 4<sup>th</sup> bullet under f): “</span><b><span style="color:#0B0B0B">Overlaps or interdependencies</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”?
What will replace it? Same questions apply to g) on page 40 and j) on page 41.<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">In Annex D on page 47, we say: “</span><span style="color:black">A Special Periodic Review may be also be initiated by community action</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”.
Shouldn’t the word ‘Periodic’ be deleted? We later say at the bottom of page 47: “</span>The outcomes of a Periodic Review are not limited but not either prescribed and could include a variety of recommendations.<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”
Should we change ‘Periodic Review’ to ‘Reviews’ so this statement includes both periodic and special reviews? These questions are probably best answered by Avri and DT-N.<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">I don’t know if I missed it in Annex D, but it doesn’t seem to cover the responsibility of reviewing systemic IANA problems and the possibility of recommending
escalation to accountability recommendations such as an RFP or accountability mechanisms that the CCWG recommends. (Note the Problem Management Process proposed by DT-M.)<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">In Annex J (Customer Service Complaint Resolution Process), in Phase 2, step b on page 76: ‘systems problem’ should be changed to ‘systemic problem’.<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">In Annex K (Problem Management Escalation Process), for step 3 on page 77, I think it would be a good idea to insert a footnote that says something like this:
“The roles of the ccNSO and GNSO in this step should be further investigated to ensure that this is consistent with their missions as well as to identify any actions that may be needed by the SOs to allow for this role.”<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">Please let me know if you have any questions.<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""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Friday, April 17, 2015 5:58 PM<br>
<b>To:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> [CWG-Stewardship] For your review - Draft Transition Plan V3.2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Dear All,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Please find attached for your review the latest version of the CWG-Stewardship Transition Proposal. Please note that it is still very much work in progress as
some key pieces are still missing such as the information from the legal memo that is forthcoming, outstanding work of the design teams (DT A) as well as final language from ‘DT X’. However, we did already want to give you an opportunity to review where we
are at and as such we would like to encourage you to instead of editing the document line by line, to focus on whether there is information missing or incorrect, the updated recommendations of some of the design teams (e.g. DT M and N) as well as reviewing
some of the changes we have made for style and consistency purposes to the DT recommendations. Note that thanks to Kim Davies a number of clarifications have been made to section I and II. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">We are still working on the annexes (focused on consistency and readability) as well as formatting and numbering of the overall document. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">As we’ve moved quite some things around in section III to follow a more logical order, there is a lot of redline in the document which does not necessarily represent
new or changed content, but also content that has changed position. As such, you will also find attached a clean version to facilitate your review. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Please share any comments you may have (preferably with a reference to page number and section) with the mailing list by Monday 23.59 UTC at the latest.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Marika<o:p></o:p></span></p>
</div>
</div>
<div style="mso-element:comment-list"><![if !supportAnnotations]>
<hr class="msocomoff" align="left" size="1" width="33%">
<![endif]></div>
</body>
</html>