<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=utf-8">
<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:Verdana;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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-family:"Calibri","sans-serif";}
@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">That would be good if possible. How do we do that in an open and transparent way?<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>
<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""> Sivasubramanian M [mailto:isolatedn@gmail.com]
<br>
<b>Sent:</b> Friday, November 28, 2014 6:17 AM<br>
<b>To:</b> Gomes, Chuck<br>
<b>Cc:</b> Greg Shatan; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Fwd: Stress Tests for IANA transition proposals<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333">Dear Chuck, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333">Agree that we must be prepared. We could prepare solutions for some of the scenarios already outlined, and if there are new scenarios that are prone to capture the imagination,
there could be a quieter way of contemplating and preparing for such scenarios.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333">Thank you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><a href="https://www.facebook.com/sivasubramanian.muthusamy" target="_blank">Sivasubramanian M</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Nov 28, 2014 at 4:35 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Siva,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I would not characterize these as ‘</span><span style="font-family:"Verdana","sans-serif";color:#333333">imaginary
extreme scenarios</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">’ . For some of them it is easier for me to see they ‘</span><span style="font-family:"Verdana","sans-serif";color:#333333">might give ideas that might
actually lead to such scenarios</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">’ than for others. Regardless, they all seem like scenarios that we need to prepare for.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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"">
<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Sivasubramanian M<br>
<b>Sent:</b> Friday, November 28, 2014 2:39 AM<br>
<b>To:</b> Greg Shatan<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Fwd: Stress Tests for IANA transition proposals</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333">Greg,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333">Apart from the scenarios that are pertinent to IANA, identified by Steve DelBianco with red coloring, more scenarios
could be outlined in the specific context of transition, and if we do, we may have to outline strategies to deal with each of these scenarios and assess if IANA would get past such scenarios ?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333">One problem with this approach is that some of such imaginary extreme scenarios vividly outline ways by which IANA
can be harmed, and might give ideas that might actually lead to such scenarios. Certain degree of caution is required in outlining some scenarios that point to ways of doing harm. I could already see one or two examples that could make someone consider it
to be interesting ways of causing trouble.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333">Just a thought.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana","sans-serif";color:#333333">Sivasubramanian M</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://www.facebook.com/sivasubramanian.muthusamy" target="_blank">Sivasubramanian M</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Fri, Nov 28, 2014 at 12:14 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">All,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">Further to our recent discussions of stress tests, scenarios and the like, I am forwarding to the group an email from Steve DelBianco of the Business Constituency with a number of examples
of stress tests and links to further discussion.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">This is particularly relevant to RFP4 (which requests a "Description of how you have tested or evaluated the workability of any new technical or operational methods proposed
in this document and how they compare to established arrangements") and RFP3 (to inform our discussion of various alternatives and their strengths and weaknesses).<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">Greg<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">---------- Forwarded message ----------<br>
From: <b>Steve DelBianco</b> <<a href="mailto:sdelbianco@netchoice.org" target="_blank">sdelbianco@netchoice.org</a>><br>
Date: Tue, Nov 25, 2014 at 3:24 PM<br>
Subject: Stress Tests for IANA transition proposals<br>
To: "<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>" <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>><br>
Cc: Steve Metalitz <<a href="mailto:met@msk.com" target="_blank">met@msk.com</a>>, Tony Holmes <<a href="mailto:tonyarholmes@btinternet.com" target="_blank">tonyarholmes@btinternet.com</a>>, Phil Corwin <<a href="mailto:psc@vlaw-dc.com" target="_blank">psc@vlaw-dc.com</a>>,
Aparna Sridhar <<a href="mailto:aparnasridhar@google.com" target="_blank">aparnasridhar@google.com</a>>, "<a href="mailto:skawaguchi@fb.com" target="_blank">skawaguchi@fb.com</a>" <<a href="mailto:skawaguchi@fb.com" target="_blank">skawaguchi@fb.com</a>>,
Jonathan Zuck <<a href="mailto:JZuck@actonline.org" target="_blank">JZuck@actonline.org</a>>, Kristina Rosette <<a href="mailto:krosette@cov.com" target="_blank">krosette@cov.com</a>>, Rick Lane <<a href="mailto:RLane@21cf.com" target="_blank">RLane@21cf.com</a>>,
Elisa Cooper <<a href="mailto:Elisa.Cooper@markmonitor.com" target="_blank">Elisa.Cooper@markmonitor.com</a>><o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif";color:black">Greg — as you requested on our call today, here are ’stress tests’ from the BC's June comments (<a href="http://www.bizconst.org/wp-content/uploads/2014/07/BC-reply-comment-on-Enhancing-ICANN-Accountability-FINAL.pdf" target="_blank">link</a> to
comments). The stress tests in a standalone doc are also available at <a href="http://bizconst.org/StressTests" target="_blank">
http://bizconst.org/StressTests</a> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif";color:black">Some of these stress tests relate to general ICANN accountability concerns. But several are relevant to the IANA role
you are looking at for Naming Functions (Numbers 3, 5, 7, 8, 9, and 10, in red below): </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">The BC recommends use of scenarios, or ‘stress tests’ to help design and evaluate ICANN accountability structures and mechanisms. Today, ICANN is an effective organization that
generally performs its core functions. Although it can be uncomfortable to imagine a scenario where a future ICANN fails dramatically or is confronted with a serious threat, we should consider challenging scenarios that could arise, such as those described
below:</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">1.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Scenario: ICANN unilaterally cancels the
</span><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue">Affirmation of Commitments</span></i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">, which it may do with just 120 days notice. And if not
outright cancellation, ICANN could refuse to implement recommendations of an <i>
Affirmation </i>review. Presently, the discipline imposed by needing to win the IANA contract forces ICANN to adhere to the only external accountability it has today: the
<i>Affirmation of Commitments</i>. If the <i>Affirmation </i>is to remain part of the new ICANN accountability framework, it is essential that the leverage formerly conveyed by the IANA contract be replaced with a new mechanism, which may or may not include
parties external to ICANN. </span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">2.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Scenario: ICANN takes steps to eliminate its legal presence in a nation where Internet users and domain registrants are planning to seek legal remedies for ICANN’s failure
to enforce contracts. This scenario is not about ICANN opening new offices around the world as part of its global outreach. Rather, it is about ICANN creating a new legal entity distinct from its present status as a California non-profit corporation, and eventually
relocating its legal presence. ICANN’s current corporate presence in California creates legal certainty for businesses; presence in a new jurisdiction might not.
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">3.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: ICANN becomes financially insolvent, due to lawsuits or gross mismanagement. However unlikely, this scenario should explore the orderly continuation of IANA functions
and ICANN contract enforcement in the event ICANN could not maintain the necessary qualified technical resources.
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">4.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Scenario: ICANN expands scope beyond its limited technical mission by using domain registration fees to fund grants for developing nations or other worthy causes. ICANN has
the power to determine fees charged to TLD applicants, registry operators, registrars, and registrants, so it presents a big target for any Internet-related cause seeking funding sources. This scenario should examine how a fully independent ICANN could be
held to its limited technical mission, and whether its fees and spending are subject to external accountability.
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">5.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: ICANN attempts to add a new top-level domain in spite of security and stability concerns expressed by technical community leaders. This scenario actually came close
to occurring when ICANN management did not respond to recommendations of its own Security and Stability Advisory Committee (SSAC) regarding risks of new TLDs interacting with security certificates and internal domains already in use. SSAC recommendations from
prior years were not acted upon until late 2013, after significant pressure from a root server operator, Internet service providers, and system integrators. In the actual event, ICANN responded with a collision mitigation plan. This scenario should assess
how proposed new accountability mechanisms could respond to similar technical risks expressed before a TLD delegation, as well as reactive responses to problems reported after a delegation.
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">6.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Scenario: Governments in ICANN’s Government Advisory Committee (GAC) amend their operating procedures to change from consensus decisions to majority voting. Today GAC adopts
formal advice according to its Operating Principle 47: “<i>consensus is understood to mean the practice of adopting decisions by general agreement in the absence of any formal objection</i>.”</span><span style="font-size:7.0pt;font-family:"Calibri","sans-serif";color:black">13
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">But the GAC may at any time change its procedures to use majority voting, where each government has equal voting power, such as in the UN and ITU. (Notably, only 61 governments
were present at the GAC meeting in Singapore during March 2014, where several GAC members expressed dissatisfaction with the multistakeholder process and consensus threshold for new gTLD program advice.) While ICANN’s board is not strictly obligated to follow
GAC advice, this scenario should assess how ICANN could respond to GAC advice with strong majority support but less than consensus. This scenario might also indicate need to amend ICANN bylaws regarding deference to GAC advice that is not supported by consensus.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">7.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: As described in scenario 6, the GAC might issue majority-supported advice instructing ICANN to suspend a TLD that refuses to remove domains with content critical of
governments (e.g., <b>.</b>corrupt ). Today, this kind of censorship routinely occurs at the edge of the Internet when governments block domestic access to websites, such as Turkey blocking Twitter. This scenario envisions censorship moving from the edge
<i>to the core of the internet </i>– the root table of TLDs used by the entire world. The stress test would ask how a proposed accountability mechanism could respond if a future ICANN board bowed to GAC advice for censorship at the root of the DNS.
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">8.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: ICANN attempts to re-delegate a gTLD because the registry operator is determined to be in breach of its contract. The registry operator challenges the breach determination
and obtains an injunction from a national court. What procedures or appeal mechanisms would be used by the entity charged with maintenance and publication of the root zone?
</span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">9.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: A court grants an injunction against delegation of a new gTLD that’s a plural version of another TLD that has already been delegated. (for example, .hotels following
after .hotel, or .coms following after .com) The court may have ruled on infringement of rights or on arbitrary and capricious behavior by ICANN, but that’s beside the point. The point of this scenario is to ask how a post-transition ICANN and IANA would be
empowered to respond to a court injunction granted by a jurisdiction where ICANN has a legal presence. Would ICANN/IANA be able to defer a delegation until court proceedings were concluded? How would ICANN/IANA be accountable for its decision if it ignored
the court injunction? </span><o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">10.</span><span style="font-size:7.0pt;color:black">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">Scenario: A government telecom minister instructs ICANN to re-delegate a country-code top-level domain (ccTLD), despite objections from many current registrants and user communities
in the country concerned. Faced with this re-delegation request, what response options and measures could be available to ICANN and the entity charged with maintenance of the root zone? </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365D">Gregory S. Shatan </span></b><b><span style="font-size:8.0pt;font-family:Symbol;color:#17365D">ï</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365D"> </span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#C0504D">Abelman
Frayne & Schwab</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365D">666 Third Avenue </span></b><b><span style="font-size:8.0pt;font-family:Symbol;color:#17365D">ï</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365D"> New
York, NY 10017-5621</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Direct</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155CC">212-885-9253 <b>| </b></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Main</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155CC">212-949-9022</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Fax</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155CC">212-949-9190 <b>|</b> </span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Cell </span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155CC">917-816-6428</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="mailto:gsshatan@lawabel.com" target="_blank"><span style="color:#1155CC">gsshatan@lawabel.com</span></a></span></i></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><span style="font-family:"Calibri","sans-serif"">ICANN-related: <a href="mailto:gregshatanipc@gmail.com" target="_blank">
gregshatanipc@gmail.com</a> </span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;background-image:initial;background-repeat:initial">
<b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="http://www.lawabel.com/" target="_blank"><span style="color:#1155CC">www.lawabel.com</span></a></span></i></b><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>