<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EpostStil18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:212231876;
mso-list-type:hybrid;
mso-list-template-ids:1539714422 68419599 68419609 68419611 68419599 68419609 68419611 68419599 68419609 68419611;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:695350236;
mso-list-type:hybrid;
mso-list-template-ids:1443952316 68419585 68419587 68419589 68419585 68419587 68419589 68419585 68419587 68419589;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Some brief comments on the SIDLEY paper. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span lang="EN-US">In regards of roles of CSC and MRT/”members group”
<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span lang="EN-US"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><span lang="EN-US">I think it is crucial to have a very clear understanding and description of what we define as
<u>escalation, </u>and that this is not only used as a term relating to the role of the CSC. In our CWG discussions Escalation has been referring to the Multistakeholder component of the oversight function, - what used to be called the MRT. In the current structure
the MRT function has been merged with the work of the CCWG - referred to as «members group” with legal personhood. It might look like necessary detailing, but I think we should keep the wording clear and underline that the escalation happens when it is sent
over to MRT/”members group”/Multi-Stakeholder community Organisation.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span lang="EN-US">H. Fundamental bylaws <o:p></o:p></span></i></b></p>
<p class="MsoNormal"><i><span lang="EN-US"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><i><span lang="EN-US">What will these be?- While this is primarily an issue for CCWG, considerations should be given by CWG to whether there are any bylaws matters upon the model is conditioned.
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span lang="EN-US"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><span lang="EN-US">YES, - any model based on sort of “golden bylaw” arrangements as the last sort of action towards IANA function operator (PRI<u>) must</u> be based on the CWG giving clear conditions on bylaws and how they should work
in regards of decisions in the ICANN community and inside the ICANN company. We can`t push this bylaws arrangements to be solved by the CCWG - even if the link between the CWG and the CCWG is strong, and the communications between the chairs are very good,
we are working in parallel and aim to finish at the same time, - so CCWG haven’t got the time or detailed knowledge to design specific bylaws that will fit a new company structure for the IANA function and the oversight/stewardship of IANA.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Regarding the question from Andrew Sullivan
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span lang="EN-US">III.C talks about CSC. In the case of a full legal separation with<br>
independent governance, would the CSC be needed at all? Presumably<br>
the arrangements between PRI and their customers would be a<br>
contractual one, and as such the management of such contractual<br>
disputes ought to be via those contracts, and not through an extra<br>
body. Or is the point that the way such a contractual arrangement<br>
would solve such disputes ought to be along the lines of the CSC ?<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span lang="EN-US"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><span lang="EN-US">Do you mean PTI ? It’s fundamental from a governmental perspective (and also for the ccTLDs I think..) that we don’t create a model with requirements for establishing a contractual relationship between the IANA functions
operator (PTI) and the ccTLDs. This is an absolute no go. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Fra:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>På vegne av</b> Greg Shatan<br>
<b>Sendt:</b> 9. april 2015 01:50<br>
<b>Til:</b> Andrew Sullivan<br>
<b>Kopi:</b> Client; cwg-stewardship@icann.org<br>
<b>Emne:</b> Re: [CWG-Stewardship] Initial Discussion Draft on Transition Models<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Andrew,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I'm copying your email to the Client Committee email list for consideration by Sidley and the Client Committee.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg Shatan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;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:0cm;margin-bottom:.0001pt;line-height:12.0pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#365F91">Partner</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4F81BD"> | IP | Technology | Media | Internet</span></b><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365D">666 Third Avenue | New York, NY 10017-5621</span></b><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;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"><a href="tel:212-885-9253" target="_blank">212-885-9253</a> <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"><a href="tel:212-949-9022" target="_blank">212-949-9022</a></span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;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"><a href="tel:212-949-9190" target="_blank">212-949-9190</a> <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"><a href="tel:917-816-6428" target="_blank">917-816-6428</a></span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;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">gsshatan@lawabel.com</a></span></i></b><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;background-image:initial;background-repeat:initial">
<b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">ICANN-related: <i><a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a></i></span></b><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt;line-height:12.0pt;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">www.lawabel.com</a></span></i></b><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Apr 7, 2015 at 3:29 PM, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
On Mon, Apr 06, 2015 at 11:04:14AM +0200, Lise Fuhr wrote:<br>
> Please see the attached initial discussion draft of the two models from our legal counsel.<br>
<br>
Thanks for this. I've read it. I have some questions. Questions for<br>
Sidley are listed, and then some observations for our own discussion<br>
(which needn't take up Sidley's time) follow when appropriate in<br>
square brackets.<br>
<br>
In I.A, particularly in numbers 4 and 6, I can't tell whether the<br>
assumption is that there are new agreements between PTI and the RIRs,<br>
and PTI and IETF. I think the fact that PTI is a new legal entity<br>
means that new agreements would be required. Is that correct? [The<br>
reason I ask this is because there is a possible risk of things coming<br>
apart if the other operational communities need to be engaged in a new<br>
negotiation. If PTI just takes the existing agreements and does a<br>
global search and replace for ICANN with PTI, that's nice, but it<br>
doesn't solve everything. For instance, the IETF would have to<br>
publish a new version of RFC 2860. It's worth remembering that every<br>
grievance everyone has with an existing document comes into play once<br>
the document is opened for editing.]<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif"">GSS: As I've noted elsewhere, the RIRs and IETF have 3 options: They can remain under contract with ICANN and ICANN can arrange with
PTI to provide the services. Depending on the existing agreements, an amendment to those agreements may or may not be required. Alternatively, ICANN can assign any or all of the agreements to PTI, so that PTI stands in ICANN's shoes in the agreement. Again
depending on the existing agreements, the consent of the RIRs</span><span style="font-family:"Arial","sans-serif""></span><span style="font-family:"Verdana","sans-serif""><o:p></o:p></span></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"><br>
By way of comparison, in II.B, does using Functional Separation permit<br>
ICANN to continue working under its existing MoUs? I'd assume yes,<br>
because AFAIK none of the existing agreements specify the internal<br>
arrangements of how ICANN delivers the service. [Notwithstanding<br>
Milton's point about getting it "right", given the timeline there is a<br>
significant advantage to not having to negotiate, I think, no?]<br>
<br>
III.C talks about CSC. In the case of a full legal separation with<br>
independent governance, would the CSC be needed at all? Presumably<br>
the arrangements between PRI and their customers would be a<br>
contractual one, and as such the management of such contractual<br>
disputes ought to be via those contracts, and not through an extra<br>
body. Or is the point that the way such a contractual arrangement<br>
would solve such disputes ought to be along the lines of the CSC?<br>
<br>
In III.D.2 there is a question about "ultimate accountability over<br>
ICANN's stewardhip". I'm not entirely sure which cases this applies<br>
to. If there is a legal separation, how is this question relevant for<br>
CWG? Under the legal separation described, PTI becomes the new IANA<br>
functions operator. If there's full independent governance of PTI,<br>
for instance, isn't ICANN's stewardship completely gone -- it has only<br>
responsibility for policy, and not for IANA operation at all, right?<br>
Is that part of the point of this question?<br>
<br>
On III.I, I'm not sure what the difference is between CSC and IRP.<br>
Why are both things needed?<br>
<br>
Best regards,<br>
<br>
A<br>
<span style="color:#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a><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></span><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>