<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<base href="x-msg://43/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>
<div>On Jun 23, 2012, at 5:47 PM, Lee W McKnight wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div ocsi="0" fpstyle="1" bgcolor="#ffffff">
<div style="direction: ltr; font-family: Tahoma; color: rgb(0, 0, 0); font-size: 10pt; ">
Parminder,<br>
<br>
What I believe McTim and I, and David, are saying, is that the sledgehammer cannot be directed.<br>
<br>
Messing with the root zone file in any way - always - would hit everyone's fingers.<br>
<br>
It would be the opposite of 'maintaining stability of the net.'<br>
<br>
And, OFAC would have that explained to them in whatever way works, metaphorically or not, should they ever attempt to go there, by NTIA, and others.<br>
</div>
</div>
</span></blockquote>
<div><br>
</div>
<div>Lee - </div>
<div> </div>
<div> I am in general agreement, but will note that there is an underlying requirement</div>
<div> for transparency in the governance and operation of these functions in order for</div>
<div> that (inadvisability to meddle in the core functions) to actually hold true.</div>
<div><br>
</div>
<div> DoC/NTIA has done a credible job in keeping the oversight role to the minimum </div>
<div> necessary and relatively free of US political concerns. While we all hope this </div>
<div> wil be the case, there would be no way of knowing if otherwise unless the actual</div>
<div> interactions between NTIA and ICANN are open and transparent. As long as </div>
<div> this is the case, any cross-USG interactions (e.g. the postulated OFAC issue)</div>
<div> would be apparent to the community and allow for appropriate response.</div>
<div><br>
</div>
<div> To this end, ARIN's written comments on the IANA Notice of Inquiry specifically</div>
<div> called out the transparency and accountability requirement:</div>
<div><br>
</div>
<div> "In order to continue to build confidence in the Internet, it is critical that the IANA </div>
<div> functions be managed in a way that is open, transparent and globally accountable. "</div>
<div> <<a href="http://www.ntia.doc.gov/files/ntia/comments/110207099-1099-01/attachments/ARIN%20NTIA%20IANA%20NOI%20Response%20Approved%20FINAL.txt">http://www.ntia.doc.gov/files/ntia/comments/110207099-1099-01/attachments/ARIN%20NTIA%20IANA%20NOI%20Response%20Approved%20FINAL.txt</a>></div>
<div><br>
</div>
<div> I believe that Parminder has a valid point that we should not be complacent with</div>
<div> respect to the ability of the USG to unilaterally act in these matters, while it is </div>
<div> hoped that appropriate structure of any oversight role will provide the transparency </div>
<div> that the community needs to facilitate accountability where needed.</div>
<div><br>
</div>
<div>FYI,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
</div>
<div><br>
</div>
</div>
</body>
</html>