<p>+1. Would that suggest an agreement and/or MOU rather than a contract? </p>
<p>Cheers<br></p>
<div class="gmail_quote">On Oct 23, 2014 10:14 PM, "Phil Corwin" <<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">
ICANN currently performs the IANA functions under contract to USG at no charge, so what is the revenue source?
</div>
<div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">
<br style="display:initial">
</div>
<div style="font-size:initial;font-family:Calibri,'Slate Pro',sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">
Sent from my BlackBerry 10 smartphone.<br>
<br>
Philip S. Corwin, Founding Principal<br>
Virtualaw LLC<br>
1155 F Street, NW. Suite 1050<br>
Washington, DC 20004<br>
202-559-8597/Direct<br>
202-559-8750/Fax<br>
202-255-6172/Cell<br>
Twitter: @VLawDC<br>
<br>
"Luck is the residue of design" -- Branch Rickey</div>
<table width="100%" style="background-color:white;border-spacing:0px">
<tbody>
<tr>
<td colspan="2" style="font-size:initial;text-align:initial;background-color:rgb(255,255,255)">
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in;font-family:Tahoma,'BB Alpha Sans','Slate Pro';font-size:10pt">
<div><b>From: </b>Greg Shatan</div>
<div><b>Sent: </b>Thursday, October 23, 2014 5:08 PM</div>
<div><b>To: </b>Burr, Becky</div>
<div><b>Cc: </b><a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a></div>
<div><b>Subject: </b>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style="border-style:solid none none;border-top-color:rgb(186,188,209);border-top-width:1pt;font-size:initial;text-align:initial;background-color:rgb(255,255,255)">
</div>
<br>
<div>
<div dir="ltr">I don't think there's any reason to assume that IANA, Inc. would be an asset-less entity. The assets that the IANA department uses to perform its functions could (and probably should) become assets of IANA, Inc. Likewise, the employees of the
IANA department could become employees of IANA, Inc. Capitalizing the entity and giving it revenue would be a challenge, but not an unreasonable one. As for piercing the corporate veil, I don't think that would be a paramount concern for ICANN, since they
are now fully liable for the acts of the IANA department.
<div><br>
</div>
<div>Finally, I doubt that one would need to replicate the broader accountability mechanisms -- amend and adapt, yes -- but not replicate.<br>
<div><br>
</div>
<div>Greg Shatan</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 23, 2014 at 4:22 PM, Burr, Becky <span dir="ltr">
<<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>And aren’t we concerned that incorporating IANA as a sub leaves users depending on an asset-less entity in the event there is a problem? Presumably, ICANN would want to set up a sub that would survive an attempt to pierce the corporate veil. In addition,
we would have to replicate all of the broader (other than SLA) accountability mechanisms.</div>
<span>
<div><br>
</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif">J. Beckwith Burr<u></u><u></u></span></p>
<p class="MsoNormal" style="font-size:11pt"><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Neustar, Inc. /</span></b><span style="font-size:9pt;font-family:Arial,sans-serif"> Deputy General Counsel and Chief Privacy Officer<u></u><u></u></span></p>
<p class="MsoNormal" style="font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif">1775 Pennsylvania Avenue NW, Washington, DC 20006<u></u><u></u></span></p>
<p class="MsoNormal" style="font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Office</span><span style="font-size:9pt;font-family:Arial,sans-serif">:
<a href="tel:%2B%201.202.533.2932" value="+12025332932" target="_blank">+ 1.202.533.2932</a> <span style="color:rgb(6,134,88)"> Mobile</span>:
<a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a> <span style="color:rgb(6,134,88)">/ <a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a> /
<a href="http://www.neustar.biz" target="_blank">www.neustar.biz</a></span></span></p>
</div>
</span></div>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;border-bottom:medium none;border-left:medium none;padding-bottom:0in;padding-left:0in;padding-right:0in;border-top:#b5c4df 1pt solid;border-right:medium none;padding-top:3pt">
<span><span style="font-weight:bold">From: </span>Milton L Mueller <<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>><br>
</span><span style="font-weight:bold">Date: </span>Thursday, October 23, 2014 at 3:51 PM<br>
<span style="font-weight:bold">To: </span>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>>, "<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<br>
</div>
<div>
<div>
<div><br>
</div>
<div>
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><a name="1493edcbec4a6454_1493eaca4ae4754e__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:4.8pt"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif">
<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Greg Shatan<br>
<br>
</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p><span>1.<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span><u>Make IANA a Subsidiary of ICANN</u>. In order to promote structural separation, and to allow for future separation of the IANA group from ICANN should that become appropriate, IANA could become a wholly-owned subsidiary of ICANN (rather than
a department). This would allow other entities to contract directly with IANA, rather than contracting with ICANN for IANA services.This would also make future separation easier (and should make the threat of separation as an accountability mechanism more
realistic).<u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">MM: Based on my initial, rather quick evaluation of this idea, I think it is a good idea for the short term; in fact, those who argue for a new, independent
contracting authority might be well-served if IANA were a separate subsidiary of ICANN. This would, as Greg suggests, make it easier to contract separately with ICANN’s IANA and facilitate the kind of separability that might be required in the future.
<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">However, this would be the easy part. The hard part is: who awards the contract?
<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">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><br>
<br></blockquote></div>