<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 05:02:25 Tuesday, 8 September 2015 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.5aefe298-f7db-430c-afb7-8abcc411c29d {
MARGIN: 0cm 0cm 0pt
}
LI.5aefe298-f7db-430c-afb7-8abcc411c29d {
MARGIN: 0cm 0cm 0pt
}
DIV.5aefe298-f7db-430c-afb7-8abcc411c29d {
MARGIN: 0cm 0cm 0pt
}
TABLE.5aefe298-f7db-430c-afb7-8abcc411c29dTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 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:11.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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial","sans-serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Arial","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;}
/* List Definitions */
@list l0
{mso-list-id:713887926;
mso-list-type:hybrid;
mso-list-template-ids:-2100397604 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:888806012;
mso-list-type:hybrid;
mso-list-template-ids:-110340950 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">
<p class="5aefe298-f7db-430c-afb7-8abcc411c29d"></p>
<div class="WordSection1">
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached please find:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. An updated ICANN bylaws matrix, clean and marked against the original draft; and<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. A draft comment letter from CWG to CCWG to the CCWG’s 2<sup>nd</sup> draft proposal.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In addition, given the recent discussion on the appeals mechanism, we thought it might be helpful to have all of the references to the appeals mechanism from the final CWG proposal in one place (see below for those excerpts).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Holly and Sharon<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">Extracts from Final CWG Proposal (June 11, 2015):<o:p></o:p></span></u></b></p>
<p class="Default"><u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Para 106:
<o:p></o:p></span></u></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The CWG-Stewardship proposal is significantly dependent and expressly conditioned on the implementation of ICANN-level accountability mechanisms by the Cross
Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) as described below. The co-chairs of the CWG-Stewardship and the CCWG-Accountability have coordinated their efforts and the CWG-Stewardship is confident that the CCWG-Accountability
recommendations, if implemented as envisaged, will meet the requirements that the CWG-Stewardship has previously communicated to the CCWG. If any element of these ICANN level accountability mechanisms is not implemented as contemplated by the CWG-Stewardship
proposal, this CWG-Stewardship proposal will require revision. Specifically, the proposed legal structure and overall CWG-Stewardship proposal requires ICANN accountability in the following respects: …<o:p></o:p></span></p>
<p class="Default" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">6. Appeal mechanism</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">.
An appeal mechanism, for example in the form of an Independent Review Panel, for issues relating to the IANA functions. For example, direct customers with non-remediated issues or matters referred by ccNSO or GNSO after escalation by the CSC will have access
to an Independent Review Panel. The appeal mechanism will not cover issues relating to ccTLD delegation and re-delegation, which mechanism is to be developed by the ccTLD community post-transition.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Para 160:<o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="color:#1F497D;background:yellow;mso-highlight:yellow">The CWG-Stewardship recommends not including any appeal mechanism that would apply to ccTLD delegations and redelegations in the IANA Stewardship Transition proposal.</span><span style="color:#1F497D">
For further information, see Annex O.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Para 194:<o:p></o:p></span></u></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The CWG-Stewardship’s proposed changes are to be implemented after NTIA approval of the IANA Stewardship Transition plan. Some changes are ready to be implemented,
and others may require further assessment by the ICG as they may affect and be of interest to other communities involved in the IANA Stewardship Transition. For all changes, including changes that do not require further assessment by the ICG, the community
will work with ICANN in implementation. The CWG-Stewardship expects that the following implementation items could be completed in approximately three to four months, in accordance with the advice of independent legal counsel: (1) identifying the ICANN assets
that relate to the IANA functions to be assigned to PTI and assigning those assets to PTI pursuant to an assignment agreement to be entered into between ICANN and PTI, (2) incorporating PTI and drafting the PTI governance documents (i.e., articles of incorporation
and bylaws) and (3) drafting, negotiating and finalizing the ICANN-PTI Contract.35 The CWG-Stewardship has attempted an initial list of elements for implementation as follows: …<o:p></o:p></span></p>
<p class="Default" style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;background:yellow;mso-highlight:yellow"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">Appeal mechanism</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">:
This have been requested of the CCWG-Accountability as part of a key dependency with the CCWG-Accountability as soon as their work is finalized.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Annex O: <o:p></o:p></span></u></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">While the CWG-Stewardship’s 1 December, 2014 draft proposal contained an appeal mechanism that would have applied to ccTLD delegation and redelegations, some
question arose as to the level of support within the ccTLD community on aspects of this proposal (see below). Design Team B was formed to assess whether there might be sufficient consensus within the ccTLD community on such an appeal mechanism. DT-B decided
to undertake a survey of the ccTLD community to assess this (see the survey and the results summarized below).
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">After informing the ccTLD community about the upcoming survey, it was sent to the ‘ccTLD World’ list, the most comprehensive list of the managers of the 248 ccTLDs
on March 23, 2015 with responses accepted to 3 April 2015. Overall, responses on behalf of just 28 managers were received (see below). Such a low level of response was judged to be an insufficient basis to provide a mandate for the inclusion of an appeal mechanism
in the CWG-Stewardship’s proposal. While acknowledging the limitations of drawing any conclusions from a survey with such a low response rate, it is nevertheless worthwhile pointing out that these limited responses tended to reinforce the overall recommendation.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">While 93% of respondents (Q.1) believe there is a need for an appeal mechanism, only 58% (Q.2) believe that it should be developed and introduced now as part
of the IANA Stewardship Transition and 73% (Q.3) agreed that it should be developed and introduced after the IANA Stewardship Transition has taken place. Questions designed to probe the level of consensus on the parameters of such an appeal mechanism (see
Q.5 – Q.9) elicited no consensus suggesting that it would take considerable time for the ccTLD community to come to a consensus view on the details of an appeal mechanism. Some 71% of respondents (Q.3) indicated that they would not wish to see the design of
such a mechanism delay the finalization of the IANA Stewardship Transition. <o:p>
</o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="color:#1F497D">Survey of ccTLD Managers on Need for Appeal Mechanism for ccTLD Delegations and Redelegations
</span></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.7pt;text-autospace:none"><span style="color:#1F497D">On 1 December 2014, the Cross Community Working Group on NTIA Stewardship Transition issued a draft proposal which contained a proposal for an “independent appeals
panel”: <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.7pt;text-autospace:none"><span style="color:#1F497D">“Independent Appeals Panel (IAP) - The CWG-Stewardship recommends that all IANA actions which affect the Root Zone or Root Zone WHOIS database be subject to an
independent and binding appeals panel. The Appeals Mechanism should also cover any policy implementation actions that affect the execution of changes to the Root Zone File or Root Zone WHOIS and how relevant policies are applied. This need not be a permanent
body, but rather could be handled the same way as commercial disputes are often resolved, through the use of a binding arbitration process using an independent arbitration organization (e.g., ICDR, ICC, AAA) or a standing list of qualified people under rules
promulgated by such an organization.” <o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D">There exists in the ccTLD community an apparent lack of consensus on the question of the introduction of an ‘appeals mechanism’ in respect of ccTLD delegations and redelegations.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="Default" style="margin-bottom:12.7pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">At ICANN 51 in Los Angeles an overwhelming majority of ccTLD representatives at the 15 October 2014 ccNSO meeting indicated their
wish for an ‘appeal mechanism’ as part of the IANA transition, though what was meant by ‘an appeal mechanism’ was not defined. In a survey of all ccTLD managers undertaken in November 2014, 94% of respondents agreed that ‘if the IANA operator does not perform
well or abuses its position, the affected ccTLD should have the opportunity to (have access to) an independent and binding appeal process’. The expression of need resulted in the appeal mechanism proposal that the CWG-Stewardship released on 1 December 2014.
The proposal indicates that such a mechanism could be used in disputes over the consistency of ccTLD delegation or redelegation decisions.
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:12.7pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A survey was undertaken in January of this year of CWG-Stewardship members and participants (this includes representation from many
communities, not just ccTLD managers) on many aspects of the CWG-Stewardship’s 1 December proposal. It found that 97% of respondents agreed that, “<i>ccTLD registry operators should have standing to appeal delegation and re-delegation decisions to which they
are a party that they believe are contrary to applicable laws and/or applicable approved ccTLD policy</i>”. However when questions were posed about potential specific parameters of such an appeal mechanism support for it was reduced. For example, only 54%
of respondents agreed that “<i>ccTLD registry operators should have standing to appeal delegation and redelegation decisions to which they are a party that they believe are contrary to applicable laws and/or applicable approved ccTLD policy, even if the operator
is not a party involved in the delegation or redelegation”. </i>In addition, only 60% of respondents agreed that, “<i>Governments should have standing to appeal any ccTLD delegation or redelegation decisions that they believe are contrary to applicable laws</i>”.
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:12.7pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This information suggests that while there may be support for an appeal mechanism in general, consensus may be difficult to achieve
on some of the important aspects of such a mechanism, including: <o:p></o:p></span></p>
<p class="Default" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.7pt;margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Who would ‘have standing’ to appeal decisions,
<o:p></o:p></span></p>
<p class="Default" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.7pt;margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What aspects of decisions might be subject to an appeal,
<o:p></o:p></span></p>
<p class="Default" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.7pt;margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Whether the scope should be limited to determining whether the process followed was complete and fair,
<o:p></o:p></span></p>
<p class="Default" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.7pt;margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Whether the dispute resolution panel would have the authority to substitute its own view on a delegation, for example, direct that the incumbent manager
be retained rather than a proposed new manager, or <o:p></o:p></span></p>
<p class="Default" style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Be limited to requiring that the delegation process be repeated.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As a consequence, this survey is intended to determine whether they might be sufficient consensus within the ccTLD community as a whole to seek a binding appeal
mechanism and if so, whether this should be sought as part of the IANA Stewardship Transition process. [The remainder of Annex O consists of the survey.]<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><u><span style="color:#1F497D">Annex I - IANA Customer Service Complaint Resolution Process for Naming Related Functions:<o:p></o:p></span></u></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Phase 2 (for IANA naming services only)
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Para 381: Should the issue not be resolved after Phase 1 [Initial remedial process for IANA naming functions], the following escalation mechanisms will be made
available to direct customers, the IFO and the ICANN Ombudsman: [FN 53] <o:p></o:p></span></p>
<p class="Default" style="margin-bottom:12.75pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">a) If issue is not addressed, the complainant (direct customer), IFO or the ICANN Ombudsman may request mediation. [FN 54]
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">b) CSC is notified of the issue by complainant and/or the IANA Functions Operator. CSC reviews to determine whether the issue is part of a persistent performance
issue and/or is an indication of a possible systemic problem. If so, the CSC may seek remediation through the IANA Problem Resolution Process (see Annex J).
<o:p></o:p></span></p>
<p class="Default"><o:p> </o:p></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">c) The complainant (direct customer) may initiate an Independent Review Process or pursue other applicable legal recourses
that may be available, if the issue is not addressed.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D">[FN 53: Non-direct customers, including TLD organizations,that are of the view that an issue has not been addressed through Phase 1 may escalate the issue to the ICANN Ombudsman or
via the applicable liaisons to the CSC to Phase 2.]<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D">[FN 54: The CWG-Stewardship recommends that as part of the implementation of this proposal, ICANN Staff explore possible approaches with regards to mediation such as, for example,
Section 5.1 of the Base gTLD Registry Agreement (<a href="https://www.icann.org/resources/pages/registries/registries-agreements-en">https://www.icann.org/resources/pages/registries/registries-agreements-en</a>).]<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><u><span style="color:#1F497D">Draft Proposed Term Sheet (Annex S):<o:p></o:p></span></u></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">ESCALATION MECHANISMS (IANA Customer Service Complaint Resolution Process)
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="Default" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo4">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Phase 1: If anyone experiences an issue with PTI’s delivery of IANA naming functions, the complainant can send an email to PTI, which will escalate
the complaint internally as required. This process is open to anyone, including individuals, registries, ccTLD regional organizations and ICANN SO/ACs.
<o:p></o:p></span></p>
<p class="Default" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo4">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Phase 2: If the issue identified in Phase 1 is not addressed by PTI to the reasonable satisfaction of the complainant, then complainants that are
direct customers only may request mediation. ICANN and CSC will be notified of the issue and CSC will conduct a review to determine whether the issue is part of a persistent performance issue or an indication of a systemic problem. If so, the CSC may seek
remediation through the Problem Resolution Process described below. This process is only open to direct customers. Non-direct customers, including TLD organizations, who have issues unresolved in Phase 1, may escalate the issues to the ombudsman or the applicable
liaisons to the CSC. <o:p></o:p></span></p>
<p class="Default" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo4">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D;background:yellow;mso-highlight:yellow"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow">The complainant may also initiate an Independent Review Process if the issue is not addressed in the steps
above. </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow"> <b><i>[Note from Sidley: We believe this should reference “direct customers.”]</i></b></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;background:yellow;mso-highlight:yellow"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
<p></p>
<p class="5aefe298-f7db-430c-afb7-8abcc411c29d"> </p>
<p>****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>
If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************</p>
</body>
</html>